Chatbots: coordinate dialogue, knowledge and support
A chatbot helps when answers, boundaries and next steps fit together. The quote should describe the full conversation journey and information maintenance. Public assistance and internal knowledge search have different access and handover needs.
Bound the tasks and audience
Should the bot answer public questions, guide customers or help employees? Define topics, languages and excluded tasks. A fixed-answer menu and an AI-powered dialogue are different solutions. A chatbot should not silently become an agent executing orders or changes. Those actions require separate scope and approvals.
Maintain the answer sources
Identify approved pages, documents and knowledge for answers. Resolve outdated prices, conflicting rules and missing material first. Assign update owners. Internal information must respect each user’s access rights. Importing documents alone proves neither correct answers nor safe access.
Design clarification and boundaries
A useful dialogue briefly explains the bot’s role. It should ask relevant clarifying questions and acknowledge missing knowledge. Define topic changes, abandoned conversations and repeated failures. Request only information needed for the task. Users should not get stuck in loops or fabricated answers.
Plan a real human handover
If a person should take over, define triggers, destination and staffed hours. Live chat, callback requests and support tickets are different paths. Clarify necessary details and conversation excerpts to transfer. Provide an honest alternative outside staffed hours. A handover button alone guarantees neither availability nor resolution.
| Handover | Agree |
|---|---|
| Live chat | Staffing and conversation takeover |
| Callback | Necessary details and expected follow-up |
| Ticket | Destination system, context and feedback |
Coordinate channels, privacy and usability
Websites, apps and internal channels may offer different sign-in and integration options. Check each channel, including mobile devices and assistive tools. Clearly identify the bot and data use. Agree retention, deletion, access to transcripts and handling of unexpectedly entered confidential information.
Test the complete conversation journey
Use your own typical questions in every agreed language. Test missing answers, ambiguous wording, forbidden access and handover through to the destination system. Check that the bot ignores unauthorised instructions in messages or knowledge sources. Set separate acceptance criteria for answers and journeys. Content or model changes need appropriate retesting.
Compare setup and usage
The quote should cover conversation design, content preparation, channels, integrations, tests and training. Licences, messages or model usage, storage and maintenance may be additional. Conversations and messages are different quantities. Clarify included usage, overages, bounded retries and effective stops. None guarantees answer quality or a specific reduction in team workload.
| Cost item | Comparison point |
|---|---|
| Setup | Content, dialogue, channels and acceptance |
| Usage | Conversations, messages, models and overages |
| Support | Updates, checks and ownership |
Checklist and introduction
Name the audience, main topics, languages, channels and available answer sources. Add expected conversations and the desired human handover. Send no passwords or real confidential conversations. Proceed through content review, a bounded dialogue design, quote, pilot with test questions, documented acceptance and supported introduction with a maintenance owner.
Frequently asked questions
Must a chatbot use generative AI?
No. Fixed answers or guided flows may suit bounded questions.
Do documents alone make a ready knowledge base?
No. Check currency, conflicts, access and typical questions.
Is human handover included automatically?
No. Agree the channel, destination, staffed hours and transferred details.
Can the bot place orders?
Only with explicitly agreed integrations, permissions and approvals. Answering questions does not include this automatically.
Does every channel work the same way?
No. Check sign-in, handover and usability for the chosen channels.
Which recurring costs matter?
Depending on the solution: licences, usage, storage and content or system maintenance. Compare matching usage assumptions.
