Wakala — huduma kwa wateja
Customer support for a mobile-money agent: identity proved by code before any balance is shown, complaints filed with a reference, and the hard ones escalated with the whole thread attached.
This is the real thing
A messaging flow runs on the same engine that answers real customers, inside a transaction that is rolled back. Nothing is sent, nothing is written, no order is created.
- ✓ Masked steps still run — you see the reply, not how it was written
- ✕ Payments, SMS and calls are stubbed here
- ☎ The IVR is walked here — no real line is ever dialled
The seller left this much readable. The rest unlocks when you buy it — but every branch and every step kind is shown, so you can see what you are getting.
Agent support is mostly four conversations, and three of them should never need a person. Nothing about an account is said until the number is proved with a one-time code — the balance, the float, the last transactions. That single rule is the difference between support and a leak. What the customer wrote is classified first, so a complaint is never treated as a question. Questions go to your knowledge base; complaints are taken down properly, given a reference, filed over your own webhook and emailed to the desk that owns them. Anything genuinely hard reaches an AI agent with a short leash and a way out, and then a person — with the AI muted first, so nobody arrives to find the bot has answered again.