How to prepare a safe test calendar for an AI booking pilot

Give a QA provider enough access to verify outcomes without exposing real customer appointments.

Clone the workflow

Ask the agency to clone its agent and connect the clone to a dedicated test calendar or test account. Use synthetic customers and an approved test number or endpoint. Do not route the test to the real customer queue.

Separate reading from writing

The QA reader needs permission to inspect the test calendar. The agent needs its own authorized booking permissions. A separate test-control adapter prepares conflicts and cleans up tagged fixtures. A read-only token cannot delete bookings.

Write down authorization

Name the agency, authorized representative, exact agent, test calendar, allowed actions, test window, volume cap, recording permission and stop contact. Agree on retention and which providers may receive synthetic transcripts.

Prove isolation before scheduling

Create a known synthetic booking, verify it, remove it through the agreed cleanup path and confirm unrelated fixtures remain. Then supervise one complete scenario. Scheduling should only follow observed safe operation and an agreed spending limit.