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.

Test

Simulations

Version 1.0 · Last updated 2026-05-27

Scripted conversations that run against the Customer Agent automatically. Catch regressions and validate edge cases before a change goes live.
This feature is in Beta and will be available soon.

Simulations are on the platform roadmap. The Preview and Quality reports tabs cover most testing needs until Simulations ship.


Preview is one human, one session. Useful, but slow. Simulations turn the questions you care about into a regression suite that runs every time you change a Source, a Procedure, or a Personality. The suite is what makes Living Knowledge improvements safe.

Key concepts

Scripted turns

The customer’s side of a conversation, written as a sequence of messages. Includes follow-ups and Procedure clicks.

Conditions

The Audience, Living Context, topic, and surface the Simulation runs under. Same setup you would use in Preview.

Expected outcomes

What you expect the agent to say or do. Used to score each run.

Suites

Groups of Simulations that run together. A daily regression suite, a per-moment suite, a pre-release suite.

What you can do here

Once Simulations ship, you will be able to:

  • Write scripted conversations that drive the agent through specific scenarios
  • Group Simulations into suites and run them on a schedule or on demand
  • Compare scores across runs to catch regressions
  • Trace failures to the Source, Procedure, or Living Context value that caused them

When to use it

  • Before any change to Living Knowledge that could break existing answers
  • Before publishing a new component or Moment
  • Before scaling to a new market or language

What to do until Simulations ship

Three things cover most of what Simulations would do.

Preview