Test the whole appointment workflow, not just the calendar.

Define what the customer is booking

Write down each bookable service, its duration and any preparation or cleanup time that affects the next available slot. Decide whether customers choose a specific staff member, a service location or simply the next appropriate opening.

Keep the first version bounded. If an appointment requires a quote, eligibility check or staff judgement, treat the submission as a request for review rather than an automatically confirmed booking.

• Service name and plain-language description.
• Appointment duration and any buffer before or after.
• Required staff, room, equipment or other limited resource.
• Minimum notice and how far ahead a customer may book.
• Information needed before the time can be confirmed.

Separate a request from a confirmed appointment

The customer should be able to tell whether a time is confirmed, waiting for staff review or unavailable. Use different messages for each state instead of sending a generic success notice after every submission.

An illustrative flow is: request received, required details checked, time accepted, confirmation sent and staff calendar updated. This is a planning example, not a claim about an 1120 client result.

• State what the customer has completed.
• Explain whether the time is held or confirmed.
• Name the next action and who must take it.
• Provide a contact path when the customer needs help.

Test availability as a shared business rule

Availability can depend on more than one calendar. Test staff schedules, breaks, locations and resources together when the service needs them. A visible opening should not remain bookable after another customer or staff member has taken it.

Run two test submissions for the same time and confirm how a conflict is handled. Also test a staff absence and a blocked resource. If the connected tools cannot resolve a conflict automatically, define who reviews it and how the customer is contacted.

Make Regina time clear everywhere

Show the appointment date, time and relevant time zone consistently on the booking page, confirmation, reminder and staff record. This matters when a customer, staff member or connected system is outside Saskatchewan.

Test the workflow with devices or accounts set to a different time zone. Check that the customer-facing message and the working calendar still refer to the same moment, and avoid abbreviations that may be misunderstood without context.

Plan confirmations, reminders and replies together

A confirmation should restate the service, time, location or meeting method, preparation details and the approved way to make a change. A reminder should not introduce information that was missing from the confirmation.

Decide what happens when a customer replies to an automated message. If replies are not monitored, say so and give a working contact route. Confirm that the selected email or messaging tools can support the planned timing and reply behaviour before promising it.

• Send test messages to more than one approved test address.
• Check the sender name and reply destination.
• Verify that rescheduled appointments receive the new details.
• Stop obsolete reminders after a cancellation.
• Keep sensitive intake information out of reminders unless it is necessary and appropriately handled.

Design cancellation and rescheduling paths

Customers and staff need a clear way to change an appointment without creating two conflicting records. Decide which changes can be self-served, which need approval and when the original time becomes available again.

Test a customer cancellation, a customer reschedule and a staff-initiated change. Check every connected record and notification. The workflow should make the current appointment clear while preserving enough history for an authorized staff member to understand what changed.

Prepare for failures and manual recovery

A booking flow needs an owner when a calendar connection, notification or staff handoff fails. Decide how failures become visible and which record staff will treat as the working source while the problem is corrected.

Use fictional or approved test data to simulate a duplicate submission, a failed notification and a disconnected calendar. Document the manual steps to confirm the appointment, contact the customer and prevent another booking of the same time.

• Who reviews failed or incomplete bookings?
• Where is the authoritative appointment status recorded?
• How will staff identify and merge a duplicate?
• What manual customer message is used during an outage?
• How will the team confirm that normal operation has resumed?

Bring a complete test case to 1120

1120's published services include booking and email automation, business websites, lead and CRM automation, customer portals and custom business software.

Bring one typical service, the rules that control its availability and the names of the tools your team already uses. Specific integrations, data handling and project deliverables need assessment before they are committed.

Start with your business process.

Describe how customers reach you and what your team needs to do next.

Explore 1120 capabilities