Channels
WhatsApp, Telegram, the chat on your site — one bot behind all of them, so an answer is the same answer wherever it was asked.
Bot
building.
One bot on every channel the firm answers on. It reads what people ask, looks it up in the firm’s own systems, answers in the firm’s voice — and hands over to a person the moment it should, with the whole thread attached.
00 — THE INBOX
000%
- 00The inbox— MESSAGES · — CHANNELS
- 01One doorEVERY CHANNEL · ONE BOT
- 02Read— INTENTS · NONE GUESSED
- 03Looked up— LOOKUPS · YOUR SYSTEMS
- 04Answered— IN THE LANE THEY CAME
- 05Handed over— TO A PERSON · THREAD ATTACHED
Six messages on three channels, which is how they actually arrive: at once, in different voices, and unread. Everything after this is the same six messages — none dropped, none answered twice.
What it covers
Six modules. The hand-over is designed before the first answer. Where the desk it looks things up in is the customizable CRM, the bot reads it as source.
Intent
Reading what a message wants — a booking, a price, an order, a person — before deciding what to do with it.
Lookup
The bot reaches into the firm’s own systems — the calendar, the desk, the orders — and answers with what is actually there.
The voice
Answers written to the firm’s own voice: what it says, what it never says, how it signs off. Written down, like a brand kit.
Hand-over
The moment the bot should stop: a complaint, a negotiation, a person asking for a person. It hands the thread to someone, whole.
The record
Every conversation kept, attributed and searchable, in the firm’s own storage. What was asked is as valuable as what was answered.
What a bot of ours is held to
Four rules, written before the first message. A bot that breaks one is a bot that is switched off.
- NO GUESSING Every fact in a reply is looked up in a system the firm trusts, and the reply says which one. A bot that cannot find it says so.
- NO TRAP A person who asks for a person gets one, with the whole thread attached. Never a loop, never a ticket number and silence.
- YOUR VOICE Written down, owned by the firm, applied the way it would be to a new hire. The bot does not have a personality; the firm does.
- YOUR DATA Conversations stay in the firm’s storage, under the firm’s name. The bot does not train on your customers.
How it runs
Three phases, the same three every line runs. Measured at each one.
P.01
Map
Two weeks. What people actually ask, read out of the inbox you already have. The intents, the systems each one needs, and the moments to hand over — written down before a reply is drafted.
P.02
Build
One quarter. The bot on one channel first, answering real messages with a person reading every reply, then the other channels, then the gates loosened as it earns them.
P.03
Hand over
The voice document, the conversation log and the hosting move into the firm’s accounts. The bot is yours to change; the record is yours to read.
What changes
Signals the engagement watches, and the direction they are expected to move.
- TIME TO FIRST ANSWER From whenever someone is free to the moment the message lands. The same answer at 02:00 as at 10:00.
- ANSWERS THAT WERE GUESSES To none. Everything the bot says it looked up, and it says where.
- THREADS THAT DIE To none. A conversation the bot cannot finish arrives with a person, whole.
- WHAT THE FIRM KNOWS More. The log of what people ask is kept, in your storage, and read back to you every month.
Shape the bot
Where it answers, what it may do alone, and who it hands to. The route recomposes around your answers — then send exactly that.
It answers.
It knows when to stop.
The engagement closes when the bot has handed over its first difficult thread and the person who received it had everything they needed.