The Email Enquiry Problem

A UK trades business with a Google Ads budget of £800/month was generating approximately 35 enquiry form submissions per week from their website. Of those 35, an average of 3-4 resulted in booked jobs. That’s an 11% conversion rate — which sounds reasonable until you account for the other 31 enquiries that went silent.

Where did they go? Follow-up calls revealed a consistent pattern: the enquiry was submitted outside business hours, the business owner saw it the next morning, called twice without answer, and moved on. Meanwhile the prospect had called three competitors and booked one of them.

The direct cost of the broken enquiry process was measurable: £800 in Google Ads spend generating enquiries that died because the response was 12+ hours late.

The solution was a WhatsApp Business API integration that delivers enquiries as instant messages, with automated acknowledgement and routing.

Why WhatsApp Over Any Other Channel

The channel decision was based on empirical evidence from the target market, not assumptions.

UK trades businesses — electricians, plumbers, heating engineers, builders — communicate via WhatsApp. Not email. Not phone calls (until they’re ready to book). WhatsApp. The tradespeople I spoke to during research all said the same thing: “If someone wants to contact me about work, they WhatsApp me. If they email, I probably don’t see it for days.”

This is not a generational thing. It’s a practical thing: tradespeople are on site all day with their phone in their pocket. They’re not checking email on a laptop. WhatsApp notifications are immediate and unavoidable.

The WhatsApp Business API adds the capability to receive messages programmatically and route them through a proper business system rather than a personal phone, while preserving the consumer-facing WhatsApp experience that customers prefer.

The Routing Logic

The routing system handles three primary scenarios:

Single tradesperson businesses — The simplest case. All enquiries route directly to the business owner’s WhatsApp, with an automated first-response template that acknowledges receipt and sets expectations: “Hi [name], thanks for getting in touch about [service]. I’ll be able to look at your job properly this evening and get back to you with availability. If it’s urgent, call me on [number].”

Multi-trades businesses — A heating and plumbing company with three engineers covering different specialities. Enquiries for boiler jobs route to Engineer A, drain unblocking to Engineer B, general plumbing to Engineer C. The routing is based on keyword matching in the enquiry: “boiler”, “heating”, “gas” → Engineer A; “blocked”, “drain”, “clearance” → Engineer B; everything else → Engineer C.

Multi-location businesses — A facilities management company with engineers based in three cities. Enquiries are routed to the nearest available engineer based on postcode matching, with a fallback chain if the primary engineer doesn’t respond within 15 minutes.

The routing logic is configured via a simple JSON rule file that business owners can update themselves without touching code:

{
  "rules": [
    { "keywords": ["boiler", "heating", "gas", "radiator"], "route_to": "engineer_a", "city": "london" },
    { "keywords": ["blocked", "drain", "clearance"], "route_to": "engineer_b", "city": "london" },
    { "default": { "route_to": "dispatch", "round_robin": true } }
  ],
  "fallback_timeout_minutes": 15,
  "fallback_chain": ["engineer_a", "engineer_b", "dispatch"]
}

Multi-Admin Failover

The single biggest operational risk with a WhatsApp lead routing system is the primary admin being unavailable. If the business owner is on holiday and their phone is off, enquiries still need to be handled.

The multi-admin failover system maintains a chain of responsibility. Each enquiry has a 15-minute acknowledgement window. If the primary admin doesn’t acknowledge (or explicitly defer) the enquiry within 15 minutes, it’s automatically escalated to the next admin in the chain.

The acknowledgement mechanism is deliberate: the system won’t escalate automatically if the primary admin has seen the message but is in the middle of responding. It escalates on silence. This prevents false escalations when an admin is actively managing a conversation.

The escalation message to the next admin includes the full conversation history so they can pick up seamlessly: “This enquiry came in at 09:42, [owner] hasn’t responded. Escalating to you.”

Template Message Approval Workflows

WhatsApp’s Business API has strict rules about message templates. Templates must be pre-approved by WhatsApp before use, and they must follow specific formatting guidelines. Businesses can’t send arbitrary free-form messages to customers who haven’t Opted In — they must use approved templates for automated first contact.

The system includes a template management workflow: business owners define templates in the admin interface, the system validates them against WhatsApp’s formatting requirements (no variable placeholders in the wrong format, no promotional language in appointment-reminder templates, etc.), and submits them for WhatsApp approval.

Template status is tracked: Draft → Submitted → Pending Review → Approved → Active → Rejected (with reason). Business owners see their template status and know exactly why a rejected template was rejected.

The most commonly used templates in practice:

  • Initial enquiry acknowledgement (auto-sent within 60 seconds of message received)
  • Appointment reminder (24 hours before booked slot)
  • Quote follow-up (48 hours after initial enquiry with no response)
  • Job completion confirmation
  • Request for review / testimonial

The Instant Response Conversion Impact

The measurable results from the pilot business:

  • First response time: from 12+ hours (email) to under 90 seconds (WhatsApp)
  • Enquiry-to-booked conversion: from 11% to 31% — nearly 3x improvement
  • Revenue attributed to formerly-lost enquiries: £18,400 in the first 3 months (based on average job value × enquiries that would previously have gone unanswered × 3x conversion improvement)
  • Google Ads cost per booked job: from £228 to £86 — the improved conversion rate means each Google Ads pound generates more booked work, so the effective cost per acquisition dropped even though the spend remained the same

The conversion improvement is the headline number, but the efficiency story is equally important. The tradesperson no longer spends Monday morning processing a backlog of emails. Enquiries arrive during working hours as WhatsApp messages, are handled immediately, and the conversation happens in the same WhatsApp thread they use for everything else.

What the Technical Build Taught Me

The most complex part of the integration wasn’t the WhatsApp API itself — it was handling the non-deterministic nature of real-world message conversations. A customer doesn’t always respond to the acknowledgement message. They might ask a follow-up question three days later. They might forward the message to someone else in their household. They might reply from a different phone number.

The system stores the full conversation thread with a canonical customer identifier that persists across multiple phone numbers, email addresses, and message channels. If Customer A sends an enquiry from their phone and then their spouse replies from a different number, the system recognises them as the same customer and attaches the response to the original enquiry record.

The second complexity was handling WhatsApp’s rate limits. WhatsApp enforces per-second and per-day message limits on Business API accounts. The system implements a message queue with rate-limit awareness — it tracks recent message volume and holds non-urgent messages (quote follow-ups, review requests) when the account is approaching its daily limit, then releases them when the limit resets.

This required careful integration with WhatsApp’s webhook system to track outbound message delivery status in real-time and update the queue accordingly.