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

Procedures

Version 1.0 · Last updated 2026-05-27

Agentic actions the Customer Agent and Team Assistant can take on behalf of a customer during a conversation.

An agent that can only answer questions is half useful. An agent that can also book a meeting, redirect to the right page, escalate to live chat, or run an API call gets work done. Procedures are how you give the agent that capability while keeping the customer in control.

Key concepts

Procedure types

Seven actions are available out of the box.

  • Suggest a follow-up question. Surfaces a related question the customer can click.

  • Redirect to a URL. Sends the customer to a specific page.

  • Start a component. Opens an Unless component during the conversation (video, form, multistep flow).

  • Switch topic. Moves the conversation to a different slice of Living Knowledge.

  • Live chat. Hands the conversation to a human agent.

  • API call. Calls an endpoint on your backend and uses the response.

  • Custom JavaScript. Runs arbitrary JavaScript when the customer clicks. Covered in detail under Custom Procedures.

Variables

Inputs a Procedure needs to run. If the agent does not already have a variable, it asks the customer for it. Variables can depend on previous answers.

Triggers

Where and when a Procedure shows up. Linked to a Source, fired on negative feedback, after an unanswered question, or always.

Escalation flag

Marks a Procedure as escalating the conversation. Used in reports to track how often the agent reached its limit.

What you can do here

  • Create Procedures of any of the seven types
  • Set variables the agent will collect during the conversation
  • Link a Procedure to one or more Sources or FAQs
  • Set trigger conditions (always, after negative feedback, after an unanswered question)
  • Mark a Procedure as an escalation
  • Test a Procedure in Preview before going live

When to use it

  • Customers ask about pricing and you want to redirect them to the pricing page
  • Customers need to book a call and you want the agent to handle scheduling
  • The agent should escalate to a human when it cannot resolve

How it works

The agent decides when a Procedure is relevant based on the conversation and the trigger conditions. The customer always picks whether to run the Procedure. This keeps a human in the loop and prevents the agent from acting unprompted.

The platform enforces one line you cannot cross: the agent never takes an irreversible action without a human approving the boundary first. You decide which Procedures count as irreversible during setup.

Frequently asked questions

How do I create a Procedure?

Open Train > Procedures and click Create procedure. Pick the type, give it a name, configure variables, set triggers.

How do I attach a Procedure to a specific Source?

Open the Procedure and add the Source under the Triggers tab. The Procedure now appears whenever the agent uses that Source.

How do I collect an email address from the customer?

Add a variable to the Procedure. Mark it required. The agent asks the customer for the email before running the Procedure.

How do I escalate to a human?

Use the Live chat Procedure type if you have a live chat integration enabled. Mark it as an escalation so it shows up in your escalation reports.

How do I limit a Procedure to certain customers?

Combine the Procedure with an Audience. Set the Procedure to fire only when the customer is in that Audience.

How do I see if a Procedure is working?

Open Analyze > Conversations and filter for conversations where the Procedure ran. Check completion rates and customer reactions.

Knowledge base · Help Center
Audiences