What this covers
A chatbot that answers from your approved information, says when it isn’t sure, and hands off to a person.
Tools
Retrieval, Model APIs, Web chat UI, Session handling. The exact stack depends on what you already use.
Where it helps
- Product help based on your own documentation
- Help for new staff during onboarding
- Guiding people to the right service before a person takes over
We agree what “done” means before work starts.
What you get
- A chatbot that answers from your approved content
- A handoff to your existing contact channel
- Source code, setup notes and an agreed definition of done
The final list depends on the agreed scope. The estimate and schedule follow from it.
Data and security
Chats are kept only as long as needed, private conversations are protected, and public information is kept separate from logged-in account data.
How I work on it
Collect common questions, decide what the bot may answer, prototype the search and chat screen, test unclear questions, then pilot it while watching handoffs.
What helps me get started
- A short description of the process and who uses it.
- Sample data, any API documents, and what access is available.
- How much it will be used, who reviews the work, and your release priorities.
A short outline is enough for a first call. Please send sample data, not real records or passwords.
Related services
Read the planning guideQuestions
Will the chatbot always be right?
No. We test it on known questions, show sources where useful, and have it say so when it doesn’t have enough information.
How do you price the work?
I look at the workflow, the systems involved, the access needed and what “done” means, then send an estimate. If there are big unknowns, we start with a short discovery or a prototype.