We sell WhatsApp enquiry routing – so we run our entire business on it. Every contact form, every store order, every service enquiry on deskbees.com pings our team’s WhatsApp in seconds, backed by email. This is the in-house case study: the architecture, the alert map, and what instant response did to our own follow-ups.
The situation
Like every small business, we lived in the inbox: contact-form mails buried under newsletters, store orders discovered hours later, weekend enquiries answered Monday. For a company whose pitch is instant response, that was embarrassing – and it cost us the exact customers who contact three vendors and hire the fastest responder. The fix had to be our own product, running in production, visible to every prospect who asks “does it actually work?”
What we did
We wired every lead source to WhatsApp plus email: contact forms (Contact Form 7 mapped field-by-field into alert templates), store orders (new order, item and value alerts to the packing desk), and service-page enquiries – each with the customer’s number tappable for one-tap callback. Setup per integration: about ten minutes, following our own CF7 and WooCommerce recipe. Email stayed as the record-keeper; WhatsApp became the speed layer. Products used: our Unofficial gateway throughout – the same plugins we sell.
The alert map
Before vs after
| Moment | Before | After |
|---|---|---|
| Enquiry sent 9 PM | Sits in inbox till morning | Phone pings in seconds |
| Order placed | Discovered at next login | Packing desk alerted instantly |
| Callback | Number copied from mail | One tap from the alert |
What changed
Measured results (response time before vs after, enquiry volumes, from our logs with dates) will be published here once compiled. Try it yourself: send an enquiry via contact and watch how fast we reply.
Related services
WhatsApp gateway · Official API · Get it for your site
Case study published 20 September 2026. In-house system, fully verifiable on the live site.