- 01
Market
Saudi Arabia
- 02
Written for
Head of CX, Commercial Director
- 03
Decision
Serve customers on WhatsApp without a queue of unanswered threads
- 04
Languages
EN · AR
The thread
What has to be remembered, and for how long
A voice call has one state and it ends. A thread has a state that persists across days and across staff, and the design question is what that state contains.
A messaging thread: first message, intent and work, a pause, resumption days later against the same state, then closure or handover to a person in the same thread.
- 01
First message
Identity resolved from the number where a record exists, and the thread linked to it so history is one conversation rather than several.
- 02
Intent, then the work
Order status, a booking, a document, a question. Each maps to a system lookup or a write, not to a scripted reply.
- 03
The pause
The customer stops replying mid-flow. The state is held, and what is allowed to be sent to restart it is decided by the platform's session rules rather than by the agent.
- 04
Resume, days later
The reply lands against the same state, so the customer continues rather than restarts. Losing this is the single most common defect in messaging deployments.
- 05
Close, or hand over
A person receives the whole thread, not a summary, and can reply in the same window the customer is already in.
To a person, in the same thread
Requested, or triggered by a complaint, a payment dispute, or repeated misunderstanding. The customer sees one continuous conversation; the change of who is answering is not their problem to manage.
Platform reality
Four constraints that are not negotiable
They come from the messaging platform rather than from the design, and a project that discovers them late redesigns the customer journey rather than the code.
- 01
You cannot message first, freely
Outside an open session, outbound contact uses pre-approved templates. Any journey that depends on reaching a customer proactively has to be designed around that constraint from the start.
- 02
Templates are reviewed, and change slowly
The wording you want may not be approved, and iterating on it is not instant. Treat the template set as a piece of the product with its own lead time rather than as copy written the week before launch.
- 03
Voice notes are normal here
A large share of Arabic messaging traffic is voice. An agent that only reads text will silently fail on a meaningful share of customers, and they will read that as being ignored.
- 04
The number is an identity
Business numbers accumulate history and reputation. Consolidating several departmental numbers into one agent is usually right, but it has to be planned rather than discovered when two teams answer the same thread.
Arabic on this channel
People write the way they speak, and switch scripts mid-sentence
Messaging Arabic is not the Arabic of a document. It is dialectal, abbreviated, frequently written in Latin characters, and mixed with English for anything technical. A system evaluated on Modern Standard Arabic will look excellent in testing and mediocre on the first day of real traffic.
So the evaluation set comes from your own inbox, including the messages that are hard to read, the voice notes and the ones with three words and a photograph. That set is also what tells you honestly where the handover threshold should sit.
Our role
What a messaging deployment involves
- 01
Platform setup done properly
Business account, number strategy, template set drafted for approval, and the session rules encoded in the journey rather than discovered in production.
- 02
Thread state that survives
Conversation state tied to the customer record, so a reply three days later continues the same piece of work and a handover does not reset it.
- 03
Evaluation on your own inbox
Built from real messages including voice notes and Latin-script Arabic, because that is the traffic the agent will actually meet.
Template approval and platform policy sit with the messaging platform; we design the journey so it works inside those rules rather than around them.
Common questions
What buyers ask
Can the agent start conversations with customers?+
Within the platform's rules, using approved templates and with the customer's consent on record. Notifications, reminders and order updates are normal uses. What is not available is free-form outbound messaging whenever you like, and any plan that assumes it will have to be redesigned.
Do we need a separate number, or can we use the one customers already message?+
Using the existing number is usually right, because it carries the history customers expect, but it is a one-way migration and it needs planning: everyone currently answering that number on a phone has to move into the shared inbox at the same time, or two conversations run in parallel on the same thread.
How does this sit with the phone line?+
Best when they share the same state. A customer who called yesterday and messages today should not be starting again, and the systems that make that possible are the customer record and the conversation store rather than the channel. Where the two are built separately, customers notice within a week.
In this cluster
Pilot it on one queue
One customer journey running on WhatsApp end to end, with the handover and the template set working before volume is pointed at it.
Start the conversation
