WhatsApp Guides
WhatsApp message templates for service businesses
Six messages most service businesses send every week, written to be clear, short and polite.
The six messages
| Message | Example |
|---|---|
| Booking confirmation | “Your AC service is booked for Thursday, 10:00 to 12:00. Reply here if anything changes.” |
| Arrival window | “Ahmed is on the way and should arrive in about 20 minutes.” |
| Quote follow-up | “Any questions on the quote? We have a slot on Saturday morning.” |
| Job completed | “The work is complete. Your report and photos are here: [link]” |
| Payment reminder | “A friendly reminder that invoice INV-2207 is due. You can pay here: [link]” |
| Review request | “Thank you for choosing us. Would you share a short review? [link]” |
How approved templates work
- Within 24 hours of the customer’s last message, you can reply freely.
- Outside that window, only approved templates can start a conversation.
- Templates use placeholders for names, dates, amounts and links.
- Customers must have agreed to receive messages from your business.
Write each template in English and Arabic and send the customer the language they used with you.
Writing templates in Arabic and English
- Write each template naturally in both languages, not as a word-for-word translation.
- Keep names, dates, amounts and links as placeholders so they fill in correctly in either language.
- Use Western digits for amounts and invoice numbers, which customers can copy easily.
- Keep the tone the same in both languages: polite, short and specific.
Send customers the language they wrote to you in. A customer who messaged in Arabic and receives an English reminder notices.
Six more messages worth writing once
| Message | Example |
|---|---|
| Running late | “Ahmed is running about 30 minutes late due to traffic. Sorry for the wait.” |
| Visit moved | “Your visit has moved to Thursday, 15:30. Reply here if that does not suit you.” |
| Deposit request | “To confirm the booking, please pay the deposit here: [link]” |
| Access check | “Tomorrow’s visit: is the gate code the same as last time?” |
| Maintenance due | “Your AC service is due next month. Shall we book a time?” |
| Thank you after payment | “Payment received, thank you. Your receipt is here: [link]” |
Tone that works for UAE customers
Customers in the UAE write in Arabic, English and often a mix of both, and they notice when a message feels careless. Good service messages are polite without being stiff, specific about times and prices, and short enough to read on a phone in a car park. A greeting helps, especially in Arabic, but long introductions do not.
- Name the day and time; avoid “soon” or “later”.
- Put the most important fact first: time, price or action.
- Use the customer’s name when you have it.
- Avoid capital letters, exclamation marks and emojis in operational messages.
Rolling templates out to the team
Templates only help if the team actually uses them. Keep the list short, name each template by when it is used rather than what it says, and review them after a month: remove the ones nobody sends and fix the ones customers reply to with questions, because a question usually means the message was unclear.
Automations can send confirmations, reminders and follow-ups at set times, so the team only writes the messages that genuinely need a person.
Mistakes that make templates backfire
A template sent at the wrong moment does more harm than no message. The most common mistake is automation without context: a payment reminder going to a customer who paid in cash yesterday, or a “how was your visit?” message after a visit that was cancelled. Every automated message should depend on the real state of the job or invoice, not on a date alone.
- Sending reminders for invoices already paid in cash.
- Using an English template for a customer who always writes in Arabic.
- Promising an exact arrival time the technician cannot keep.
- Leaving placeholder text like [name] unfilled.
How to tell whether templates are working
You do not need a dashboard to judge templates. Three questions are enough after a month. Are customers replying to confirmations with “yes” or with questions? Are fewer customers calling to ask where the technician is? Are unpaid invoices being paid after the first reminder rather than the third? If the answer to any of these is no, rewrite that one template and check again the following month.
Frequently asked questions
How long does template approval take?
Approval is handled by WhatsApp and is usually quick for plain service messages. Avoid promotional wording in operational templates.
Can templates go out automatically?
Yes. Confirmations, reminders and follow-ups can be sent by automations at the times you choose.
Can we send promotions with these templates?
Keep operational templates operational. Promotional messages follow different WhatsApp rules and need the customer’s agreement to receive marketing.
Should we mix Arabic and English in one message?
Usually no. Send one language, matched to the customer, and keep amounts and invoice numbers in Western digits so they are easy to copy.
How many templates should a small team start with?
Start with the six core messages: confirmation, arrival window, quote follow-up, completion, payment reminder and review request. Add the others only when the same message has been typed by hand more than a few times in a week.
Can technicians send templates from the field?
Messages such as “on my way” and “job complete” work best when they are triggered by the job state the technician updates, so the technician does not have to type anything.