Two dental follow-up messages. One of them gets deleted.

Here is a message from HighLevel's free dental template, exactly as it ships:

Hi {{contact.first_name}}, thanks for claiming our "{{custom_values.promotion_name}}" promotion - How was your visit at a Dental Clinic in the past?

And here is the equivalent message from the layer we built, at the moment a patient has been presented a treatment plan and hasn't said yes:

{{contact.first_name}}, {{custom_values.tc_name}} here. Be straight with me - is it the cost, the timing, or do you want a second opinion first? Whichever it is, I can help.

Three things separate them.

A human sent one of them. The second message has a name attached - the treatment coordinator, the person who was actually in the room. The first was sent by a merge field. Patients answer people.

One of them asks a question with a real answer. "How was your visit at a Dental Clinic in the past?" is not a question anyone can answer. It's a survey prompt wearing a text message's clothes. "Is it the cost, the timing, or do you want a second opinion?" is three doors, and every one of them is a door the practice can actually walk through.

One of them knows what's happening. The first message treats a person who's just been told they need $12,000 of work the same way it treats someone who clicked a whitening ad. The second one knows exactly where the patient is and what they're weighing.

That's the whole difference between a template built to book cleanings and a system built to close cases. Everything else - the workflows, the pipelines, the branching - is downstream of whether the copy sounds like a person who was in the room.

Why the branch matters more than the message. Cost, timing and second opinion are not the same objection and they don't get the same follow-up. Cost routes to financing. Timing routes to a scheduled callback with a date on it. Second opinion routes to the doctor, not the coordinator. A single generic nurture can't do that, which is why the free template's version has nowhere to go after the send.