Channel

A conversation that closes the case on your site

One line of script. About twenty kilobytes compressed. Zero requests to other companies' servers. The widget answers with citations, and when a case is beyond it, hands it to a human with the full context.

No changes to your code · works on any CMS · no site rebuild

Example: a return handled in one conversation

A demonstration conversation. The answers come from a returns policy loaded into the knowledge base.

Customer I bought these shoes two weeks ago and they are too small. Can I return them?
Agent Yes. You have 30 days from delivery, so the deadline is 8 September. The shoes need to be unworn with the tag on. Source: Returns policy, point 3.
Customer Then I would like a return label.
Agent I have prepared a return for order 48812. Before I send the label, our team confirms it.
Operator Approves the confirmation card with one click.
order lookupeligibility checkconfirmation cardlabel dispatch

Four messages, one conversation, zero minutes of team time up to the approval. An operation that changes data never runs without a human.

How it works on your side

1

Paste the script

One tag before the closing body element, carrying your organisation's public key. It behaves the same on a shop platform, on WordPress and on a hand written page.

2

We set up your domain list

The widget answers only on pages you name. A request from any other domain is not served, so copying the snippet gets a stranger nowhere. We enter the list during onboarding, based on the addresses you give us.

3

You check that the widget came up

The embedding screen in the panel fetches your page and says whether the widget answers on it. When it stays silent, it names the reason: a typo in the key, a domain outside the list, the snippet pasted into one subpage instead of the template.

The details that usually surface only after launch

It does not break your styles
The whole interface lives in its own Shadow DOM tree. Your CSS does not reach in, ours does not leak out.
It pulls nothing from outside
The script has no runtime dependencies. It fetches no library from a content delivery network, so it adds neither a consent banner nor another entity to your privacy policy.
Identity without a cookie
The conversation session rests on a short lived token carried in a header. That keeps it working on your domain even when the browser blocks third party cookies.
Citations in the bubble
Under each answer you can see which of your materials it came from. The customer clicks and checks.
Answer rating
A thumbs down is appended to the audit log with the turn number and the reason given, so the team can filter it there by entry kind. The gap register fills up separately, from questions with no coverage in your materials.
Starter prompts
A few ready questions that you set yourself. The customer does not have to invent what to ask.
Voice from the same window
The conversation can switch to voice without installing anything.
Theme and language
The widget follows the host page's theme and language, so it does not look pasted in from somewhere else.

First conversation in about fifteen minutes

Upload a few articles, paste the script on a test page, and ask the agent the questions your team answers every day.