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.

Advanced

Multi-step and chained component experiences

Version 1.0 · Last updated 2026-05-27

Multiple steps in a single component, or several components chained one after the other. For onboarding, walkthroughs, and longer journeys.

A customer journey rarely fits in one screen. Onboarding flows, sign-up paths, guided product tours - they all need multiple beats. Multi-step and chained components are how you build those without writing custom code.


Key concepts

Multi-step component

Single component with a built-in stepper. Two to four steps recommended. Each step has its own content (image, header, body, buttons). Common use: in-product onboarding for a new feature.

Chained components

Several independent components linked one after the other. Each is its own component, on its own page or surface. Common use: marketing-site qualification flow that hands off to a sign-up form.

Step IDs and linking

Each component has an ID. Chain components by setting the primary button URL to the next component’s ID. Same-page jumps use #[id]. Cross-page jumps use the path plus the ID.

Final step actions

The last step of a multi-step component can close, redirect, run a Procedure, or capture an email.

What you can do here

  • Build a multi-step component
  • Chain multiple components into a sequence
  • Capture email or other variables at the final step
  • Trigger Procedures at any step
  • Combine chained flows with Audiences for targeted journeys

When to use it

  • You are building a multi-step onboarding flow
  • You have a journey that spans multiple pages
  • You want a quick qualification flow that hands off to a deeper experience
  • You need to onboard a new user with a guided product tour

When not to use it

  • A single step would do. Resist the temptation to make every flow multi-step.
  • The flow is sequential by nature, but the customer often skips ahead. Use chained components instead, where each step is its own page.

How it works

A multi-step component uses an internal stepper. The customer moves through with primary and secondary buttons. Chained components are simpler: each component primary button URL points at the next component’s ID, and the platform handles the navigation.

Frequently asked questions

How do I build a multi-step component?

Open "Deploy > Conversation starters > Library". Filter for Multistep. Pick a template, configure settings, open the editor. Use the Stepper tab to add or edit steps.

How do I add steps to an existing multi-step component?

Open the component editor and find the Stepper tab. Click the plus icon to add a step. Keep total steps to three or four for best results.

How do I chain two components together?

On the first component, set the primary button URL to #[id] of the second component (same page) or /path/#[id] (different page). The second component appears when the customer clicks.

Where do I find a component ID?

The ID appears in the URL when previewing the component or on the settings page.

Can I capture an email at the end of a multi-step component?

Yes. The last step has an email field option. Map it to your CRM or trigger a follow-up Procedure.

Can chained components span different surfaces?

Yes. The first component can live on your marketing site and the next on the product, as long as the Unless snippet is installed on both.

Living Memory: retention and identity matching