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.

Deploy

Procedures

Version 1.0 · Last updated 2026-05-27

Which Procedures the Customer Agent offers in each Moment. Configure them once in Train, attach them to a Moment here.

The same Procedure may be useful in Acquisition (book a meeting) and Support (book a meeting with the account team), but the trigger conditions, variables, and routing differ. Attaching Procedures per Moment keeps the agent doing the right thing in each context.

Key concepts

Per-Moment selection

Each Moment has its own list of attached Procedures. A Procedure can be attached to several Moments at once.

Conditions

Per Moment, you set when the Procedure triggers. Always available, after a Signal, after an unanswered question, only for a specific Audience.

Routing

Where the Procedure sends results. Could be a CRM record, a Slack channel, or your support team. Routing can differ per Moment.

What you can do here

  • Pick the Procedures attached to each Moment
  • Set per-Moment trigger conditions
  • Set per-Moment routing (which team owns the outcome)
  • Reorder Procedures so the most relevant one appears first
  • View per-Moment Procedure completion rates in Analyze

When to use it

  • After creating Procedures in Train and ready to put them in front of customers
  • After a Moment review where you noticed wrong Procedures were firing
  • After adding a new Moment that needs its own Procedure set

How it works

A Procedure defined in Train is reusable across Moments. Here you decide where it appears and under what conditions. The full Procedure logic (variables, action, what it actually does) lives in Train.

Frequently asked questions

How do I add a Procedure to a Moment?

Open Deploy > Procedures, pick the Moment, and select from the list of available Procedures. Save.

How do I create a new Procedure?

Procedures are defined in Train > Procedures. Once created, come back here to attach it.

Why is the same Procedure fine in Acquisition but wrong in Retention?

Usually the trigger condition or routing differs by Moment. Open the Moment's Procedure list and adjust conditions. If the Procedure itself is wrong, edit it in Train.

Can a Procedure trigger only for a specific Audience?

Yes. Set the trigger condition to require the Audience. The Procedure only shows up when the customer is in that Audience.

How do I see how often a Procedure is used?

Open Analyze > Conversations and filter for the Procedure. You see when it fired, how often customers ran it, and what happened next.

Personality
Notifications