TAPEWALL / SETUP AND COMPATIBILITY

Test-only access, clear evidence

What the current product stores and what must be agreed before a pilot.

Separate test resources

Never connect a production calendar or customer queue. Use cloned agents, synthetic names and contact details, a dedicated test calendar, and written permission with an expiry. Booking tests require an agreed fixture and cleanup contract.

What we store

The workspace stores client facts and approvals, scenarios, transcripts, calendar evidence, test outcomes, investigation notes, permission references and audit records. Voice runs can include recording references when recording is explicitly authorized. Platform inspection stores metadata and prompt fingerprints; selected prompt text is displayed for review.

Credentials

Platform keys are configured server-side and bound to a workspace. Do not put keys or passwords in facts, prompts, forms or email. Customer-managed OAuth and a self-serve credential vault are not available yet.

Retention and deletion

Automated retention and customer self-serve deletion are not implemented. Before a pilot, agree the retention window and deletion process with the operator, including any copies held by the voice, calendar and model providers. Do not upload real customer data.

Current access boundary

The testing app is owner-private. Public customer accounts are not open yet. We have not claimed an independent security certification or guaranteed that an agent is safe.

Reports and model judgment

Calendar verification establishes booking evidence. A model can assist with conversation review but cannot create a verified booking from a transcript. Uncertain findings remain visible for human review.