Connecting WhatsApp + SMS to StudioOps

Sometimes the email goes to spam. Sometimes the customer just lives on their phone. WhatsApp and SMS solve both. StudioOps doesn't host its own messaging — instead you sign up for Twilio (the messaging provider) once, do a short onboarding, and paste a few credentials into StudioOps. From then on every "Send booking link" button gets a WhatsApp sibling, and reminders can go by SMS too.

This guide walks every step. It looks long because we've covered each click; the actual work is about 30 minutes of your time spread over 2-3 calendar days (most of which is Meta + Twilio approving your account in the background).

Why Twilio and not just StudioOps? Twilio is a registered Meta Business Solution Provider. They handle the Meta paperwork on your behalf — you never have to open Meta's Business Manager. Each studio brings their own Twilio account so customers see your business name on every message, not StudioOps. You pay Twilio directly for the messages you send (UK rates: ~GBP 0.04 per SMS, ~GBP 0.03-0.05 per WhatsApp conversation).

What you'll need before you start

• A bank card (Twilio takes a GBP 5 minimum deposit to activate the account)
• A copy of your business registration (Companies House registration is fine, sole-trader proof of address works too)
• 30 minutes of focused time, split roughly: 5 min Twilio signup, 15 min WhatsApp Sender + business verification, 5 min template submission, 5 min pasting credentials into StudioOps
• 2-3 business days of patience for Meta to approve

1. Sign up for Twilio (~5 min)

1. Go to twilio.com → click Sign up.
2. Enter your real business email (not a Gmail), full business name, and a strong password. Twilio uses these for billing + support contact later — keep them sensible.
3. Verify your email (Twilio sends a code).
4. Verify a mobile number (Twilio sends an SMS code).
5. Twilio asks a few setup questions ("What do you want to build?" → pick Send a notification, "Which language?" → No code, "Do you write code?" → No). These choices don't lock you in — they just route the onboarding UI.
6. Add GBP 5 of credit to activate. Twilio gives a small trial balance to start; GBP 5 covers ~100 SMS or ~150 WhatsApp conversations.

You should now be in the Twilio Console. The two values you'll need later live at the top of the dashboard:

• Account SID (starts with AC)
• Auth Token (click to reveal — 32 random characters)

Don't paste these into StudioOps yet — finish the next two steps first.

2. Set up a WhatsApp Sender (~15 min active, then 1-3 days of waiting)

This is the part where Twilio talks to Meta on your behalf so you don't have to.

1. In the Twilio Console, go to Messaging → Senders → WhatsApp senders → New WhatsApp Sender.
2. Twilio asks for the phone number you want to use for WhatsApp. Two options:
   • Use a number you already own (Chayil Couture uses its existing business mobile here, for example). The number can't be currently active on personal WhatsApp — if it is, you'll need to deactivate it on the consumer app first, OR pick a different number for business.
   • Buy a fresh Twilio number in Twilio's checkout (~GBP 1/month). Cleaner separation but customers won't recognise the sender.
3. Enter the business details Twilio asks for: legal business name, display name (what customers will see on WhatsApp — keep it identical to your studio name), business category (pick the closest fit), website (your StudioOps booking page works: studioops.uk/your-slug/book), business description (one-line plain English).
4. Submit for review. Twilio passes this to Meta. Status will read Pending review.
5. While you wait (typically 1-3 business days), set up the SMS Sender if you want SMS too. Messaging → Phone numbers → Manage → Active numbers → Buy a number for a UK SMS-capable number (~GBP 1/month). Pick one that's nearby geographically — UK customers see a UK number and trust it more.

Once Meta approves the WhatsApp Sender, the status flips to Active in Twilio's UI and you get an email. At that point you can move on to step 3.

3. Submit your booking-link message template (~5 min active, then 1-3 days of waiting)

WhatsApp won't let you send unsolicited templated messages without a pre-approved template. Twilio's Content Template Builder makes this much less painful than going through Meta directly.

1. In the Twilio Console, go to Messaging → Content Template Builder → New template.
2. Fill in:

3. Paste this into the body — exactly as written, including the {{1}}, {{2}}, {{3}} placeholders:

Hi {{1}}, it's {{2}}. Here's the booking link we just talked about: {{3}}

Pick a time that suits you and we'll see you then.

4. Twilio asks for sample values. Use plausible test ones — they're only shown to Meta during review:

5. Submit for approval. Status will be Pending for 1-3 business days while Meta reviews.

Once approved, Twilio shows a Content SID that starts with HX. Copy that — you'll paste it into StudioOps next.

Why this exact wording

It's short, transactional, no urgency cues. Meta downgrades long templates and rejects anything that smells promotional ("save now", "limited", "guaranteed", "free"). The wording above sits squarely in the UTILITY category and approves first time in our testing.

If you want to tweak the wording later, that's fine — but you'll need to submit a new version and wait for approval again. Lock the wording before submitting.

4. Paste it all into StudioOps (~5 min)

1. Open your StudioOps dashboard.
2. Settings → Messaging — WhatsApp + SMS → Set up messaging.
3. Paste the four values from your Twilio Console:

4. Click Connect Twilio. StudioOps pings Twilio with the credentials before saving — if anything's wrong, you get a friendly error right then rather than a silent failure on the first customer send.
5. On success: a green "connected" card appears. Don't stop here.
6. Below the connected card, paste the Content SID from your approved template into the Approved WhatsApp template field → Save template SID.

You're now live.

5. Test it (~2 min)

1. On the same page, scroll to Send a test message.
2. Pick WhatsApp, enter your own mobile in E.164 (+44...), leave the default body or type your own.
3. Send test.

Two things might happen:

• Message arrives on your phone → everything works. You can now use Send by WhatsApp on any enquiry's detail page.
• Twilio rejects with "Outside 24-hour window" → expected if the test phone has never messaged your Twilio number. Either send a message TO your Twilio number from the test phone first (opens a 24-hour window), or trust that the test is purely to check API auth and use the freeform mode just to confirm credentials. Real customer sends use the approved template, which works outside the 24-hour window.

For SMS the test always works — no template approval needed.

6. Using WhatsApp on every enquiry

From now on, every enquiry detail page shows a green Send by WhatsApp button next to Send by email. Click it when:

• The customer's enquiry came in by phone or has a phone number on file
• You think the email might land in spam
• It's a younger customer who lives on WhatsApp

Both buttons send the same booking link — customers can use either to get to the slot picker.

If the WhatsApp button is greyed out, hover for the reason. Common causes:

• Twilio not connected → finish step 4
• Content SID not pasted → finish step 4
• Customer has no phone on file → add one to the customer record
• Customer phone isn't in a format we recognise → update to UK 07... or international +44...

What costs what

You pay Twilio directly (StudioOps doesn't mark up). Roughly:

*A "conversation" in WhatsApp pricing means 24 hours of unlimited messages between you and one customer after the first send. So a booking-link send + a reschedule follow-up the same day = one conversation. The next day's reminder = a new conversation.

For real numbers: a Chayil-scale studio sending 30 WhatsApp booking links a month would be ~GBP 0.90/month. A 5-tech nail salon doing 200 sends ~GBP 6/month. StudioOps shows a WhatsApp sends this month counter on Settings → Messaging so you can sanity-check; for actual GBP figures you check your Twilio billing console.

Disconnecting

Settings → Messaging → Disconnect clears all credentials from StudioOps. Your Twilio account, your WhatsApp Sender, your approved template — none of that is touched. Just StudioOps stops being able to send. You can reconnect at any time by pasting the credentials again.

Troubleshooting

Twilio rejected the credentials on Connect. Re-check the Account SID (starts with AC, 34 chars) and Auth Token (32 chars). The Auth Token in the console is masked by default — click "Show" before copying. If it still rejects, generate a new Auth Token in Twilio (account → API keys & tokens → rotate) and paste the new one — old tokens occasionally don't propagate.

"No approved WhatsApp template yet" when I click Send by WhatsApp. You connected Twilio but didn't paste the Content SID. Go back to Settings → Messaging and paste the HX... from your approved template.

Customer didn't get the message. Check Settings → Messaging → "Last send error" line at the top of the connected card. Common Twilio responses:

• 63016 (Failed to send freeform message because you are outside the allowed window) — use the template send (real customer sends do this automatically; only test sends use freeform)
• 63007 (The Channel could not find the From address) — your WhatsApp sender phone is wrong; re-check the format whatsapp:+44...
• 21408 (Permission to send an SMS has not been enabled) — your SMS sender number isn't SMS-capable; buy a UK SMS-enabled number in Twilio

For anything Twilio-specific, the Twilio Console error log has the full details. For anything StudioOps-specific, help@studioops.uk.

See also

• Setting up your services catalogue — the catalogue is what customers see at the end of a booking link
• Setting up the people customers can book with — staff profiles + skill matrix
• Payments: Square and bank transfer — getting money in once they've booked
• Frequently asked questions — common questions about StudioOps

If you get stuck, the StudioOps help centre at studioops.uk/help has search and a ticket form. For anything urgent, email help@studioops.uk.