- Merge fields insert real data like names, locations, and inquiry types into automated messages
- Contextual language adapts based on the source, timing, or type of enquiry received
- Conversational tone, short sentences, and simple language make automation feel human
- Strategic timing and transparency prevent automated messages from feeling intrusive or misleading
- Clear next steps guide the lead forward without requiring you to jump in immediately
Automated responses get a bad reputation because most of them read like automated responses. They feel robotic, impersonal, and a bit insulting. The lead knows you didn't write it, which makes them wonder if you care.
But automation doesn't have to feel cold. When done well, personalised automated responses acknowledge the lead quickly, provide useful information, and move the conversation forward without making anyone feel like they're talking to a script. The difference lies in how you build the message.
Use merge fields correctly
Merge fields pull real data from your form or CRM and insert it into the message. First name, location, service requested, date and time of enquiry. These fields make the difference between "Thanks for getting in touch" and "Thanks for getting in touch, Sarah."
The name field is the most common, but it's not the only one that matters. If someone fills out a form asking about boiler repairs in Manchester, your automated response should reference both the service and the location. That proves you received the right information, and it reassures the lead that they're not just another entry in a database.
Be careful with capitalisation. If your CRM stores names in all caps, the merge field will output "SARAH" instead of "Sarah." Most platforms allow you to format merge fields, so check your settings and test the output before the message goes live.
Also avoid over-personalisation. Using someone's name three times in a four-sentence message doesn't feel friendly, it feels like a telemarketing script. Once at the start is usually enough.
Build contextual awareness into your messages
Personalisation isn't just about inserting a name. It's about showing that you understand what the lead actually wants. That requires context, and context comes from knowing where the enquiry came from, what they asked for, and when they asked.
If someone fills out a contact form at 11pm on a Saturday, your response should acknowledge the timing. "Thanks for reaching out, James. We've received your request about emergency plumbing in Bristol. Our team will call you first thing Monday morning, or if it's urgent, you can reach us on [emergency number]."
That message works because it reflects reality. It doesn't pretend you're sitting at your desk at midnight, and it gives the lead a realistic timeline alongside an alternative if they can't wait.
Context also applies to the source. A lead from a Google Ad might need different language than one from a referral or a repeat customer. If your CRM tracks lead source, you can write separate automated responses for each channel. That way, someone who found you through a paid ad gets a different tone than someone who came through a recommendation.
Write in a conversational tone
Automated messages fail when they try to sound formal or professional in a way that no human actually speaks. "We are in receipt of your enquiry and will endeavour to respond within the next business day" is technically polite, but it sounds like it came from a bot.
Compare that to "Thanks for getting in touch. We'll call you back tomorrow morning." Same information, but one feels like a person wrote it.
Short sentences help. So do contractions. "We'll" feels more natural than "we will." "You've" feels more natural than "you have." These are small changes, but they shift the tone from corporate to conversational.
Want automated responses that actually convert?
We'll set up personalised messaging that feels human from the first reply.
Book a free discovery callRead the message out loud before you send it. If it sounds awkward when you say it, it'll feel awkward when someone reads it. If you wouldn't say it to a lead on the phone, don't put it in an automated message.
Another trick is to write in second person. "You'll hear from us tomorrow" is more direct than "customers will receive a response within 24 hours." The lead doesn't want to know what happens to customers in general. They want to know what happens to them.
Timing matters more than you think
The speed of your automated response changes how it feels. If the message arrives within seconds of the form submission, that's fine, provided the message acknowledges the timing. But if it arrives three hours later, it stops feeling like an automated response and starts feeling like you ignored them for half the day.
Instant responses work best when they're paired with a realistic follow-up window. "Thanks for reaching out, we'll call you back tomorrow" feels honest. "Thanks for reaching out, we'll call you back shortly" creates an expectation you might not meet.
Avoid sending automated responses outside normal business hours if the message implies immediate availability. A message that says "we'll get back to you soon" sent at 2am feels dishonest. Better to say "we'll call you first thing in the morning" or schedule the message to send when you're actually available.
Some platforms let you add delays to automated responses. A two or three-minute delay can make the message feel more human, especially if the lead expects that someone is typing. This works well for SMS, where instant replies can feel robotic but a short pause suggests a real person is involved.
Be transparent, but don't apologise for automation
You don't need to announce that the message is automated, but you shouldn't pretend it's not. Starting a message with "Hi Sarah, this is Dave from ABC Plumbing" when Dave hasn't actually seen the enquiry yet crosses the line into deception.
Instead, use language that reflects the reality of the situation. "We've received your enquiry" is honest. "I've personally reviewed your request" when you haven't is not.
That said, you also don't need to apologise for using automation. Phrases like "sorry for the automated response" or "apologies for the delay" create unnecessary friction. The lead doesn't expect you to sit by the phone 24 hours a day. They just want confirmation that you received their message and that someone will follow up.
If the follow-up is going to take longer than expected, say so. "We're experiencing high demand at the moment, so we'll call you back within 48 hours" is better than an overpromise you can't deliver.
Provide clear next steps without creating extra work
A good automated response doesn't just acknowledge the enquiry. It moves the conversation forward. That might mean confirming an appointment time, sending a link to book a call, or asking the lead for more information.
The best next steps are ones that don't require you to be available. If you send an automated response that says "reply with your availability and we'll book you in," you've created extra work for yourself. Better to include a booking link that lets the lead choose a time that works for them.
If you need more information before you can provide a quote, ask for it in the automated message. "To give you an accurate estimate, we'll need to know the size of the property and the type of work required. Can you reply with those details?" That way, when you do follow up, you've already got what you need.
Clear next steps also set expectations. If the lead knows you'll call them at 10am tomorrow, they're less likely to chase you at 9am or assume you've ignored them. That reduces inbound queries and makes your follow-up process smoother.
From the EveryCatch team
We help service businesses turn automated responses into the start of real conversations. Our systems personalise every message without adding extra work to your day.
