
On this page
Most service businesses end up with both WhatsApp and SMS, usually by accident. The front desk uses WhatsApp because customers reply there, and the booking system sends SMS because that is what it was built with.
The customer then gets two threads from the same business, and replies to whichever one they saw last.
Decide the default
Pick one channel as the default for automated messages, and use the other for a specific reason.
A sensible split:
- WhatsApp for anything with a reply: confirmations, reminders, quote follow-ups.
- SMS for anything that must arrive on any phone: one-time codes, fallback when WhatsApp fails, customers who asked for SMS.
Write the rule down. “Whatever the front desk feels like” is not a rule.
Use one number if you can
Two numbers for one business is confusing. If your provider supports WhatsApp on the same number you already use, do that.
If you must have two, make the WhatsApp one the main published number, and mention the other only in messages the customer is already expecting.
Consent is not optional
WhatsApp has stricter rules than SMS in most markets, and both have rules that vary by country.
Before connecting anything, decide:
- Where consent is captured, and how it is recorded.
- What the opt-out instruction says.
- Who checks that the list is clean.
A customer who never agreed to WhatsApp messages, receiving one from a business number, is a complaint waiting to happen.
Templates, written once
Both channels work better with approved templates for the messages you send most:
- Booking confirmation
- Reminder with confirm and reschedule
- Quote sent
- Payment link
- Review request
Write them, get them approved where the platform requires it, and keep them short. Long templates get truncated and look broken.
The fallback rule
This is the part most setups miss. If a WhatsApp message fails to deliver, what happens?
Options:
- Retry once after an hour.
- Fall back to SMS.
- Create a task for the front desk to call.
Pick one, and make sure the failure is visible somewhere. A message that silently fails is worse than one that was never sent, because everyone assumes it arrived.
Test before you go live
Send every template to your own phone, on both channels, at the time of day it would normally go out.
Check:
- Does it arrive from the right name?
- Is the link clickable?
- Does a reply land in the shared inbox?
- Does the opt-out work?
Then test a failure: put the phone in aeroplane mode, send, and see what the system does.
Keep the conversation in one place
The customer does not care which channel they used. The team should not have to either.
Every message, on either channel, belongs in the same thread on the same record. If the reply to a WhatsApp message sits in a different inbox from the SMS reply, someone will miss one.
What to tell customers
One line on the booking page is enough: “We’ll confirm by WhatsApp, and text you if we can’t reach you there. Reply STOP at any time.”
That sentence prevents most of the confusion, and it makes the opt-out easy to find.
Where BittaFlow fits
BittaFlow connects WhatsApp and SMS to the business number, keeps both in the shared inbox, and applies the fallback rule you set. Delivery failures appear as tasks rather than disappearing.
Connect both, then write the rule for which is which.


