The chatbot responds quickly, but customers still have to call
This case is drawn from Thu Thi Ecom's chatbot implementation for a retail chain. The organization's name and sensitive data are withheld by agreement with the person responsible.
Context
The chatbot responded to customers almost immediately, but the sales team still received many calls repeating questions already addressed in the chat flow. This shows that response speed had not yet created a complete problem-solving experience.
How the implementation team identified bottlenecks
Rather than simply adding more answers, the team reviewed customers' actual intent, the order of questions, the data used in responses, escalation conditions and the information retained when handing off to an employee. The goal was to prevent customers from having to start over.
Operational lessons
Automation is valuable only when it brings customers closer to a result. A chatbot must know when it can resolve a request on its own, when it needs more information and when it should hand off to a person with enough context.
Disclosure scope
The case is shared with the consent of the person responsible at the business. The website does not disclose the organization's name, customer data or internal metrics.