Confirming an appointment

Most teams already send confirmations. The messages go out, the customer still does not show, and the conclusion is that confirmation does not work. What usually failed is the content. A sequence that asks for reassurance gets a cancellation, and a sequence that delivers something gets a customer who feels the appointment has already started.

The examples below come from an independent insurance agency and an appointment-setting agency, whose setters book meetings on a client's calendar. The sequence is the same whether the appointment is a phone call, a video meeting or a visit.

The sequence starts on the set call, not the next morning

The first touch happens before you hang up. Read the appointment back out loud: day, date, time, the name of the person they will meet, how to join or where to go, and one sentence about what will be ready. Then ask the customer to say the time back. That acknowledgment is the difference between an appointment that was set and one that was agreed to.

Write down at the same moment anything the customer needs to have ready: the current policy's declarations page, a recent bill, the right login, the other person who has to be on the call. Everything you fail to capture here turns into a second appointment, and a second appointment is another chance to no-show.

Touch two: the same person, in writing, within five minutes

Send it from the number the customer will use to reach you. It carries the day and time in words, the first name of the person they will meet, how to join or the address, and what you are preparing. It closes with what to have ready, if anything.

This message matters more for the thread it opens than for the confirmation it provides. From this point the customer has somewhere to send a question, a delay or a reschedule, and you have somewhere to send a document, a figure or an update. A team that skips this one has no channel when the morning of the appointment goes sideways.

Touch three: the day before, and it has to carry something

Late morning or early evening the day before. Three formats work, and you pick one based on what you actually have.

• The preparation message. What you have done on their behalf. The comparison is written up, the options are ready, the right specialist has blocked the time. Close with the time.
• The logistics message. The link and a number to call if it fails, or which entrance and who to ask for, and how long it will take. Practical detail tells a customer that a specific person is expecting them at a specific hour.
• The small choice. One question answerable in a word: phone or video, two options or all three, 10:30 or 11:00. A customer who answers a question has recommitted without being asked to.

What none of these do is ask whether the appointment is still on. That message does two harmful things at once. It reminds a wavering customer that canceling exists, and it invites a one-word reply that closes the conversation.

Touch four: a live call, two to three hours ahead

A short call from the person they are meeting. Two sentences: everything is ready, talk to you at 5:30. If it reaches voicemail, leave the same two sentences and follow with a text.

The call exists for two reasons. It catches the problem you can still fix, which is usually a time that no longer works and a customer who did not want to send a message saying so. And it puts a voice on the appointment a few hours before it happens, which is when people decide what they are actually doing with their afternoon.

The same-day appointment

An appointment set at two o'clock for five o'clock cannot run a four-touch sequence, and it does not need one. Compress it to two touches: the read-back on the call, and the written message within five minutes carrying how to join, your name and what you will have ready. Skip the confirmation call, because a second call three hours later reads as doubt rather than preparation. What you keep from the long sequence is the part that always applies: the customer has the name of a person, a specific time and a reason that belongs to them.

When the customer goes quiet

Silence is not confirmation. It is missing information, and the right response is to change channel rather than to send the same message again.

1. Two texts with no reply. Stop texting. Call, from the same person, at a different hour than your last attempt.
2. No answer on the call. Leave a voicemail that holds the time rather than questioning it: “Everything is ready, I will be on at 5:30, and call me if the timing changed.”
3. Still nothing the morning of. Keep the appointment on the calendar and prepare it anyway. An unconfirmed customer who shows up to find nothing ready is worse than a no-show.
4. A reschedule request. Take it right away, name a new specific time on that same call or thread, and restart the sequence from touch one. A reschedule that ends without a new time is a lost customer wearing a polite face.

Who sends it, and what software should not do

The name on the sequence has to be the name of the person the customer will meet. If a setter books the appointment and someone else runs it, introduce that person by name in touch two, and let them own touches three and four. That handoff is the most common place a confirmation sequence goes cold, because the customer stops hearing from anyone they recognize.

At an appointment-setting agency the person the customer will meet works for the client, which makes the handoff harder and more important. Synthetic example: a setter books a meeting on a client's calendar and sends touch two with the client rep's name, and the client rep never sends touch three. The customer hears nothing but a calendar invitation from a stranger. Agree with each client who sends touches three and four before the first meeting is booked.

Scheduling the sends, drafting the wording and reminding the rep are reasonable things for software to do. Deciding what to say when a customer replies at nine in the evening that their situation changed is not. Keep the reply in front of a person.

The rules around the messages

Confirmation texts and calls sit inside the same framework as the rest of your customer contact. Under the FCC's rules at 47 CFR 64.1200, telephone solicitations to a residential subscriber may not be made before 8 a.m. or after 9 p.m. local time where the customer is, and the FTC's Telemarketing Sales Rule sets the same outbound calling window at 16 CFR 310.4. Consent for marketing messages and for calls made with an automatic telephone dialing system or an artificial or prerecorded voice is a separate question, and the FCC's rules let a customer revoke consent by any reasonable means, including replying “stop.”

Two practical habits follow. Honor a stop request right away in every system that can reach that customer, not just the one that received it. And keep confirmation content about the appointment, because a message that starts as a confirmation and ends with this month's promotion is a different kind of message. Ask your own counsel how your team should treat these messages. This is general information, not legal advice.

Measure the sequence, not just the outcome

Show rate tells you something went wrong. It does not tell you where. Track three things next to it.

• How many appointments received all four touches. The day-before message is often the one that gets skipped when the team is busy.
• How many were set with a specific time and a named person. A sequence cannot rescue an appointment that was never set properly.
• How many customers replied to anything. A thread with a reply in it behaves differently from one without, and a rep with many silent threads is sending messages that do not invite an answer.

What to do this week

1. Delete every template that asks whether the customer is still coming, and replace it with a preparation, logistics or small-choice message.
2. Put the read-back at the end of the set call and listen for it on two recordings per rep.
3. Assign touches three and four to the person the customer will actually meet, including at client companies.
4. Write the escalation rule: two unanswered texts become a call, at a different hour.
5. Check that a stop request in one system stops messages in all of them.