Unfinished Website Chats: SMS Follow Up That Brings the Conversation Back

Plenty of website chats end mid sentence. The visitor got called away, lost signal, or opened a second tab and forgot yours. If the chat captured a phone number early, you have a fair chance to restart that conversation by text, provided the visitor agreed to be contacted.

The follow up logic here borrows from phone work. SMS follow up sequences after calls covers what to text after a conversation ends. An unfinished chat is a different case, because the conversation never reached its point.

Earn the number before you need it

Ask for a mobile number as part of the chat itself, early enough that a dropped chat still leaves you a way back. The honest framing works. Say the number is for the booking confirmation and for a text if the chat cuts off. Visitors hand over a number when they can see what it is for. Add a clear line that texting is optional and a refusal changes nothing about the chat.

The first text does one job

The first follow up text should name the business, remind the visitor what they were doing, and offer one easy next step. A link back into booking, or a reply word that restarts the chat by text. Keep it to a couple of lines. A text that tries to recap the whole chat, pitch a service, and ask three questions will be ignored, and it should be.

Send it while the errand is still fresh in the visitor mind. Same day, during reasonable hours. A follow up that arrives two days later about a haircut chat reads as marketing, whatever you intended.

Two messages is a sequence, three is a campaign

If the first text gets no reply, one more message a day or so later is reasonable, ideally with something new in it, such as a slot that opened up. After that, stop. Put the contact into your normal marketing list only if they agreed to that separately. Permission to finish a booking conversation is a narrow permission, and stretching it damages the trust that made the first reply possible.

Measure replies, not sends

Track how many follow up texts get a reply and how many of those end in a booking. If replies are rare, the problem is usually the chat, which asked for a number before giving anything of value. Fix the chat order first. Our piece on turning website visitors into booked appointments shows a flow that gives the visitor a slot before it asks for details, and that order lifts follow up replies too.

Where the chat should ask, and how often

Asking for a number in the first message is too early, because the visitor has received nothing yet. Asking after the first useful exchange works better. The bot has answered a question or shown available times, and the request lands as part of finishing the job. If the visitor declines, the chat continues without comment and does not ask again in the same session. A second request in one chat turns a service step into pressure, and visitors can feel the difference.

Keep a record staff can see

When a follow up text goes out, log it on the customer record with the time and the wording used. Staff answering a reply need to see what was sent, and two team members should never follow up the same dropped chat on the same afternoon. This sounds like housekeeping until the day a customer replies angrily about being texted twice, and nobody can work out who sent what. One shared log ends that problem before it starts, and it also gives you the reply and booking numbers you need to judge whether the follow up is earning its keep.

What a good reply rate looks like in practice

Judge your follow up by comparing it with your other channels for the same job. If a text after a dropped chat earns replies at a rate anywhere near your reminder replies, the flow is healthy, because reminders go to people who already booked and chats go to people who had not decided. A follow up that performs far below that usually has a wording or timing problem rather than an audience problem. Change one of those, resend to a fresh batch of dropped chats, and compare before you conclude that visitors simply do not want texts.