Platform
Not a chatbot with a script. An agent with a job.
A scripted bot breaks the moment somebody asks a question you did not anticipate. This one understands what was asked, checks what it is allowed to do about it, does it, and tells you when it could not. Here is exactly how that is put together.
= one agent, doing a real job
Anatomy
Five things make up an agent.
Every one of them is written in plain language, and every one of them is yours to change. There is no code anywhere in this.
01 / Knowledge
What it knows
Your website, policy documents, price lists, product catalogue, FAQs and past conversations. It answers from your material, not from the open internet, so it cannot invent a policy you never had.
02 / Instructions
Who it is
Its role, its tone, how formal it should be, what it calls your products. This is where your brand voice lives, and it holds across all eight channels.
03 / Procedures
The steps it follows
Numbered steps in ordinary sentences. Greet, identify the request, ask for the application number, check eligibility, confirm. It follows them in order, every time, without getting tired at four in the afternoon.
04 / Guardrails
What it must never do
The list of things it will not promise, will not discuss and will not decide. When a conversation reaches one of those lines, it stops and hands over rather than improvising.
05 / Actions
What it can actually do
Look up an order, check an application status, book a slot, create a ticket, send a document. Answering is useful. Doing the thing is what makes customers stop phoning.
The path of a message
From a message at 22:40 to a closed ticket.
This is what happens on every conversation, on every channel, whether a person is watching or not.
01
Arrives
A customer writes on WhatsApp. The agent detects the language and picks up the thread history if there is any.
02
Understands
It works out what is actually being asked, which is rarely what was literally typed, and matches it to a procedure.
03
Acts
It answers, looks something up, collects an ID number or requests a document. Whatever the procedure calls for.
04
Routes
A ticket is created in the right department pipeline with everything already attached. Nobody rekeys anything.
05
Closes or hands over
Most conversations end here. The rest land with a named person, in the same thread, with the full history.
What your team works in
The agent handles the volume. Your people handle the exceptions.
One queue, agent and humans together
Every conversation across every channel lands in the same helpdesk, tagged by department and status. Your team is not switching between a WhatsApp phone, an inbox and a spreadsheet.
- Tickets routed into department pipelines automatically
- Status, owner and last update visible on every one
- Departments discuss a ticket inside it, not over email
Step in without starting over
When a person takes over, they arrive in the same conversation the customer is already in. The customer is not asked to repeat their name, their number or their problem, which is the moment most support experiences fall apart.
- Full history and collected details already on screen
- Agent pauses while a person is in the thread
- Hand it back once the exception is dealt with
Documents collected in the chat
Customers send an ID, a payslip or a proof of address straight into the conversation. Files are filed against the right record and the right ticket, so nobody is searching a phone gallery for a photo of a document.
- The agent asks for what is missing and chases it
- Stored against the customer, not in a shared inbox
- Retention and access handled the way POPIA expects
What customers are actually asking
The reporting is not there to make the agent look good. It is there to show you which six questions are eating your week, where the agent is escalating too often, and which topic is growing before it becomes a problem.
- Topic volumes and how they move week to week
- Resolution rate and every reason it escalated
- Sentiment, so you see frustration building early
Integrations
It can reach into the systems you already run.
Order lookups, application status, bookings, stock. If your system has an interface, the agent can be given an action that uses it. If it does not, the agent still answers from your documents.
Who does what
You are not building this yourself.
Plenty of platforms sell you a builder and wish you luck. This is a done for you build, and here is the honest division of labour.
| Stage | We do | You do |
|---|---|---|
| Knowledge | Pull in your site, documents and past conversations, structure them and fill the gaps. | Point us at what exists and tell us what is out of date. |
| Procedures | Write the steps and the escalation rules with you, then test them against real scenarios. | Tell us how you actually handle each request today. |
| Guardrails | Turn your rules into limits the agent cannot cross. | Tell us what must never be said or promised. |
| Channels | Set up and verify the WhatsApp Business number and connect the rest. | Confirm the business details Meta requires. |
| Go live | Run it in test, then live, and watch the first weeks closely. | Have someone available for escalations. |
| Ongoing | Review escalations, tune the agent and report on what changed. | Tell us when your prices, policies or hours change. |
Underneath
Built on infrastructure that has been audited.
SOC 2 Type II infrastructure
The platform we build on has passed an independent SOC 2 Type II audit for security and availability.
POPIA aligned
Consent, purpose and retention handled properly, with a record of what was collected and why.
Never used for training
Your conversations and documents train your agent alone. They are not fed into public models.
Official WhatsApp API
A verified Business number registered to you, not an unofficial workaround that gets shut down.
See it on your own questions
Send us the six questions
your team answers all day.
We will show you the agent handling them before you commit to anything. No meeting, no slides, just the thing working on your material.