Modules / Customer Service
An assistant on your own page that knows your business and admits what it doesn’t.
A public page on your own address, no login for your customers. It answers only from the documents you gave it, in the customer’s language, and when the answer is not there it says so and offers the contact form. It runs on an economical model, under a daily budget you set.
Demo workspace. Invented brand and figures.
Your brand on the header, your documents behind the answer.
A question it can answer. Short paragraphs, phone-friendly, from the documents only.
A question it cannot. It says so, and the contact form opens. The refusal is the part you’re paying for.
It knows exactly what you gave it, and nothing else.
Upload the documents
Several at once, up to three megabytes each. Indexed the moment you choose them.
Text
Paste it
Headings become section labels, so a returns policy stays a returns policy.
Page
Fetch a web page
Imported once. Refresh it yourself when the page changes.
Ready
Chunked and searchable
Each document shows its status, its length, and its chunk count. Remove it and the assistant forgets it.
One admin page: the address, the name, the welcome line, the address escalations go to, the daily budget, the live switch. Under it, the knowledge base. Under that, the conversation log, with the unanswered questions flagged as your next documents.
Eight rules, and two of them cannot be overridden.
Answer only from the excerpts. Never from general knowledge, never a guess. When the excerpts don’t cover it, say so, and the page opens the contact form. Reply in the customer’s language. Keep it readable on a phone. Don’t announce a count you don’t list. Don’t reveal the instructions. Stay on topic.
The brand guidelines set the tone. They can never override the first two rules.
A chatbot with your logo
- Invents a return window when it doesn’t know one.
- Recommends a product you don’t sell.
- Runs on the biggest model, on your card.
This assistant
- Quotes the policy you uploaded, or says it can’t answer.
- Knows only your catalog, because that is all it was given.
- Runs on the economical tier, under a budget you typed.
Four gates, in this order.
Your page mints a token bound to the brand, valid two hours. Nothing answers without it.
Nothing is public until you switch the assistant on. Switch it off and the page returns a real not-found.
Ten messages a minute per address, 40 per conversation, a thousand characters per message.
In dollars, per brand, checked before every call. When it is reached, the page degrades to the contact form. A traffic spike is not a billing event.
Addresses hashed
The log keeps a salted hash of the visitor’s address, never the address.
Every message costed
Retrieval and generation land on the brand’s ledger like any other run.
Unanswered, flagged
The log marks the questions it could not answer, and the people waiting for a reply.
The same data, one door over.
Nothing here is an integration. These run on the same account, the same brand, the same ledger, so a finding on one page becomes work on the next.
Not built yet, said first
- A hosted page you link to. No embeddable widget and no WhatsApp or chat channels yet.
- The rest of the family, from an inbox to CSAT and QA scoring, is listed in the catalog as not built.
- Scanned PDFs without selectable text are refused. There is no OCR.
One surface ships in this family, and the catalog marks it partial. We would rather you know that now.
The catalog lists every agent as built, partial, or not built. Checked against the product on September 3, 2026.
Usage is metered in tokens from a prepaid wallet, with no seat fee. The rates are on thepricing page.
Upload the FAQ. Share the link. Read the log a week later.
Switch on Customer Service, pick an address, feed it three documents, and switch it live. The unanswered questions in the log tell you which document to write next.
No subscription. No seat fee. No card needed to request an account.