Missed appointments cost clinics, gyms and service businesses real money, and the follow-up is usually the first job that slips on a busy week. It is also a job Claude is well suited to: find the right people, write a kind message, and send it once you have said yes.
Step 1: Ask who missed their appointment
Start with a question, not an action. Name the sub-account and the time range:
In Bright Smile Dental, who missed their appointment this week?
Claude looks through the calendar's appointments and lists the no-shows. This is your chance to check the list. Perhaps one person called to cancel and the appointment was never updated, or one is a regular you'd rather call yourself.
Step 2: Agree the message
Tell Claude what you want to say, or ask it to draft something:
Draft a short, friendly text for them. No guilt, just a link to rebook:
https://brightsmile.example/book
Ask for changes until it sounds like your business. Short and warm works best: acknowledge that life gets busy, and make rebooking one tap.
Step 3: Send, after you confirm
When the wording is right:
Send it to everyone on the list except Noah.
Claude always checks with you before it sends messages, so you'll see who it is about to text and the exact wording, and nothing goes out until you confirm. Each message is sent from the sub-account's normal conversations, so replies land in GoHighLevel as usual.
Step 4: Follow the replies
The next morning:
Did anyone reply to yesterday's rebooking texts?
Claude can read the conversations and tell you who replied and what they said, so your front desk knows who to call.
Make it a habit, not a scramble
If no-shows are a regular problem, consider a workflow so the first nudge happens automatically:
Build a workflow: when an appointment is marked as no-show, wait two hours, then text the contact a link to rebook.
Claude builds it as a draft for you to check and publish. See how to build a follow-up workflow for more on drafts.
Good to know
- Messages need your yes. Claude is told to confirm before it sends anything.
- Only chosen sub-accounts. Claude can only work in the sub-accounts your organisation has switched on for it.
- It's all on record. The Activity log shows each request, who made it and whether it worked. Message text itself is not stored in the log.
Chasing no-shows is a good first job for a new team member using Claude: it's useful, easy to check, and it saves hours every month.
