GoHighLevel Appointment Reminders Not Sending: A Practical Troubleshooting Guide
When appointment reminders stop going out, the cause is usually the reminder workflow, the calendar event or contact consent. This guide covers how to trace a reminder that never fires, without rebuilding the whole booking setup.
Table of Contents
- 01.Why reminders silently stop
- 02.What to check first
- 03.Reminder workflow triggers and timing
- 04.Calendar event type mismatch
- 05.DND and consent for SMS or email
- 06.Workflow conditions and filters
- 07.Time zone and timing offsets
- 08.How to test a reminder workflow
Why reminders silently stop
Reminders depend on a chain. The calendar event has to exist, the reminder workflow has to trigger on it, the contact has to be allowed to receive the message, and the timing has to be correct. A break in any link stops the reminder, and because reminders are time sensitive, you often do not notice until a no-show happens.
What to check first
- Confirm the appointment exists on the calendar with the correct contact linked.
- Check the reminder workflow's trigger and timing settings.
- Look at the workflow history for the contact to see if the reminder step ran.
- Verify the contact is not DND for the reminder channel.
- Confirm the reminder timing offset is not in the past for that appointment.
Reminder workflow triggers and timing
A reminder workflow triggers on a calendar event, usually a set time before the appointment. If the trigger is set to the wrong event type, or the timing offset is wrong, the reminder fires at the wrong time or not at all. Confirm the trigger watches the correct calendar and event type, and that the offset matches when you want the reminder to go out.
If the reminder is set to fire 24 hours before the appointment but the appointment was booked 12 hours before it starts, the reminder window has already passed and it will not fire. This is a common cause of reminders missing for recently booked appointments.
Calendar event type mismatch
If you have multiple calendar event types, a reminder workflow pointed at the wrong one will ignore appointments on the correct calendar. Confirm the workflow trigger matches the event type the appointments are actually booked on. A mismatch here is silent, the workflow simply never sees the appointments.
DND and consent for SMS or email
Reminders go out by SMS or email, and both respect DND. If the contact has DND enabled for the channel the reminder uses, no message will send. Check the contact record for the DND indicator. A contact who opted out of SMS will not receive an SMS reminder regardless of the workflow.
Consent matters. Appointment reminders are generally expected, but if a contact has explicitly opted out of a channel, respect that setting rather than overriding it.
Workflow conditions and filters
A condition or filter between the trigger and the reminder step can stop the message. A filter that requires a certain tag or custom field will skip contacts who do not match. Read the workflow history to see whether the reminder step was reached or the contact exited earlier.
Time zone and timing offsets
Reminder timing is calculated against the appointment time, and time zones affect that calculation. If the calendar time zone and the workflow's expected zone differ, the reminder can fire too early, too late or not at all. Confirm the calendar time zone is correct and that the reminder offset is calculated in the right zone.
How to test a reminder workflow
- 1.Book a test appointment with a contact you control.
- 2.Confirm the appointment appears on the calendar with the contact linked.
- 3.Check the workflow history to see if the reminder step is scheduled.
- 4.Verify the contact is not DND for the reminder channel.
- 5.Confirm the reminder fires at the expected time.
Frequently Asked Questions
Why are my GoHighLevel appointment reminders not sending?
The most common causes are a reminder workflow trigger set to the wrong calendar event, a timing offset that has already passed for the appointment, a contact blocked by DND, or a workflow condition that exits before the reminder step. Check the workflow history to see whether the reminder step was scheduled.
Why did a GoHighLevel reminder not fire for a recently booked appointment?
If the reminder is set to fire a set time before the appointment and the appointment was booked inside that window, the reminder time has already passed and it will not fire. This is common for appointments booked on short notice.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
GoHighLevel Calendar Not Booking Correctly: Availability, Time Zone and Scheduling Problems
Calendar booking problems usually come from availability rules, time zones or event settings. This guide covers how to diagnose a calendar that shows the wrong slots or rejects bookings.
GoHighLevel SMS Not Sending: Common Workflow, Phone and Contact Issues
SMS failures in GoHighLevel usually come from phone number setup, carrier filtering, DND settings or workflow conditions. This guide covers what to check before you rebuild the workflow.
GoHighLevel Emails Not Sending: What to Check Before Rebuilding Your Workflow
When GoHighLevel emails stop going out, the cause is usually in the email configuration, the contact record or a workflow condition, not the workflow itself. Here is how to diagnose it step by step.