Start with the conversation you want to improve
Separate customer support, sales qualification and internal knowledge search. A support assistant needs current policies and a clear escalation queue. A sales assistant needs agreed questions and a useful lead record. An internal assistant needs permissions so one team cannot retrieve another team’s restricted information. Pick one audience and one channel for the first release, then define what a successful conversation looks like.
- Which questions repeat each week?
- Which answers need a source or a staff decision?
- What information may the assistant collect?
- Who receives a handover, and during which hours?
Test your knowledge before choosing a model
Collect representative questions with approved answers and their source documents. Include missing information, conflicting policies and outdated content. The assistant should ask a useful clarification or admit that the source does not answer the question. Changing a model cannot fix an unmaintained knowledge base. Assign someone to approve content updates and test whether changes reach the assistant. Keep a record of failed answers and repeat the evaluation after a model or prompt change.
Compare website and WhatsApp delivery
A website assistant gives you control over the page experience. WhatsApp adds a messaging channel with its own account, integration and messaging requirements. Confirm the current WhatsApp Business Platform rules and provider charges for the intended use. An existing personal number does not automatically provide a production integration. Test how conversations, consent choices and staff replies stay consistent when a person changes channels.
| Decision | Website chatbot | WhatsApp integration |
|---|---|---|
| Entry point | Your website pages | An approved business messaging setup |
| Team handover | Support inbox or CRM connection | Supported staff inbox and message routing |
| Cost drivers | Hosting, model usage and integration | The same costs plus messaging/provider charges |
| Acceptance test | Mobile use, sources and fallback | Delivery failures, permissions and human takeover |
Test the languages your customers use
For Malaysia, validate the English, Bahasa Malaysia and Chinese questions relevant to your audience. For Singapore, confirm the actual customer language mix rather than assuming English alone. Include short messages, spelling mistakes, local product names and mixed-language questions. Ask a competent reviewer to assess accuracy and tone in every supported language. Only advertise a language after the agreed evaluation passes. The preview language options are not proof of a deployed model’s multilingual quality.
Define handover, access and the operating cost
Before launch, test a request for an exact quotation, a complaint, a restricted record and an unavailable backend. Define when the assistant may draft a response, retrieve data or take an action. Sensitive changes should have explicit permission and a review step. Ask for implementation costs separately from hosting, model usage, messaging and maintenance. Agree retention, access, export and support responsibilities in the proposal. Begin with a supervised pilot and compare resolved questions, incorrect answers and successful staff handovers against the baseline.