Envoy
An assistant that has read your documentation is a colleague. One that has not is a complaint generator.
- 100%
- Answers carrying the source they came from
- 1
- Refusal path, for when the answer is not there
- 0
- Releases shipped without an evaluation set
The problem
Nearly every question a support team answers has been answered before, in writing, often by someone who has since left. The generic assistant bolted onto a website cannot see any of it, so it invents policy.
What we did
- 01
Every answer grounded in your own material, with the source cited so a reader can check it in seconds.
- 02
The evaluation set is built from real historical questions before the assistant is.
- 03
A refusal path. When the material does not support an answer it says so and routes to a person.
- 04
Put where the conversation already happens: the helpdesk, the site, or WhatsApp through Verse.
Where it landed
The repeated question stops reaching a person, and the unusual one arrives with the context already attached. Tone, scope and escalation rules are yours to set.
Built with
- Python
- pgvector
- Claude
- Evaluation harness
- Helpdesk APIs