Skip to main content
Use a small, repeatable scenario with a distinctive utterance and an expected answer. Verify the complete path, not just a connected socket or a provider response. For an external write, check the destination system. A reply_text event does not establish that audio played, and a completed conversation does not establish that a booking or lead was saved. Keep a failed-path test: missing knowledge, backend timeout, interrupted turn, and customer hang-up. Use conversation and turn IDs to correlate browser events, hook requests, and timeline events. Do not log identity tokens, API keys, or deployment shared secrets. Browser events.