Skip to content

Agent

One agent. Every customer moment.

The customer-facing side of Unless — one AI Customer Agent across acquisition, retention, expansion, and support, with the Help Center it auto-generates as its public face. Browse a moment, or see the full overview.

Acquisition

Qualify, convert, educate. 24/7 on your marketing site.

Retention

See churn coming. Act before it does, inside the customer's product.

Expansion

Catch upsell signals early. Route them to the right owner.

Support

Resolve, co-pilot, learn — across every helpdesk and channel.

Engine

The platform underneath.

The back-of-house side of Unless — a Living Knowledge library that maintains itself, plus the Train → Test → Deploy → Analyze loop that keeps every Customer Agent sharper after every conversation. See how the engine compounds.

Train

Always current. Always ready. Living Knowledge + Living Context.

Test

Before a customer sees it. Preview, simulate, audit.

Deploy

One agent. The whole journey. Memory across all of it.

Analyze

Performance, value, AI maturity. All visible. All live.

Trust

Built for the EU from day one

The architecture that lets your DPO, security, and procurement teams sign off without slowing your team down. Browse the page, or jump straight to a section.

Privacy Vault

Twelve numbered measures keep sensitive identifiers home.

Compliance posture

Three pillars — sovereignty, AI Act readiness, sector readiness.

Architecture

Five EU-resident layers — touchpoints to LLM constellation.

Frameworks

EU AI Act, GDPR, DORA, OWASP — built into the platform, not bolted on.

Customers

Trusted by leaders

How regulated-Europe brands — from Visma to Onguard — turned customer success into a revenue engine with Unless.

Visma Enterprise AS

Norway's leading ERP — modernized self-service with Unless.

Helping patients

Patient self-service surged within weeks of deploying Unless.

Enhancing credit software

Financial service Onguard powers their support operations with Unless.

Ticket deflection at scale

Meet Sally, Kontek’s AI support colleague in regulated finance.

Resources

Search resources and support articles

Documentation, articles, and recipes for getting the most out of your Unless deployment — plus a help desk when you need a human.

Help center

Get-started guides and advanced playbooks for the platform.

Security and compliance

Privacy measures, security by design, and compliance guidelines.

Developer documentation

Find reference documentation for the javascript API.

The Unless cookbook

Bite-sized examples for every stage of the customer lifecycle.

Pricing

Pay per outcome. You choose.

Two equal-weight plans, both built around outcomes. Browse the page, or jump straight to a section.

The two plans

Flex (€0.99 per outcome) or Fixed (€1,999/month). Equal weight.

What's included

Full platform on both — Living Knowledge, Memory, Context.

Flex modules

Productized add-ons. À la carte on Flex, bundled into Fixed.

Frequently asked

What counts as an outcome, fair use, and switching mid-year.

Train

Knowledge base

Version 1.0 · Last updated 2026-05-27

Where structured knowledge lives after Living Knowledge processes your Sources. Continuously restructured and rewritten into one non-ambiguous library.

Raw Sources are messy. Different writing styles, repeated information, contradicting answers, scattered across systems. The Content library is the Engine's clean version of all that, ready for the agent to use without surprises.


Key concepts

Structured content units

Discrete pieces of content the Engine derives from your Sources. Each unit covers one idea, written in a consistent voice and stripped of duplicates.

Continuous restructuring

The library rebuilds itself whenever Sources change. Add a new Source, the library updates. Update an existing Source, the library updates. You do not maintain this manually.

Source traceability

Every unit in the library traces back to the Source it came from. When the agent answers a question, you can follow the chain to the original content.

Conflicts and gaps

The Engine flags conflicting content across Sources and topics where Living Knowledge is thin. These appear in the Inbox as Messages waiting for human judgment.

What you can do here

  • Review structured content units the Engine has derived from your Sources
  • Trace a content unit back to its original Source
  • See which units are referenced most often by the agent
  • Inspect flagged conflicts and gaps
  • Approve, edit, or discard suggestions from Team Feedback

When to use it

  • You want to understand what the agent actually knows, not just what is in your Sources
  • The agent gave a wrong answer and you want to find the offending content unit
  • You are auditing Living Knowledge for an internal review

When not to use it

  • You want to add new content. Add it as a Source and the Content library will pick it up.
  • You want to publish customer-facing articles. That is what the Help Center is for.

How it works

The Engine reads every Source, breaks it into ideas, dedupes across Sources, and rewrites into one voice. This is the difference between a vector index over raw documents and a maintained library: ambiguity gets removed at processing time, not at retrieval time.

Frequently asked questions

How do I see what is in the Content library?

Open Train > Knowledge base > Content library. The view lists structured units, with filters for topic, Source, and usage frequency.

Why is a content unit wrong?

Open the unit to see its source chain. Usually one of the upstream Sources is wrong, outdated, or contradicts another Source. Fix the Source and the library updates.

How do I resolve a conflict between Sources?

Open the conflict in the Inbox. Decide which Source is correct, archive or update the other, and the library reprocesses.

Can I edit content directly in the library?

No. Edits happen at the Source level. The library is derived, not authored.

How often does the library refresh?

On every Source change. There is no schedule to manage.

Knowledge base · Sources