Write automated follow-up that still sounds like a person

This page shows how to build the automated messages that go out after someone contacts a business: the instant acknowledgment, the missed-call text back, and a short sequence for leads that go quiet. Automation makes the follow-up fast and consistent. What keeps it from sounding like a robot is a person writing it for a specific kind of customer, and staying in the loop for anything that matters.

Before you begin

• A written response standard: who responds, by when, and how many attempts. Speed to lead shows how to write one.
• A CRM or messaging tool that can send on a trigger, stop when the customer replies, and log every message on the lead's record. See the CRM pipeline guide.
• A business phone number that can send and receive texts, registered for business texting if you text customers in the US.
• Email that sends from the business's own domain, with SPF, DKIM, and DMARC records in place.
• The three or four questions the office needs answered before it can quote.

Build the follow-up

1. Write the instant acknowledgment

   This is the message a customer gets seconds after a form fill, by text, email, or both. It has three jobs: say that a real person has the request, say what happens next, and say when. A named person and a specific time do more than any amount of polish.

   Hi [First name], this is [Your name] at [Business]. Got your request
   about [what they asked for]. I'll call you by [time] to set up a time
   to take a look. If it can't wait, call or text this number.

   It can also ask one question that speeds up the quote, such as a photo of the problem or the best time to call. It should not quote a price, promise an appointment nobody has confirmed, or read like a receipt.

   After hours, change only the promise. Say when the call will come, such as "first thing tomorrow, before 9," and make sure someone keeps it.

2. Set up the missed-call text back

   When a call to the business line goes unanswered, a text goes out from the same number a minute or two later. Plenty of owners take calls from job sites and trucks, and a caller who reaches voicemail can simply try the next business on the list. The text keeps the conversation open.

   Hi, this is [Your name] with [Business]. Sorry I missed your call, I'm
   on a job. Text me what you need and I'll get right back to you, or I'll
   call you back by [time].

   Log the missed call and the text on the CRM record, alert the lead's owner, and still make the return call, because some callers use landlines, which usually cannot receive texts. Leave out numbers already marked as spam or as vendors.

3. Write a short sequence for leads that go quiet

   A lead that stops answering has not necessarily said no. A short sequence gives them easy chances to come back, then stops. Three rules: a few touches, spaced further apart as time passes; a new reason to reply in each one; and a clear final message, after which the lead moves to Lost. When I set up a basic follow-up sequence, it is three to five messages, not an open-ended drip.

   For a lead nobody has reached yet, the attempts come straight from the response standard, for example a call and a text on day 1, a call on day 2, an email on day 4, and a final text on day 7. For a quote that has gone quiet, I use the same spacing as my own proposals: follow-ups on days 3, 7, and 14, and a close-out at day 21. Here is one way to fill that in.

   When	Channel	The reason to reply
   Day 3 after the quote	Text	Check that the quote arrived and offer to walk through it. Easy to answer with a yes or no.
   Day 7	Email	Something useful: photos of a similar job, the warranty in plain words, or the answer to a question customers often ask.
   Day 14	Call	A real conversation. Leave a short voicemail if they do not pick up.
   Day 21	Text	The close-out: you are closing the quote unless they want to keep it open. Then the lead moves to Lost.

   Hi [First name], it's [Your name] with [Business]. I haven't heard back
   about the [service] quote, so I'll close it out on my end for now. If the
   timing changes, reply here and I'll pick it right back up.

   That last message is honest, asks for nothing, and leaves the door open.

4. Write like a person from this business

   Plain, specific, and local beats polished. Before you turn a message on, read it out loud and ask whether the owner would say it that way to a customer standing in front of them.

   • Use a real first name, not "The Team" or "Customer Care."
   • Name the thing they asked about in their own words: the leak, the patio, the fence along the back.
   • Mention local details only when they are true, such as the town you are working in this week.
   • Ask one question per message, one that can be answered from a phone.
   • Keep texts to a few lines, and put any link on the business's own domain rather than a public link shortener.
   • Leave out fake urgency, capital letters for emphasis, and strings of exclamation points.
   • Say what happens next, every time.

   Instead of	Write
   "Thank you for your submission. A representative will contact you shortly."	"Got your message about the leak over the garage. This is [Your name], and I'll call you by 3 today."
   "Just following up on my previous message."	"Did the quote for the fence come through okay? Happy to walk you through the two gate options on a quick call."
   "Don't miss out! Book today!"	"I have a crew in [Town] next Tuesday and Wednesday. Want me to pencil you in?"

   Send the third kind of message only when it is true.

5. Set stop rules

   A follow-up that keeps going after someone replies is the fastest way to sound like a machine. Every sequence needs automatic stop rules, tied to the lead's record rather than to someone remembering. Stop the sequence when:

   • The customer replies on any channel, including calling in.
   • The customer books, schedules, or accepts a quote.
   • The customer texts STOP or unsubscribes.
   • The lead moves to Lost, or a person takes over the conversation.

   Check two edge cases. A customer who submits a form twice should get one sequence, not two, because automation tools can fire the same trigger more than once. And when a customer replies, a person has to be alerted, or the sequence stops with nobody picking up the conversation.

6. Keep a person in the loop for price and schedule

   Automation is good at acknowledging, asking, reminding, and confirming what a person already decided. It should not quote a price, promise a date for the work, or accept a change to a job. Promising when someone will call back is fine, because the business controls that. Promising when the crew will show up is a decision for a person with the calendar in front of them.

   Two more lines I hold to. Anything sent to a list, such as a seasonal promotion to past customers, waits for a person to approve it; only one-to-one messages triggered by something the customer did send on their own. And if you use AI to draft replies, treat what it writes as a draft for a person to edit, never as a message that sends itself.

7. Follow texting and email rules

   This is general information, not legal advice, and the rules change. The basics:

   • Get consent before texting. A form that offers text updates should say so plainly, next to the phone field. A missed-call text back should stay a one-time reply about that call, not an entry onto a marketing list.
   • Honor opt-outs right away. A reply of STOP ends texts to that number, and the opt-out should carry across every tool that can text the customer.
   • Register for business texting. In the US, business texting from a standard local number generally requires registering the business and its message types with the carriers, a process called A2P 10DLC registration that runs through your texting provider. Unregistered messages can be filtered or blocked. Toll-free numbers have their own verification process.
   • Cover the basics in marketing email. In the US, commercial email needs a working unsubscribe link and the business's postal address.
   • Mind the clock. Send during reasonable local hours. Some states have their own texting laws, including limits on when messages can be sent.
8. Measure replies and bookings

   Judge each message and each sequence by what it produces, and log the results on the lead record so the numbers come from the CRM rather than from the texting tool's dashboard.

   Reply rate

   Leads who replied, divided by leads who got the message. Measure it per message to see which touch does the work.

   Bookings

   Leads who scheduled or accepted a quote after entering the sequence, and which touch they answered.

   Time to first human contact

   Whether the automation is buying time for a person or quietly replacing one.

   Opt-outs

   A rising count means the messages are too frequent, too salesy, or reaching people who never asked for them.

   Ignore email open rates for this. Some mail apps load tracking images automatically, so opens get counted for messages nobody read. Replies and bookings cannot be inflated that way.

   Change one thing at a time, such as the wording of the day 3 text, and compare a few weeks before and after. At small-business lead volumes a formal split test can take a long time to settle anything, so keep the comparison simple and honest.

Verify it works

Test from a phone number and an email address the business does not recognize, and test every door a customer can use, not just the main form.

• A form submitted at night gets the acknowledgment within a minute or two, in the inbox rather than spam, naming a person and a time.
• A call that rings out gets the text back from the business number, and the missed call shows on the CRM record.
• A reply to any message stops the sequence and alerts the lead's owner.
• Texting STOP from a test number ends all texts to that number.
• A test lead left alone receives each touch on schedule, then moves to Lost with the reason "No response."
• Submitting the same form twice starts one sequence, not two.
• Leads from every entry point, including each form on the site and any message ads, enter the right sequence.

Troubleshooting