Customer Support · Customer-facing
Talks to your customers.
Reads from your library.
Embed Dokko on your site or in your product. The assistant answers from your help centre, policies, product docs, and release notes — branded as yours, isolated from every other tenant. Deployed across communal services, retail, tourist agencies, real estate, rentals, hospitality — wherever document AI needs to face the customer.
Overview
Generic chatbots invent return policies. The FAQ widget you shipped years ago can't keep up with your release cadence. Routing every question to a human doesn't scale; routing none of them costs you customers. Dokko reads your real documentation end-to-end and answers from it — and when the question is outside what the documentation covers, your operator steps in mid-conversation via live session takeover.
Where it shows up
The same engine, configured for every vertical.
We ship Customer Support across very different shapes of business — what changes per deployment is the document library, the brand chrome, and the Skills configured by the team that owns the assistant. The engine doesn't.
Communal services
- › "How do I report a damaged headstone?"
- › "What are the cemetery's opening hours?"
- › "Where do I pay this year's burial fee?"
Retail
- › "Can I return this if the packaging is open?"
- › "When will my order ship?"
- › "Do you have this in size medium?"
Tourist agencies
- › "Does the package include airport transfer?"
- › "Is the hotel pet-friendly?"
- › "Can I change my departure date?"
Real estate
- › "What's the deposit policy on this listing?"
- › "When can I tour the property?"
- › "Are pets allowed in this rental?"
Rental companies
- › "What's the late-return penalty?"
- › "Is the damage waiver included?"
- › "Can I extend my booking?"
Hospitality
- › "What time is check-in?"
- › "Can I cancel my reservation?"
- › "Is breakfast included in the rate?"
And the long tail beyond that — anywhere the customer's question has a real answer in the company's documents, and anywhere a generic chatbot would otherwise invent one.
Capabilities
What it does
Reads end-to-end
Answers drawn from your help centre, policies, product docs, release notes — cross-referenced and cited
Region-aware Skill
Skills shape every conversation — region-specific policies, refusal rules, structured lookups, the upgrade path your team wants surfaced
Closes the loop
Agents take multi-step actions — open the ticket, trigger the refund through your billing API, notify the on-call human in Slack
Live session takeover — operators watch sessions in flight and step in with a single click; the customer doesn't see a disconnect
Brand & isolation
Your embed runs on your domain, in your colours, with your name. The library it answers from is yours alone — no other Dokko tenant can read it, no other tenant's behaviour leaks into your responses. Conversation logs sit in your tenant. Audit trails belong to your team.
Editorial control
How your team stays in charge of every conversation.
Document-level citations
Every answer cites the source it drew from. When a customer asks where a claim came from — or your QA team audits a conversation — the answer points back to the document.
Grounded, not generated
The assistant answers from your library or it tells the customer it can't. Open-ended invention isn't a failure mode — the engine simply doesn't reach outside your indexed documents.
Live session takeover
Your operators watch sessions in flight and step in when they want to. The handoff is a single click; the customer doesn't see a disconnect or repeat themselves.
Audit log from Pro
Every question, every answer, every Skill that fired, every Agent action — time-stamped and exportable. Available from the Pro tier; retention configurable to your policy.
Get started
Read deep. Act fast.
On your documents.
The 14-day trial runs on your real library, not a sandbox. Bring your contracts, manuals, or frameworks — and see how Dokko reads them.