Prepare a Vapi agent for QA

1. Prepare the test agent

A saved test assistant ID and private API key. The operator binds the credential to your workspace.

Use synthetic customer information and a dedicated test calendar. Disable access to production booking tools and live customer queues.

2. Inspect the configuration

Tapewall reads the selected assistant and its standard system messages. Custom model configurations may need an agency-supplied prompt export.

Open Settings in the private workspace, select the platform and your cloned agent, and request a read-only inspection. Credentials stay server-side.

3. Approve the facts

Review hours, services, prices, staff and booking rules from the prompt. Add them to the fact registry and approve them before creating scenarios. Imported text is not automatically approved.

4. Check the booking, not just the answer

Agree on written test scope, connect the isolated calendar, and complete a supervised test before scheduling. A booking needs matching service, time, staff and synthetic customer evidence.

Keep the test assistant separate from production. Do not replace an existing production server URL. Simulated or mocked tool calls are not calendar evidence.

When the prompt changes

A new manual inspection compares the available prompt and version with the saved snapshot. Detected changes require review before live tests resume. This does not continuously monitor every tool or remote setting.