Good SMS follow-up helps someone continue an enquiry they have already made. It identifies the business, addresses the actual service and makes the next action easy. It should not become a stream of generic messages that ignores replies.

Before writing anything, decide which contacts you are allowed to message and why. Keep evidence of the relevant preferences and make stopping straightforward.

Group enquiries by the next action

Do not send one sequence to everyone. Separate people who have not been reached, people who asked a question, people choosing a time and people reviewing a proposal.

SituationUseful message purpose
No conversation yetOffer a suitable way to connect
Question unansweredAnswer it or arrange staff help
Ready to bookOffer accurate availability
Proposal sentAsk about scope or timing
DeclinedClose the relevant sequence

The same phone number may appear in several systems. Keep one current status so the customer does not receive contradictory messages.

Start with a specific, answerable message

For an appointment enquiry:

“Hi [Name], this is [Business]. You asked about [service]. Would this week or next week suit a conversation with the team?”

For a project request:

“Hi [Name], thanks for telling us about [project]. Is there a convenient time for us to ask a few questions and discuss the next step?”

These are illustrative templates. Replace the details accurately and send only through approved channels and timing rules.

Make the next message depend on the response

If someone asks a question, pause the generic booking prompt. If they request a person, assign a callback. If they choose a time, check availability before confirming it.

A useful automation reacts to the customer’s status. It should not continue simply because a timer has elapsed. Make staff takeover visible in the CRM and cancel queued messages where necessary.

Set a clear end to the sequence

Agree a maximum duration and a limited set of helpful contacts. Do not increase pressure when someone remains silent. Respect opt-outs and other requests to stop.

Messaging platforms offer configuration for consent and suppression. Twilio’s consent management documentation describes storing opt-in, opt-out and re-opt-in status. Your implementation still needs to match the purpose and requirements of the business’s messages.

Test the sequence like a customer

Submit a test enquiry, reply with a question, let staff take over and then book an appointment. Check that the unbooked messages stop. Repeat with a decline and an opt-out.

Review sender identity, links, local time, message length and where replies arrive. A technically delivered message can still be confusing or useless.

Measure conversations and valid next steps

Track replies, useful conversations, suitable bookings, opt-outs and manual corrections. A high message count is not a business result.

Explore SMS Follow-Ups, faster lead response and estimate follow-up to choose the right workflow for each enquiry.