Situation
A multi-staff service business in Riyadh (clinic-style: appointments, packages, bilingual enquiries) received most demand on personal and shared WhatsApp numbers. Ads and Google Maps worked. Staff answered when free. When the main phone holder was offline, on leave, or buried in groups, warm enquiries went cold.
Leadership could not answer basic questions: how many new enquiries this week, who owns each thread, which sources convert, and which leads never got a second reply.
Friction
- Personal numbers with no backup or rota
- No single log — history lived inside chat threads
- No source tags (ads vs Maps vs referral)
- No first-reply SLA; evening peaks often missed
- Website WhatsApp button pointed at one person with no handoff
Buying more traffic would have amplified the leak. The fix was operational structure behind WhatsApp, not a new chat app.
System built
Viewkeeper scoped a VK Leads-style path: keep WhatsApp as the conversation layer; add capture, log, owner, and follow-up behind it.
1) Capture — Landing and Maps CTAs open WhatsApp with a prefilled first message (service + city). Optional short form for people who prefer not to chat first. Bilingual first reply (AR/EN) with hours and next step.
2) Log — Every enquiry lands in a shared sheet/CRM row: timestamp, source, phone, intent, status. Chat stays on WhatsApp; the row is the system of record.
3) Owner — Named owner or daily rota. New rows notify the owner. No “someone will reply” ambiguity.
4) Follow-up — Reminder if status stays “new” past the agreed window (e.g. same business day). Weekly review of new / contacted / booked / lost.
5) Light reporting — Counts by source and owner so leadership sees volume without opening every chat.
Results (operational outcomes)
We frame outcomes as process changes, not invented conversion percentages:
- Response ownership clear — every open lead has a named owner or rota slot
- First-reply discipline — team can measure time-to-first-reply against a stated SLA instead of guessing
- No silent drop-offs in the log — unanswered rows surface in reminders instead of vanishing in personal chat
- Source visibility — ads vs organic vs referral can be compared without scraping chat history
- Handoff safe — leave or shift change does not orphan the number
Hypothetical illustration only (not a measured client claim): if a team previously lost several warm chats per week to missed follow-up, a logged owner + reminder loop typically recovers those conversations before they go cold. Real numbers depend on volume, hours, and offer.
Package callout — VK Leads
Opening range for this shape of work is typically 4,500–7,500 SAR project fee, about 2–3 weeks after a short scope call, depending on integrations (sheet vs CRM, form vs WhatsApp-only). Riyadh studio · KSA and GCC delivery.
Related playbook: WhatsApp lead systems for Riyadh teams.