WhatsApp automation connected to a CRM pipeline for a Riyadh service business

The starting point

The company provides maintenance and installation services to households and small businesses across Riyadh. Almost all new business arrived through WhatsApp — from referrals, from a Google Business listing and from social media — but it arrived on whichever personal number the customer happened to have. Coordinators forwarded jobs to technicians by message, quotes were typed by hand, and nobody could answer the owner's simplest question: how many enquiries did we get last month, and how many became jobs?

The owner had already tried a CRM once. It failed because staff had to copy conversations into it manually, which nobody did after the first week. Any new system had to capture the conversation automatically or it would not be used.

Moving to the WhatsApp Business API

The first step was structural: one verified business number on the WhatsApp Business API, with the coordinators working from a shared inbox instead of their own phones. Personal numbers were kept alive for a transition period with an automatic reply pointing customers to the business number. The distinction between the free WhatsApp Business app and the API — and why a multi-agent team needs the latter — is explained in our WhatsApp automation guide for Saudi businesses.

Templates were deliberately kept to a small set: enquiry acknowledgement, appointment confirmation, reminder the day before, and a post-service follow-up. Each existed in Arabic and English and was approved once. Marketing broadcasts were explicitly out of scope for the first phase; the goal was to stop losing enquiries, not to send more messages.

The qualification flow

When a new conversation starts, the flow greets the customer in the language of their first message and asks three things: the type of service, the district, and the preferred time window. The answers are enough for a coordinator to quote or schedule without a back-and-forth, and they are written to the CRM before a human ever opens the conversation.

Connecting the conversation to Bitrix24

Bitrix24 was chosen because the company needed a pipeline, task assignment and a shared calendar for technicians without a large licence commitment, and because its open channels and REST API made the WhatsApp integration straightforward. The pipeline stages were taken from how the business actually works — enquiry, quoted, scheduled, completed, follow-up — rather than from a generic sales template. Our approach to this configuration is described on the Bitrix24 CRM service page.

• Contacts are matched by phone number, so a returning customer is never duplicated.
• A deal is created from the flow's answers with service type, district and time window as fields, not free text.
• Stage changes made by the coordinator trigger the corresponding template — confirmation, reminder, follow-up — without the coordinator retyping anything.
• The full conversation is logged on the deal timeline, which is what made the CRM stick this time.

A lightweight reporting export to a shared spreadsheet gave the owner a weekly view of enquiries by source, conversion by stage and first-response time, without building dashboards prematurely. The same pattern — automate the capture, keep humans on judgement, report simply — underpins our broader business process automation work.

Getting the team to use it

Adoption was treated as part of delivery, not an afterthought. Coordinators were involved in writing the qualification questions and the handover rules, which meant they trusted the flow when it went live. Training took place on real conversations in the shared inbox rather than on slides. A short set of response guidelines — tone, expected reply time, when to call rather than message — was agreed and pinned in the inbox.

The transition period for personal numbers was fixed in advance and communicated to regular customers. When it ended, the auto-reply on personal numbers remained for a further period as a safety net.

What we would repeat on the next project

• Write the handover rules before the flow, with the people who will handle the handover.
• Keep the template set small and bilingual; approval friction drops and consistency improves.
• Make the CRM record automatic — if staff must copy conversations, the CRM will fail.
• Match pipeline stages to real operations, not to a sales textbook.
• Report simply first; dashboards can follow once the data is trusted.