Digitalisimo
Service continues after purchase confirmation
Once customers buy, their questions change: has the order been prepared, where can it be tracked and how can an issue be resolved? A WhatsApp chatbot can organise those enquiries and direct them appropriately when it has reliable information or a clear handover route.
For a shop selling in Bogotá and shipping to other Colombian cities, distinguish general delivery questions from questions about an individual order. This helps define automatic answers and cases needing system access or human review.
Use statuses with a shared meaning
Order received, payment verified, preparation, dispatch and delivery are different stages. The bot should not announce that a parcel is on its way when only a label exists or the warehouse has not handed it to the carrier. Document the source confirming each status.
Without an operational connection, explain how to check the reference or register a request for the team. An honest next step is more useful than an unsupported update. Customers need to understand what is happening rather than receive a message for every internal movement.
Check orders without exposing unnecessary information
Before showing purchase details, define how the person's authority to access them is checked. Avoid revealing addresses or other customers' information in generic responses. Design verification with the business's security and privacy owners.
Request only what is needed to resolve the enquiry and avoid routine requests for sensitive documents. If verification cannot be completed, hand over to the appropriate service channel. Integrations need scope-limited permissions and a record of failures requiring review.
Recognise cases needing a person
Failed delivery, a damaged item or an exchange request may need judgement and additional information. The bot can collect a reason and explain the published procedure, but should not authorise undefined compensation.
If offering cash on delivery, distinguish an attempted delivery from a completed sale. Organise cases with dispatch and customer service owners. Preserve the reference, reason and prior answers when an agent takes over so the customer does not need to repeat everything.
Send updates customers can use
A useful update communicates a confirmed status and next step. Avoid repeated messages that add no information. Define communications and permissions, and review current WhatsApp requirements before enabling notices outside a customer-initiated conversation.
Assess channel and provider conditions and costs within the project budget. Building a flow does not provide unlimited messaging. Keep a human support option and a response schedule the team can sustain.
Evaluate whether tracking becomes easier
Review whether people find the correct status, which enquiries return to the same point and which incidents reach the team without context. Test changes with example orders and error scenarios clearly labelled as tests. Do not use actual customer data in a public demonstration.
Expand once sources, permissions and handovers work. The after-sales goal is to help customers understand their purchase and resolve problems. Automation adds value when it makes that journey easier and allows a person to intervene when needed.