TAPEWALL / SETUP AND COMPATIBILITY
Prepare a Bland agent for QA
How to prepare a separate test agent, review its prompt and verify booking outcomes with Tapewall.
1. Prepare the test agent
A test pathway ID and API key for the supported US API host. Confirm region with the operator before connecting.
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 pathway nodes and extracts available prompt or text fields. This is a configuration snapshot, not a complete behavioral audit.
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.
Do not use the production pathway as a test target. Native test execution is not enabled in Tapewall. Regional accounts need separate validation.
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.
Official reference: Bland configuration API. Setup notes reviewed 20 October 2026.