WhatsApp Enquiry Handoffs for Owner-Run Dubai Businesses: Practitioner Notes

Description and use

A WhatsApp CRM for owner‑run Dubai businesses eliminates duplicate inquiries, respects reply windows, tracks ownership, and requires approval before sending price or appointment details, boosting trust and efficiency.

Problem

Owner-run Dubai businesses rely on simple tools like Google Sheets and phone for CRM, but lack robust WhatsApp enquiry handling, leading to trust issues and operational inefficiencies.

Outcome

The system reduced duplicate enquiries, ensured timely replies within WhatsApp’s constraints, and provided a clear approval step for sensitive messages, increasing owner trust and operational efficiency.

Workflow

• 1. Customer sends message on WhatsApp.
• 2. System receives webhook and checks for duplicate using provider message ID and object key.
• 3. If new, create enquiry record and assign to owner; if duplicate, upsert.
• 4. If message contains price or appointment info, flag for approval.
• 5. Owner taps approval button; system sends message via approved template if outside reply window.
• 6. Enquiry state transitions: new → owned → next_step_due → closed.
• 7. Unassigned enquiries appear in a visible "needs a human" list.

Evidence

On WhatsApp, once a customer messages you, you can reply freely for a limited window. Outside it, you need approved message templates.

Source

Treat every inbound event as possibly a duplicate. Use a stable key such as the provider message id plus the object it touches, and upsert instead of inserting.

Source

Free-text notes do not scale past a busy Saturday. If the system cannot confidently assign an owner, it puts the enquiry in a visible "needs a human" list. It never guesses.

Source

Anything mentioning a price, a discount, a delivery date or an available appointment slot waits for one tap from the owner or manager.

Source