Approach

Five rules. Each one has a mechanism in the code.

It is easy to write that an AI agent is safe and does not make things up. It is harder to show where exactly in the product the gate that enforces it stands. This page does the harder thing: next to every rule we name the mechanism that enforces it and the place where you can inspect it.

No certification claims · no borrowed numbers · a rule we cannot point to in the code does not make it onto this page

The five rules

In the order a customer meets them in a conversation. Each one describes what happens in the code, not what we promise.

01

An answer without coverage never goes out

The model writes the whole answer into a buffer, and the citation gate judges it as a whole before the customer sees the first word. An answer that was meant to rest on your content and cites no source is rejected in full, not sentence by sentence, because an uncovered sentence sounds exactly as confident as a covered one. The only answer that needs no citation is one built from live data the agent has just fetched with a tool (an account status, a price list): there is nothing to cite. The customer hears plainly that the material does not cover it, and the question goes to the gap register. In the support agent's channels (the logged-in customer chat, email, SMS, team chat) a second such case in the same conversation hands the matter to a human; the public window on the website stops at a plain refusal.

02

The agent does not change data. It issues a card.

An operation that changes something has no execution path around the card: the agent names the operation, shows the parameters and waits. Approval is a separate human click, and at the moment of the click the checks run again: the card's validity, the parameters against the current account state, and a kill switch that also stops cards already approved. A repeated click replays the saved result instead of running the operation twice. An anonymous visitor cannot issue a card at all.

03

Tenant scope is a condition of the query, not a filter on the result

Knowledge search has a single entry point, and your company's identifier is required there and comes only from the context of an authenticated session, never from a parameter. Without it the query does not exist. The same rule holds in the gap register, confirmation cards and handoffs: every read and write clause starts with the company, and someone else's resource answers exactly like a non-existent one.

04

Ada leads instead of redirecting

Instead of pasting a link, Ada shows the place on the page: she picks an identifier from a closed catalog of sections, and the browser decides what it means. Instead of saying please call us, she books a slot: on the phone, once the company switches voice booking on, she first receives the list of free windows and then books one of them, never a slot outside the list; on the website the same calendar sits in the booking window, where the visitor picks the slot. And when a matter goes beyond her scope, she hands it to a human with a reason from a closed catalog and the full conversation history.

05

What the agent did not know becomes a list to write

Every question without coverage lands in the gap register: variants of the same question merge into one entry with a counter, the sample question is masked for personal data and disappears after the retention period, while the entry stays. Editors write the article and close the gap. If the question comes back despite publication, the gap reopens, because the article does not answer it.

Where to see it

A rule you cannot inspect is a claim. Each of the five has a place in the product or in a document you can read before any sales conversation.

Answers only with coverage
In the chat window: the list of sources under the answer, or a sentence saying the material does not cover it. In the panel: a handoff with the reason no knowledge in the inbox and handoffs.
Confirmation card
In the chat window as a card with the operation name and parameters. Every issue, approval, expiry and execution is recorded in the audit log.
Tenant scope in the query
In documents available before any sales conversation: the security page describes the mechanisms and the data processing agreement template names them.
Ada leads
On this page: in a voice conversation, ask Ada to show one of the sections. On the demo page: a slot picked in the booking window. In the panel: the handoff queue with the reason and a summary of the conversation.
Gap register
In the panel, on the Knowledge gaps screen: questions ranked by how often they repeat, with a sample free of personal data. The mechanism is described on the gap register page.

What you will not find here

Next to what is here. Both lists follow from the same five mechanisms.

What you will find

  • An answer with a list of sources the customer sees right away
  • A confirmation card for every operation that changes data
  • One company's scope written into every database query
  • A register of uncovered questions with a repeat counter
  • A trace of every turn in the audit log, with no raw personal data
  • A data processing agreement template and a subprocessor register available before any sales conversation

What you will not find

  • Answers from outside published content: neither from the internet nor from the model's guesses
  • A data operation executed without a human click
  • A shared knowledge index across companies
  • Certifications we do not hold, or other people's test results used as proof
  • Accuracy figures without coverage in your own conversations
  • A promise that the model never errs: an uncovered answer is rejected, and that is all we claim

How you start

Two roads to the same agent. They differ in who takes the first steps, not in what you get at the end.

1

On your own, today

You create an account: company name, email address, password and acceptance of the terms, then a six-digit code from your inbox, valid for fifteen minutes. For 14 days you test without giving a card; you provide one only when moving to a paid plan. In the panel you point at your content (files or a website address to scan) and copy a single line of script into your site.

Create account · How to embed the widget

2

We deploy with you

You book a demo without an account: you pick a slot in the booking window, receive a confirmation with a calendar file and reminders a day, an hour and ten minutes before the meeting, and Ada runs the demo, briefed on your company from a scan of your website. The installer in the panel can do the embedding: you provide file access to your site (SFTP or FTPS), the wizard recognises WordPress and installs a single plugin without touching the theme, and on a static site it adds a block before the end of the page. Before writing it checks the plan limit, the account owner accepts the contract annex, and after the job neither a copy nor our access data stays on your server.

Book a demo · Talk to us

Works alongside what you already use

The agent does not require a change of tools. It connects to the channels your customers already write to and call.

Website Email SMS Phone Team chat Calendar invitations

Chat, voice and email land in one inbox. The providers that process data on our behalf are listed by name, with the country of processing and the transfer basis, in the subprocessor register.

Questions we hear most often

Will Ada answer from the internet when the knowledge base lacks something?
No. She answers only from your company's published content. When there is no coverage, she says so plainly, and the question goes to the gap register as a task for the editors.
What happens when a customer asks for a change to their account?
The agent prepares a card: operation name, parameters, expiry time. Execution happens only after a human click, and the trace of that click stays in the audit log.
Can I start without talking to a salesperson?
Yes. You create the account yourself, test for 14 days without giving a card, and upload content and the script from the panel. The demo and the installer are for those who prefer someone from our side to take the first steps.
How do I know what to add to the knowledge base?
From the gap register. Uncovered questions line up by how often they repeat, so you write first what customers ask about most, not what seemed important in a meeting.

Test the rules on your own content

Upload a fragment of your material, ask the questions your team answers every day, and see what remains in the log after the conversation.