Skip to content
    Follow-up

    Personalization at Scale: Automated Messages That Feel Personal

    How to send automated SMS and email that still read like a person wrote them: the data to collect, the merge fields to use and the templates that work.

    By , Director, Neelo DigitalUpdated First published 7 min read

    Team planning personalised customer messages on a whiteboard

    Personalization at scale means automated messages that change based on what you know about each lead, mainly the service they asked about, how they found you and what they've done since, so they read like a person wrote them. You don't need a unique message per customer. You need a handful of good fields, a few versions of each sequence, and a person ready to take over when someone replies.

    Personal messages get replies. Mass messages get ignored. The problem is that writing a personal message to every lead takes time most small teams don't have. This guide covers the data you need, the levels of personalization worth using, templates we use with clients, and how to set it up in GoHighLevel without it becoming creepy or robotic.

    Why does personalization matter to customers?

    Because people now expect it. McKinsey's Next in Personalization 2021 research found that 71% of consumers expect companies to deliver personalized interactions, and 76% get frustrated when that doesn't happen. That research is about consumer brands, but the expectation carries over to anyone who has just told you exactly what they need on a form and then received a generic reply.

    For a small service business, the stakes are simple. A message that clearly belongs to this lead gets read and answered. A message that could have gone to anyone gets skimmed, and the lead replies to the competitor who sounded like they were listening.

    Personalization is about relevance, not first names

    "Hi Lindiwe" at the top of a generic message isn't personalization; everyone knows a merge field when they see one. What makes a message feel personal is that it's clearly about their situation: the service they asked about, the problem they described, the stage they're at. Relevance is what earns the reply.

    What customer data do you actually need?

    You don't need a data enrichment platform. For most service businesses, a handful of fields does almost all the work:

    • First name and preferred channel (SMS, email or WhatsApp).
    • Service or product of interest, captured as a dropdown on your form, not free text, so your automations can branch on it.
    • Lead source: Google, Facebook ad, referral, walk-in. This changes what they already know about you.
    • Timeline: "this week", "this month", "just researching".
    • Location or area, if you serve several.
    • Their own words: the message box on your form. Read it; it's the best personalization data you have.

    Every extra form field costs some conversions, so ask for what you'll use and collect the rest during the first conversation. We usually keep forms to name, phone, email, a service dropdown and one open message box, and capture lead source automatically from the form or ad it came from.

    The five levels of personalization

    Level 1: Name

    "Hi {{first name}}". Expected, not impressive. Use it, but don't rely on it.

    Level 2: Service

    The message changes depending on what they asked about. A teeth whitening inquiry gets a different follow-up from an implant consultation; a geyser replacement gets a different one from a blocked drain. This is the single biggest step up for most businesses.

    Level 3: Source and stage

    A referral who already trusts you needs a different message from someone who clicked an ad an hour ago. A lead who booked and didn't show needs a different message from one who never booked.

    Level 4: Behaviour

    Messages triggered by what they do: clicking the pricing link, replying "later", missing an appointment. Behaviour-triggered messages arrive when the topic is already on their mind. GoHighLevel has triggers for exactly this, including Trigger Link Clicked for tracked links in your emails and texts, and Customer Replied, which can filter on phrases in the reply and on the channel it came from.

    Level 5: Human touch on the important moments

    Automation handles the routine messages; a person writes the ones that matter, such as a reply to a detailed question or a note after a consultation. AI can help draft these, but someone should read them before they go.

    Templates that use real data

    Service-specific first reply (SMS)
    Hi {{first name}}, thanks for asking about {{service}} at {{business}}. Most people want to know price and how soon we can start, so I'll cover both on a quick call. Does today or tomorrow suit you? {{booking link}}
    Referral source (email)
    Subject: {{referrer}} mentioned you might get in touch Hi {{first name}}, great to hear from you. {{referrer}} is a client of ours, and we'd be glad to help with {{service}} too. The easiest next step is a 15-minute call: {{booking link}}
    Clicked the pricing link, didn't book (SMS)
    Hi {{first name}}, Thandi here. If any of the {{service}} options weren't clear, I'm happy to explain which one most people in your situation choose. Want a quick call?
    Timeline: 'just researching' (email)
    Subject: No rush on {{service}} Hi {{first name}}, you mentioned you're still looking into options, so here's the short guide we give everyone before they decide. When you're ready, reply and I'll put a quote together.
    No-show (SMS)
    Hi {{first name}}, we missed you today, no problem at all. Want to pick another time? {{booking link}}

    Always set a fallback

    If a field is empty, a merge field can leave a gap ("Hi ,"). In GoHighLevel's email builder you can set a default value for each custom value, such as "there" for a missing first name. For SMS, use an If/Else branch on whether the field is empty, and send yourself a test with an incomplete contact before switching a workflow on.

    How many message versions do you need?

    Fewer than you think. You don't need a unique message per person. You need a small number of versions per meaningful difference. A practical approach:

    1. List your top three to five services.
    2. For each, write one short sequence (four to six messages).
    3. Add one line that changes by source, such as "Thanks for the referral from {{referrer}}" or "You found us on Google".
    4. Add one branch for timeline: "this week" leads get a call task straight away, "just researching" leads get the slower, more helpful sequence.
    5. Let behaviour triggers handle the rest.

    Five services with one sequence each is perhaps 25 messages to write once, and every lead from then on gets a relevant conversation. We usually write them with the owner in a single working session, because they already know how they'd explain each service on the phone.

    A checklist before you switch it on

    • Every merge field has a fallback value or an empty-field branch.
    • Each message reads naturally when said out loud.
    • The sender is a real person's name, not "Team".
    • Each message has one clear question or next step.
    • Branches cover every option on your service dropdown, plus "other".
    • You've sent a test to yourself with a complete and an incomplete contact.
    • The sequence stops when the lead replies or books.

    Where does personalization go wrong?

    • Too much detail. Mentioning things a customer didn't tell you directly feels intrusive. Stick to what they shared with you or did on your site.
    • Fake familiarity. "Hey buddy!" from a business they contacted once. Friendly and professional beats over-familiar.
    • Pretending automation is personal. "I was just thinking about you" at 3am fools nobody. Make automated messages useful rather than pretending they were typed by hand.
    • Ignoring replies. If they reply "after the holidays", the next automated message shouldn't be "Just checking in!". Stop the sequence on reply and set a reminder for the date they gave.
    • Sending without consent. Only message people who gave you their details and agreed to be contacted, and honour opt-outs straight away. For SMS in the US, the CTIA Messaging Principles and Best Practices set out what carriers expect.

    Personalization also means meeting people where they reply. Short questions work best as texts or WhatsApp messages; detail belongs in email. Our email vs SMS vs WhatsApp comparison and the guide to multi-channel follow-up cover this in detail.

    Setting it up in GoHighLevel

    1. Create custom fields for service, source and timeline, and make them dropdowns on your forms.
    2. In your workflow, use If/Else branches on the service field to send the right sequence.
    3. Insert contact fields and custom values as merge fields in SMS and email actions, with defaults set.
    4. Use triggers such as Trigger Link Clicked, Appointment Status and Customer Replied for behaviour-based messages.
    5. Turn on Stop on Response and send the lead's owner a notification when they reply, so a person takes over.

    Personalization also starts before the form: the landing page should match the ad that brought them. If you need pages and campaigns built that way, Neelo Digital builds the websites and landing pages that feed Signal2Sale. To see how service-specific sequences look for your type of business, browse our industry setups, and for the timing behind each message, read the psychology of follow-up.

    Frequently asked questions

    What is an example of personalization at scale?

    A dental clinic whose form asks which treatment you're interested in. Someone who picks 'implants' automatically gets a reply and follow-up about implant consultations, while a 'whitening' inquiry gets a different sequence. Both use the lead's name and the clinic coordinator's name, and both stop when the person replies.

    How do you personalize automated SMS messages?

    Use merge fields for the lead's first name and the service they chose, branch the workflow by service so each lead gets the relevant sequence, and sign off with a real person's name. Keep texts to two or three sentences with one question, and test with a contact that has missing fields so nothing breaks.

    Can personalization feel creepy?

    Yes, when a message mentions things the customer never told you, or pretends an automated text was typed personally. Stick to what the lead shared on your form or did on your site, such as the service they picked or a link they clicked. Relevant and helpful feels personal; surprising detail feels intrusive.

    What are merge fields and fallback values?

    Merge fields are placeholders, such as first name, that your CRM replaces with each contact's data when a message is sent. A fallback value is the text used when that field is empty, for example 'there' instead of a missing first name, so the message never reads 'Hi ,'.

    Do I need AI to personalize messages?

    No. Most of the benefit comes from capturing the right fields and branching your workflows by service, source and timeline, which any good CRM can do. AI is useful for drafting replies to detailed questions, but a person should read those before they're sent.

    Sources

    1. McKinsey & Company — "The value of getting personalization right—or wrong—is multiplying" (Next in Personalization 2021)
    2. HighLevel Support Portal — "Set Default Fallback Values for Email Custom Values"
    3. HighLevel Support Portal — "Workflow Trigger - Trigger Link Clicked"
    4. HighLevel Support Portal — "How to Use the Customer Replied Trigger in GHL Workflows"
    5. CTIA — Messaging Principles and Best Practices (May 2023)

    Written by

    Director, Neelo Digital

    Adam Mosselson is a director of Neelo Digital, a web development and lead-generation agency with teams in Johannesburg, Cape Town, Manchester and Jerusalem. Neelo sets up and runs Signal2Sale for its clients. About Neelo Digital

    Keep reading

    See what you'd pay in one 15-minute call.

    We'll look at how leads reach you today and quote a fixed monthly price on the spot.