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.

Getting started

Key concepts

Version 1.0 · Last updated 2026-05-27

A short tour of the vocabulary the help center uses. Read this before going deeper into Train, Test, Deploy, or Analyze.

Unless uses a small set of concepts that recur across every section. Once you know them, the rest of the help center clicks into place quickly.

The agent side

Customer Agent

The customer-facing AI agent. Runs on your marketing site, product, portal, help center, and any helpdesk channel. One agent serves all four moments of the customer lifecycle.

Team Assistant

An AI assistant for your internal team. Lives inside the helpdesk your team already uses. Drafts replies, surfaces context, and runs Procedures on behalf of agents.

The moments

Four customer-lifecycle moments where the agent works: Acquisition, Retention, Sales expansion, and Support. One agent covers them all, but each moment has its own Signals, Personality, Procedures, and Notifications.

The engine side

Engine

The back-of-house platform behind both agents. Two structural ideas live here: the three senses and the loop.

The three senses

  • Living Knowledge is what the agent knows. Built from your Sources, structured into the Content library, published as the Help Center.
  • Living Memory is who the agent is talking to. Per-customer preferences, history, sentiment, and goals. Scoped per agent, kept private.
  • Living Context is where the agent is acting. Connections to your CRM, billing, ERP, helpdesk, and custom APIs so the agent acts inside your systems of record.

The loop

Four phases the Engine cycles through: Train, Test, Deploy, Analyze. Each pass sharpens the agent. Train builds the knowledge and procedures. Test validates before customers see anything. Deploy puts the agent to work. Analyze measures what happened and feeds the next cycle.

Trust and governance

Trust

Governance layer that sits alongside the loop. Four pillars: Transparency, Privacy, Security, Accountability. Built into the platform at the architecture level, not added after the fact.

Agent boundary

The agent does real work across the lifecycle, but never takes an irreversible action without a human approving the boundary first. Customers get help. Your auditor gets the receipts.

Model constellation

The Engine runs on a constellation of EU-hosted foundation models from Anthropic, Mistral, OpenAI, Google, Cohere, and Amazon Titan. The constellation lets Unless pick the right model for the job and swap providers in real time if regulation or vendor terms change. Customer data is never used to train public models.

Frequently asked questions

How do I tell Customer Agent from Team Assistant?

Customer Agent talks to your customers. Team Assistant helps your team. Same Engine behind both, different surface.

What is the difference between Living Knowledge, Memory, and Context?

Knowledge is what the agent knows from your Sources. Memory is what it remembers about a specific customer. Context is what it sees right now from your CRM, billing, and product data.

Why is Sales expansion sometimes written as just Expansion?

On unless.com the moment is labeled Expansion. The help center uses Sales expansion to be unambiguous. They mean the same thing.

Where do Procedures fit?

You set up Procedures in Train. You attach them to a specific Moment in Deploy.

About Unless
Glossary