Support Assistant

It can change the order, not just explain the returns policy.

Support Assistant answers your customers from your own documents and shows the sources. When something needs doing — a lookup, a change of address — it does it in your own systems, once the customer has confirmed that exact change. And your team can step into any conversation and take over.

Shows the documents behind every answer Declines rather than guessing A person can take over mid-thread
Order 41822
Deliver to
Flat 2, 14 Rue Lafayette
Dispatch
Thursday
I’ve moved. Can order 41822 go to 8 Kensington Row instead?
orders.lookup 41822 — not yet dispatched, deliver to Flat 2, 14 Rue Lafayette
It hasn’t been dispatched, so the address can still change.

Change delivery address

From
Flat 2, 14 Rue Lafayette
To
8 Kensington Row

A worked example. Press Confirm and watch the order change — nothing here leaves your browser.

It answers from what you actually published.

Retrieval first, generation second. The assistant looks up passages in your own material, answers from those, and shows what it used. When your content doesn’t cover the question it says so and offers a person instead — the single behaviour that decides whether a support bot gets trusted or switched off.

Only links that appear in your own published material can be clicked, so an invented address can never be followed by a customer. Replies stream as they are written, and an internal handbook can be restricted to an internal assistant and never reach one.

Do you ship to Germany?

Yes — standard delivery is 3–5 working days, and it’s free over €60.

Can I pay in three instalments?

I can’t find anything published about instalment payments, so I’d rather not guess. I can put you through to the team.

Nothing changes until your customer says yes.

Approval covers that one action and nothing else — there is no blanket “this chat may now make changes”. Anonymous visitors get read-only actions; anything that writes needs a customer who is signed in. You decide, per action, whether it is on, read-only or off.

Every call is logged with its arguments, its result and how long it took, and the confirmation the customer reads is written from the record rather than by the model — so the assistant cannot tell somebody a thing was done when it wasn’t.

Look up an orderAnyone
Check stockAnyone
Change a delivery addressSigned in, confirmed each time
Cancel an orderSwitched off

A person can take over, mid-sentence.

Your team gets a Slack message or an email carrying the last exchange, so they can judge urgency without opening anything. They reply in the thread the visitor is already reading — nothing restarts and nothing is lost — and hand it back when they’re done.

The assistant escalates on its own when it is stuck or the conversation turns, and replies show as coming from your team rather than from a named individual. Reading transcripts is a separate permission from replying to them.

My parcel arrived damaged and I need it before Friday.

Priya from the team joined

Hi, I’ve got this one. A replacement is going out today on next-day delivery — you’ll have it Thursday. I’ll email the label for the damaged one.

Three steps to live.

We onboard customers one at a time at the moment, so the first step is a conversation rather than a form.

We set you up

There is no self-service signup here. Tell us what your support looks like and we open your tenant, your first assistant and an admin login for you. Give us your website and the widget arrives already wearing your colours.

Give it your material

Upload PDF, Word, Markdown, CSV and text, in folders. Add a web page by giving us its address — one page per address you name, because we don’t wander your site. Re-index whenever you change something; the new version is built invisibly and swapped in at once.

Paste one line into your site

A single script tag, locked to the origins you allow. Choose whether it floats in a corner, sits inside your own layout or docks beside the page. Persona, greeting, branding and handoff rules are yours from the console.

One platform, every company you serve.

Resell it. Each client company gets its own knowledge, its own branding, its own assistants, its own limits and its own bill — and they are separated where the data lives rather than by a filter somebody has to remember to write.

Separated at the database

Row-level isolation, enforced where the data lives, so it cannot be undone by a coding mistake in application code.

Your plans, your prices

Set per-model rates and what a billable message costs, with an audited history of every pricing change. Your clients package it up for their own merchants.

Ceilings, not surprises

Monthly spend caps with automatic warnings at 50%, 80% and 100%. When an allowance runs out the current message still finishes and the next conversation routes to a person.

Plans that price on conversations, not on seats you don’t use.

Every plan includes the widget, retrieval, citations, actions, human handoff and the full admin console.

Starter

$19 / month
  • 5,000 questions / month
  • 1 business
  • 2 team seats
  • 30-day conversation history

Advanced

$89 / month
  • 40,000 questions / month
  • 20 businesses
  • 10 team seats
  • 180-day conversation history