# Appointment-booking test pack

By Kashif Rehman | BizThrivers | October 24, 2026
https://bizthrivers.com/resources/appointment-booking-test-pack/

Free to adapt. Use sample values; do not place credentials or customer records in this worksheet.

## Planning decisions

### Calendar, booking path and responsible owner
Illustrative: one 30-minute agency consultation, booked through the public website widget. Record calendar name, version, assigned staff member, connected external calendar and the person who can stop a faulty booking path.
Your decision: 

### Business, staff and visitor timezones
Record named zones, not just a UTC offset. Define the visitor display, stored appointment time, staff calendar time and confirmation wording. Include a second visitor timezone and a date near a daylight-saving change where relevant.
Your decision: 

### Availability, busy events and booking limits
Write available hours, blocked dates, busy calendars, appointment length, buffer, minimum notice and any daily limit. Decide which external events should block a slot and who investigates a mismatch.
Your decision: 

### Repeat contact, recurrence and change rules
Decide what should happen when the same contact books again. Separately record whether recurring appointments are used, how unavailable occurrences are handled, and who may reschedule or cancel. A repeat booking is not automatically a recurring series.
Your decision: 

### Notification owner, evidence and release decision
For each booking event name the notification or workflow, recipient, channel and timing. Use controlled test destinations. Record actual receipt, exception owner, evidence location, release approver and a manual booking fallback.
Your decision: 

## Booking evidence matrix
Use controlled test contacts and private evidence references. Keep meeting links and personal information out of shared copies.
| Scenario | Booking path / calendar version | Expected instant / named zone | Observed appointment / external event | Message / recipient / time | Result / owner / retest |
| --- | --- | --- | --- | --- | --- |
| Two visitor timezones | | | | | |
| Busy slot and released slot | | | | | |
| Notice / buffer / daily limit | | | | | |
| Same contact books again | | | | | |
| Unconfirmed then confirmed | | | | | |
| Reschedule then cancel | | | | | |

## Notification ownership
| Event | Calendar notification or workflow owner | Recipient / channel | Timing / stop rule | Evidence |
| --- | --- | --- | --- | --- |
| New unconfirmed booking | | | | |
| Confirmed booking | | | | |
| Reminder | | | | |
| Reschedule | | | | |
| Cancellation | | | | |

## Optional recurring-series check
Recurrence path: Calendar configuration / Custom in-app recurrence / Not used
Occurrence count / unavailable-slot rule: 
Busy occurrence observed / approval: 
Single-series confirmation and per-occurrence reminders checked: 

## Release gate
Blocking failures: 
Booking fallback / responsible person: 
Approver / tested version: 
Rollback decision / owner: 
Next operating review: 

## Observed test record

### 1. Two visitor timezones describe the same appointment
Action: Book through the live visitor path in two named timezones using separate sample appointments. Compare selected date/time, CRM appointment, staff event and received confirmation, including the date boundary where relevant.
Expected: Visitor display, stored appointment, staff event and confirmation refer to the same intended instant and named zone.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 2. Busy time blocks and released time can reopen
Action: Create a controlled busy event on a calendar that should block booking. Inspect the slot, then remove that event and check again after observed sync. Record the wait and any discrepancy.
Expected: A known busy slot is blocked; a released slot returns only when the written availability rules allow it.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 3. Notice, buffer and booking limits hold at the boundary
Action: Try a slot just inside and just outside minimum notice, next to a booked appointment, and beyond any configured daily limit. Record chosen times and the visible result.
Expected: Slots follow the configured notice, buffer and limit rules; any exception has an explanation and owner.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 4. A repeat booking follows the agreed rule
Action: Use the same controlled contact to book again through the same path. Check appointments, contact record, assignment and messages. If recurrence is enabled, also test an occurrence that meets a known busy slot.
Expected: The second booking and any recurring occurrence follow the documented policy without a silent unexpected appointment.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 5. The correct recipients receive the correct event
Action: Create an unconfirmed booking and, where used, confirm it. Inspect each enabled calendar notification and workflow. Compare actual controlled-inbox receipt, message time, timezone, recipient and meeting location.
Expected: Each enabled event reaches its intended recipient with the right time and location, without an unintended duplicate.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

### 6. Rescheduling and cancellation clear stale actions
Action: Use the received links or documented operator path to reschedule the sample appointment, then cancel it. Inspect the CRM, connected staff calendar, messages and pending reminder actions.
Expected: Records and messages reflect the final state; stale reminders or duplicate active bookings are investigated before release.
Observed: 
Evidence location: 
Responsible owner / fix: 
Result: Untested / Needs work / Passed

## Release and handover
Outstanding fixes: 
Operating owner: 
Approver and decision: 
Review date: 
Where to monitor and how to pause a problem: 
Change-request route: 

## Sources checked October 23, 2026
https://help.gohighlevel.com/support/solutions/articles/155000003358-troubleshooting-tool-for-calendar
https://help.gohighlevel.com/support/solutions/articles/155000003441-calendar-email-in-app-sms-whatsapp-appointment-notifications
https://help.gohighlevel.com/support/solutions/articles/155000003450-recurring-appointments

A completed log records your observations. It does not automatically verify the CRM or agent.
Independent HighLevel affiliate: I may earn a commission through referral links on BizThrivers.