How will the rules be represented?
Ask the provider to walk through one service, its required resources and buffers. They should explain whether the current booking product can support the rules or why additional development is needed.
Choosing help
Ask what happens when two people choose the same time.
A useful proposal explains how availability is enforced and how staff handle exceptions after launch.
Reviewed October 16, 2026 ยท Faith Forge Labs
Which system owns the booking?
Clarify how connected calendars are used, what delayed updates look like and who resolves failures. A sync feature needs a recovery process as well as a successful demonstration.
What will be tested?
Ask for simultaneous requests, staff absence, rescheduling, timezone changes and failed payment where relevant. A test plan should distinguish a stored appointment from a sent notification.
Who maintains it?
Clarify control of hours, service durations, provider accounts, templates and custom code. Staff should know how to close a date or resolve a conflict without relying on undocumented access.
How will live checks avoid disruption?
Agree fictional bookings, test recipients and payment test modes where supported. Keep test records identifiable and out of business reporting. Separate release work from ongoing support and vendor charges.