Build around one useful next step
Choose what the person needs to do next. That might be describing the work, selecting a booking time or asking for a callback.
Each message should support that step. Repeating “just checking in” adds little if the original enquiry was about arranging an appointment and the message gives no way to arrange one.
Use the enquiry itself to keep the wording relevant. Do not write as though the owner has personally reviewed something they have not seen.
Example schedule for an appointment enquiry
This is an example, not a required timetable. Use texts only where the person has consented to business texting.
- When the enquiry arrives: Confirm the requested service and offer the booking link.
- The next day, if there is no reply or booking: Ask whether they need help choosing an appointment.
- A few days later, if still unanswered: Offer a callback and make it easy to decline further contact.
Set an endpoint for an unanswered sequence. Silence should not create an endless run of reminders.
Make stopping part of the design
Stop the automatic sequence when someone replies, books or says no. A reply should bring the conversation to a person, even if it does not contain the answer the system expected.
Honour STOP on texts. Check that a booking made elsewhere is recorded so the sequence does not keep asking an already-booked customer to choose a time.
For US business texting from regular 10-digit numbers, arrange A2P 10DLC registration and obtain the person’s consent. Registration and consent are separate requirements; setting up the former does not supply the latter.
Keep judgement with a person
Automate routine acknowledgements, booking prompts and reminders. Keep quotes, complaints and anything requiring judgement with the owner or another responsible person.
For example, “Can you lower the quote?” needs a considered answer. Another scheduled booking message would ignore what the customer actually said.
What to do about it
- Choose the one next step you want from an enquiry: describe the work, book, or ask for a callback.
- Write two or three short messages that each support that step, and set an end to the sequence.
- Make a reply, a booking or a STOP end the automatic messages.
Questions
Should messages continue after a reply?
No. Stop the sequence and let a person handle the response. Decide any later reminder based on that conversation.
Can every enquiry use the same sequence?
Use wording that fits the request and its next step. A callback request should not receive messages that assume the person is ready to book.
What if someone declines without typing STOP?
Treat a clear request for no further contact as a stop instruction. Do not require a specific word before respecting their answer.