Hypothetical teaching example
One missing reminder, two different diagnoses
This invented example is not a client case study, actual log, or tested repair. Assume a discovery-call booking made 48 hours ahead should receive one SMS reminder 24 hours before the appointment.
A. No enrollment
Hypothetical evidence: Imagine the booking belongs to the Discovery Call calendar, but the workflow's entry filter names Legacy Consultation. No matching enrollment appears in the reviewed contact history for the booking window.
Working hypothesis: A calendar-filter mismatch could explain the missing enrollment. A missing history entry alone does not establish the cause.
Next-safe checks: Read the booking's calendar, status, timestamp, and time zone alongside the selected trigger, filters, workflow publication state, and re-entry settings. Confirm that the history covers the right contact and time window.
Proposed repair: If the mismatch is confirmed, scope a correction to the intended calendar filter and review its impact on other bookings. Do not manually enroll contacts to hide the entry failure.
B. Enrolled, but no reminder
Hypothetical evidence: Imagine a matching enrollment and completed wait step, followed by an SMS action reporting an invalid destination. No delivery confirmation is available.
Working hypothesis: This path reached the reminder action; it is not a no-enrollment problem. The destination error is a lead to investigate, not proof that all other settings are correct.
Next-safe checks: Read the action's error and message status, selected phone field, destination format, channel configuration, consent, and do-not-disturb state. Distinguish waiting, skipped, failed, sent, and delivered states without bypassing restrictions.
Proposed repair: If the destination mapping is confirmed wrong, scope that correction separately. Do not retry customer messages or switch channels without approval and appropriate consent.
Proposed acceptance test
This is a test plan, not a test performed or included implementation.
- After separately approved repairs, use an authorized test contact and controlled recipient, with no real-customer enrollment or messaging.
- Create an eligible booking 48 hours ahead on the intended calendar. Record one expected enrollment and its appointment, workflow, and time zone.
- At the agreed reminder time, verify one reminder attempt for that booking, its action and delivery status, and receipt on the controlled device. A completed workflow step alone is not a delivery pass.
- Check an excluded-calendar booking and a restricted test contact. Confirm no unintended enrollment or prohibited send, then check for duplicate reminders.
What this example cannot prove
Every observation above is hypothetical. No account was inspected, message sent, repair made, or acceptance test run to produce this example.
An actual audit depends on the agreed workflows and available records. Missing history, inaccessible settings, or unavailable delivery receipts remain documented gaps, not confirmed diagnoses or successful outcomes.
Your appointment rules, channels, reschedules, cancellations, and re-entry behavior may need different checks. This example does not establish consent or guarantee message delivery.
Log concepts: HighLevel documents enrollment history and per-action execution details, including errors, skipped states, and time zones. See HighLevel's enrollment history and execution logs guide (source reviewed September 5, 2026). This reference explains log concepts only; it is not evidence for the hypothetical observations above.
This service is audit only: diagnosis, issue list, workflow map, and prioritized roadmap. Implementation and execution of proposed acceptance tests are scoped separately.