How to Automate Welcome SMS and One-Click Templated SMS in Zoho CRM (UK Guide)
SMS open rates sit at 98%. For UK businesses using Zoho CRM, that’s a significant opportunity, but only if your SMS automation is set up correctly, complies with the rules, and works for your team.
This guide covers how to send automated welcome texts to new leads and give your sales team a one-click SMS button, all from within Zoho CRM. We’ll cover four practical approaches, the UK compliance rules you need to follow, and common implementation pitfalls.
This article was inspired by a community discussion on SMS Automation in Zoho for a UK Business and expanded with verified technical guidance and UK compliance detail.
What You’re Actually Building
Before setting things up, it helps to pin down what “SMS automation in Zoho” means. The terminology can get muddled quickly.
| Component | What it means in practice |
|---|---|
| Trigger | A new lead is created via web form, manual entry, import, or ad platform |
| Automated action | An SMS is sent without human involvement |
| Manual action | A staff member sends a pre-written SMS from a lead record with one click |
| The key constraint | Zoho CRM isn’t an SMS carrier. You need a third-party gateway |
| UK-specific constraint | PECR and UK GDPR govern when and how you can text people |
| Hidden requirements | Merge fields, E.164 number formatting, opt-out handling, and delivery logging |
This guide focuses on Zoho CRM, the most common setup for UK businesses. Section 4 covers alternatives for Zoho Campaigns, Bigin, and other products.
Critical: The EU Datacenter SMS Limitation
Before configuring anything, check where your Zoho CRM account is hosted.
If your account is on the EU Datacenter, Zoho’s native SMS functionality is disabled due to GDPR data residency regulations. This catches many UK businesses off guard, since EU hosting is common for UK accounts.
How to check: Go to Setup → General → Company Details and check your data centre region.
If you’re on the EU Datacenter, use one of these routes:
- A third-party SMS gateway connected via custom Deluge functions (Approach B below)
- Zoho Flow or a tool like Make.com to connect your CRM to an SMS provider (Approach C)
- A Zoho Marketplace extension that connects to the gateway independently
This determines which approach is available to you.
The Four Approaches (Most to Least Practical)
Approach A: Zoho CRM Native SMS Integration + Workflow Rule (Best for most businesses not on EU Datacenter)
What it does: Connects a supported SMS gateway inside Zoho CRM, then sends messages automatically through a Workflow Rule when a lead is created.
Step-by-step setup:
Step 1 — Choose a UK-capable SMS gateway
Zoho CRM’s SMS integration framework supports several providers, including Twilio, ClickSend, and SMS-Magic (Screen Magic). For UK businesses, consider:
- Twilio — strong UK coverage, alphanumeric sender IDs, long codes, and two-way messaging. It also offers delivery reporting.
- ClickSend — UK support, delivery reporting, and a straightforward API.
- SMS-Magic — conversation management and inbound handling, with separate licensing.
Before choosing a provider, confirm it supports:
- Workflow-triggered outbound SMS, not just manual sends
- Merge fields from CRM records
- Delivery status written back to Zoho
- Inbound STOP reply handling
- UK sender ID or long code availability
- Consent and suppression list synchronisation
Check the Zoho Marketplace for the current list of supported providers and their UK-specific capabilities, which can change.
Step 2 — Connect the gateway
In Zoho CRM, go to Setup → Channels → Business Messaging → SMS (the exact path may vary by UI version). Select your provider, enter your API credentials, and configure your sender ID or number.
Store API keys in Setup → Developer Space → Connections. Never hardcode them in functions.
Step 3 — Create your SMS template
In the SMS settings, create a template. Keep it under 160 characters to avoid message splitting (see the pitfalls section for details):
“Hi ${Leads.First Name}, thanks for getting in touch with [Business Name]. We’ll call you shortly. Reply STOP to opt out.”
Use "Hi there" when the first name is blank, rather than "Hi ,".
Step 4 — Build the Workflow Rule
Go to Setup → Automation → Workflow Rules → Create Rule:
- Module: Leads
- Trigger: Record Action → Create
- Conditions (recommended):
- Mobile is not empty
- SMS Opt-in equals True
- Welcome SMS Sent equals False
- Instant Action: Send SMS (available once the integration is configured; it may be labelled “SMS Notifications”)
- Select: your template and the Mobile field
Edition note: Workflow Rules with custom actions typically require Zoho CRM Professional edition or above. Confirm your plan supports the workflow actions your gateway integration uses.
Step 5 — Test thoroughly
Create a dummy lead with your own mobile number. Check that the message arrives, the merge field populates correctly, and the activity appears on the lead timeline.
One-click manual SMS (within Approach A)
Once the integration is live, staff can open a lead record, click the SMS icon in the record header, select a template, and send. Some gateway integrations also support bulk sends from list view.
This still requires a template picker step. For a true single-click experience, combine it with Approach B.
Approach B: Custom Button + Deluge Function (Best for true one-click sending and EU Datacenter accounts)
What it does: A custom button on the Lead record runs a Deluge script that sends a fixed message through your gateway’s API. No popup or template selection is needed.
This is also the recommended route for EU Datacenter accounts, since it bypasses Zoho’s native SMS layer and calls the gateway API directly.
Step-by-step setup:
- Go to Setup → Customization → Modules and Fields → Leads → Links & Buttons → New Button
- Set placement to Record Detail Page (and optionally List View for bulk sends)
- Set action to Write a Function (Deluge)
Your Deluge function should:
// Fetch lead details
leadId = input.get("leadId");
leadDetails = zoho.crm.getRecordById("Leads", leadId);
firstName = leadDetails.get("First_Name");
mobile = leadDetails.get("Mobile");
// Normalise UK number to E.164 format
// Converts 07123 456789 → +447123456789
if(mobile.startsWith("0"))
{
mobile = "+44" + mobile.removeFirstOccurrence("0");
}
mobile = mobile.replaceAll(" ", "");
// Build message
if(firstName == null || firstName == "")
{
firstName = "there";
}
message = "Hi " + firstName + ", thanks for contacting [Business]. We'll be in touch shortly. Reply STOP to opt out.";
// Call gateway API (example: Twilio)
params = map();
params.put("To", mobile);
params.put("From", "YourSenderID");
params.put("Body", message);
response = invokeurl
[
url: "https://api.twilio.com/2010-04-01/Accounts/YOUR_ACCOUNT_SID/Messages.json"
type: POST
parameters: params
connection: "twilio_connection"
];
// Log activity on lead
note = "Welcome SMS sent to " + mobile + " at " + zoho.currenttime;
zoho.crm.addNote("Leads", leadId, note, "SMS Activity");
// Update 'Welcome SMS Sent' field to prevent duplicates
updateMap = map();
updateMap.put("Welcome_SMS_Sent", true);
zoho.crm.updateRecord("Leads", leadId, updateMap);
For more on writing and troubleshooting Deluge functions, see our guides on Mastering Zoho Flow Custom Function Outputs and Master Deluge Troubleshooting.
Pro tip: Create separate buttons for different templates, such as “Missed Call SMS”, “Quote Follow-Up”, and “Booking Reminder”. Each can call the same function with a different message parameter.
Approach C: Zoho Flow or Make.com (Best when your gateway isn’t natively supported, or you’re connecting multiple apps)
What it does: A no-code flow triggers on “Lead Created” in Zoho CRM and calls an SMS provider, without custom code.
Setup in Zoho Flow:
- Create a new flow with trigger: Zoho CRM → Lead Created
- Add a filter: Mobile is not empty AND SMS Opt-in is True
- Add an SMS action (Twilio, ClickSend, Vonage, etc.) or a webhook
- Add a final step to update a CRM field: Welcome SMS Sent = Yes (prevents duplicates)
Alternatively, Make.com has a visual, drag-and-drop automation builder that connects Zoho CRM to virtually any SMS provider. It’s useful if you already use Make for other automations or your gateway isn’t in Zoho Flow’s native connector library.
For a walkthrough of connecting Zoho products through Flow, see our Step-by-Step Guide: Integrating Zoho SalesIQ with Zoho Creator via Zoho Flow.
For one-click manual sends via Approach C: You’ll still need a custom button (Approach B) to trigger the flow via webhook, rather than call the gateway directly.
Limitations: Zoho Flow has task and execution limits depending on your plan. Make.com is a separate subscription. Both add another system to monitor.
Approach D: Other Zoho Products (Situational)
| Product | SMS capability | UK note |
|---|---|---|
| Zoho Campaigns / Marketing Automation | SMS campaigns and journeys | Confirm UK sender support and pricing before committing. Coverage varies |
| Zoho Voice | Business numbers and SMS in some regions | UK SMS availability has changed over time. Verify current status |
| Zoho Bigin | Messaging via Marketplace integrations | Check the Marketplace for UK-capable SMS extensions |
| Zoho SalesIQ / Desk | Chat-focused | Not suited for lead-welcome SMS |
Approach E: WhatsApp as a Complement (Longer-term consideration)
Zoho CRM integrates with the WhatsApp Business API. Template messages need Meta approval, and contacts must have opted in. Open rates are often higher than SMS, and per-message costs can be lower.
If your leads are likely to use WhatsApp, tools like Treble.ai can help you build WhatsApp messaging workflows around your CRM data. This won’t replace SMS if your audience doesn’t use WhatsApp, but it may fit into your longer-term communication strategy.
UK Compliance: What You Must Get Right Before Launch
Automated texts to new leads fall under PECR (Privacy and Electronic Communications Regulations) and UK GDPR. Getting this wrong carries ICO enforcement risk and reputational damage.
The consent question — and why “transactional” is not a free pass
Many businesses assume that a welcome text after a form submission is “transactional” and exempt from marketing consent rules. This is often incorrect.
Under PECR, a welcome SMS that includes promotional content, such as offers, services, upsell, or future contact, is classified as marketing. You need specific prior consent for SMS.
The soft opt-in, which allows marketing to existing customers without fresh consent, generally does not apply to brand-new leads who haven’t made a purchase.
A purely service-based message, such as “We’ve received your enquiry and will call you at 2pm”, sits in a different category. Even so, ICO guidance recommends erring on the side of explicit consent.
The safest approach: Treat all automated texts to new leads as marketing unless you have specific legal advice confirming otherwise.
Your compliance checklist
- Capture SMS-specific consent on your web form. Use a tick box such as: “I agree to receive SMS messages about my enquiry from [Business Name]”. Store the consent date, source, and wording in CRM fields.
- Don’t assume email consent covers SMS. The ICO is explicit: consent must be specific to the communication channel.
- Include your business name in every message.
- Include a free opt-out in every message: “Reply STOP to opt out”. You need a number that can receive replies. Alphanumeric sender IDs in the UK are one-way only and can’t receive STOP replies.
- Honour opt-outs immediately. Write opt-outs to a CRM field (e.g.
SMS Opt-out = True) and use that field as a workflow condition. Also configure STOP handling at the gateway level. Don’t rely only on CRM logic. - Maintain a suppression list and screen future sends against it.
- Avoid late-night sends. There’s no statutory curfew, but you can add a time condition to your workflow (e.g. 8am–8pm).
- Add the SMS gateway to your privacy notice and data processor agreements.
- Record everything: consent wording, source, date, message sent, and delivery status.
ICO guidance: ico.org.uk — Electronic and telephone marketing
This is general information, not legal advice. For edge cases, consult the ICO or a solicitor.
Common Pitfalls and How to Fix Them
| Problem | Root cause | Fix |
|---|---|---|
| Messages fail silently | UK number stored as 07123 456789 instead of +447123456789 |
Normalise to E.164 in a Deluge function or workflow field update before sending |
| Duplicate welcome texts | No idempotency check | Add a Welcome SMS Sent checkbox field, make it a workflow condition, and update it after a successful send |
| Message splits into multiple segments | Unicode characters (emojis, curly quotes) switch encoding from GSM-7 (160 chars) to Unicode (70 chars per segment) | Use plain ASCII text and test character count before deploying |
| Texts sent to landlines | No number validation | Validate that the number starts with 07 (UK mobile prefix), or use your gateway’s number lookup feature |
| Merge field renders as blank (“Hi ,”) | First Name isn’t required on the form | Make First Name required, or add a fallback: if(firstName == null) { firstName = "there"; } |
| No audit trail | Integration doesn’t log to CRM timeline | Ensure your gateway integration logs activity, or add a zoho.crm.addNote call in your Deluge function |
| Opt-outs not honoured | STOP replies aren’t synced back to CRM | Configure inbound STOP handling at the gateway and sync to a CRM SMS Opt-out field |
| EU Datacenter blocks native SMS | Account hosted on EU servers | Use Approach B (Deluge + direct API) or Approach C (Zoho Flow / Make.com) |
The Fields You Need to Create First
Before building any automation, add these custom fields to your Leads module (Setup → Customization → Modules and Fields → Leads):
| Field name | Field type | Purpose |
|---|---|---|
SMS Opt-in |
Checkbox | Consent captured at form submission |
SMS Opt-in Date |
Date/Time | When consent was given |
SMS Opt-in Source |
Single Line | Which form or channel captured consent |
SMS Opt-out |
Checkbox | Set when STOP reply received |
Welcome SMS Sent |
Checkbox | Prevents duplicate sends |
Last SMS Sent |
Date/Time | Audit trail |
If leads aren’t appearing correctly from form submissions, our guide on Resolving Missing Leads from Zoho CRM Form Issues covers common causes.
Suggested Rollout Plan
Day 1 — Foundations
- Confirm your Zoho CRM edition and data centre region
- Choose your UK SMS gateway (compare per-message price, two-way support, and UK sender options)
- Create the six custom fields above
- Update web forms with an SMS consent checkbox
Day 2 — Gateway setup
- Connect the gateway to Zoho CRM (or set up your Deluge connection if you’re on the EU Datacenter)
- Create 2–3 SMS templates: welcome, missed call, and quote follow-up
Day 3 — Automation
- Build the Workflow Rule (Approach A) or Deluge function (Approach B)
- Test with internal numbers. Check merge fields, delivery, and CRM logging
Day 4–5 — Manual send button
- Build the one-click custom button for staff (Approach B)
- Train the team to use the button and follow the opt-out process
Week 2 — Review
- Check delivery reports, opt-out rates, and gateway costs
- Refine templates based on response data
Which Approach Is Right for You?
| Your situation | Recommended approach |
|---|---|
| Non-technical team, not on EU Datacenter, want the quickest result | Approach A |
| EU Datacenter account, or want full control over the message logic | Approach B |
| Want a single button with a fixed message for staff | Approach A for automation + Approach B for the button |
| Using a gateway Zoho doesn’t natively support | Approach C (Zoho Flow or Make.com) |
| Already heavily using Zoho Campaigns | Check Approach D, but verify UK coverage first |
| Exploring higher-engagement channels alongside SMS | Approach E (WhatsApp via Treble.ai) |
Key Takeaways
- Zoho CRM isn’t an SMS carrier — you need a third-party gateway (Twilio, ClickSend, SMS-Magic)
- EU Datacenter accounts can’t use Zoho’s native SMS integration — use Deluge custom functions or Zoho Flow instead
- Workflow Rules for SMS typically require Professional edition or above — confirm your plan
- PECR requires SMS-specific consent — general form consent or email consent isn’t sufficient
- Alphanumeric sender IDs are one-way — you need a long code or short code to receive STOP replies
- E.164 formatting (+44…) is essential — normalise numbers before sending
- The
Welcome SMS Sentfield is essential — without it, workflow retries will send duplicates - Log everything — delivery status, opt-outs, and message content should appear on the lead timeline
Need Help Setting This Up?
SMS automation in Zoho CRM involves several moving parts: gateway selection, EU Datacenter considerations, Deluge scripting, PECR compliance, and workflow logic. They all need to work together.
The Creator Scripts team specialises in Zoho CRM customisation and automation for UK businesses. We can help with a complete SMS automation build, a compliance review of your existing setup, or a custom Deluge function for your gateway.
- Book a consultation — discuss your requirements with a Zoho specialist
- Explore our Zoho services — CRM customisation, automation, and integrations
- Browse our Zoho blog — more guides like this one
- Zoho partner FAQs — what working with a Zoho partner looks like
Ready to get started with Zoho CRM? Explore Zoho CRM here. If you’re considering the full Zoho suite, Zoho One gives you access to 45+ integrated apps under one licence.