Chatbot and LLM Apps
We build chatbots and other LLM applications grounded in your help center, product data, or internal docs, with a path to a person.
The problem
A widget with no sources will sound sure and be wrong. Support then spends the afternoon undoing it. The fix is not a friendlier prompt. It is approved content and a refusal policy.
We define the topics the assistant may answer, the content it may cite, and the topics that always go to a person. Staff tools and customer tools are different products and we do not blur them.
What you get
Grounded assistant
Answers drawn from a corpus you can edit, not from the open web by default.
Sources
A link or citation when showing where an answer came from helps the reader.
Handoff
A clear exit to email, a ticket, or a person for anything outside policy.
Evaluation set
Questions you care about, with the expected behavior, so later changes can be checked.
How the work runs
01
Collect the corpus
Help articles, policies, or product facts. Stale pages are removed before launch.
02
Write the boundaries
What it must not answer: pricing exceptions, legal, medical, account-specific secrets.
03
Build the interface
The chat or embedded assistant matches the product, including the empty and error states.
04
Score it
We review misses with you and adjust retrieval and copy before a wide release.
Stack
- LLM APIs
- Retrieval over your documents
- Your site or app as the host
- Analytics on unanswered questions
Who it is for
- Support teams with a documented help center
- Product companies adding an in-app assistant
- Internal teams that want answers from their own wiki