An assistant that knows your business.
Give it your documents and your spreadsheet. It answers by voice or by text, on your site or on a link you send.
voice + text · answering Live
Most assistants guess. This one filters.
Text search treats “1.85M” and “3.2M” as the same kind of thing: a big number where a price goes. Your documents are read for meaning. Your spreadsheet is filtered on the actual values.
Upload what you already have.
Policies, brochures, price lists, an FAQ. Then the spreadsheet of whatever you sell or rent. Nothing needs rewriting for the assistant to use it.
- Documents are read for meaning, so wording doesn’t have to match
- Spreadsheets are filtered on the real values, so “under 2M” means under 2M
- Columns you mark private stay private, even from the assistant
- Change a document and the next answer already knows
| Name | Bed | Price | Ready |
|---|---|---|---|
| Marina Court | 2 | 1.85M | 2026 |
| Cedar Wharf | 2 | 1.62M | 2026 |
| Ellis Yard | 2 | 1.94M | 2026 |
| Foundry Row | 3 | 2.40M | 2028 |
Read back every conversation.
Not just what it said — what it looked at. Each answer shows which documents it read and which records it searched, so you can tell a good answer from a lucky one.
- Voice and typing in one thread, in the order they happened
- Whatever you asked for before the chat, saved with it
- Length and cost on every conversation
- Kept for as long as you choose, then deleted
| Name | R. Alvarez |
| r.alvarez@… | |
| Interest | 2 bed, ≤2M |
| Channel | Voice, then text |
Three places to put it.
One assistant, three front doors. They all share the same knowledge, the same settings and the same conversation history.
A link you send
Every assistant gets its own page. Send the link, put it in an email signature, print it on a QR code. Nothing to install.
yoursite.com/a/abc123A button on your site
One script tag puts a chat button in the corner of your own pages. Change the assistant and your site changes with it.
<script src="/widget.js"
data-assistant="abc123"></script>Your own interface
Or build the interface yourself and reach the same assistant over the API.
POST /v1/assistants/{id}/chatBuild your own front end.
Open a conversation, send a turn, read the reply as it arrives. Keys you create and revoke yourself, usage you can see per key, and webhooks that fire on what the assistant heard.
Read the API docs →Three steps, one afternoon.
Give it what you know
Upload your policies, brochures and FAQs. Add the spreadsheet of what you sell, rent or stock.
Tell it how to behave
Write the instructions in plain English, pick a voice, and set what it should ask before a chat starts.
Publish it
A link you can send, or one script tag on your own site. You set the limits.
The answer isn’t the end of it.
Drag a few steps together. Send the enquiry to whoever handles it, push it into your own systems, wait a day and follow up. There is no service for you to write.
See what it can do →trigger
ai.assistant
logic.condition
action.email
data.http
Use your own accounts.
Model usage is billed to you directly, at whatever rate you negotiated. Swap providers whenever you like. The assistant, its knowledge and its history stay where they are.
Keys are stored encrypted, used only to answer your visitors, and revocable from your side at any moment.
See what it does with your own documents.
Upload one, ask it a question, and judge it on the answer. It takes about ten minutes to find out.