# Test the hard cases, then launch safely > Run repeatable Web call and Phone call tests, verify difficult conversations and structured results, switch the agent to Live, and connect controlled traffic safely. Source: https://www.heyrik.com/docs/academy/test-and-launch Use Web call and Phone call tests while the agent is Draft, run a repeatable scenario suite, switch to Live only after it passes, and connect controlled traffic. 20 minute lesson Outcome: A tested agent on controlled live traffic Follow along in your workspace.[Open dashboard](https://www.heyrik.com/assistants) ## By the end of this lesson You will run the same eight scenarios through a Web call, validate real telephone audio with a Phone call, correct every failure while the agent remains Draft, switch to Live, and connect only a small amount of controlled traffic. ## Open the Test panel from the Draft Dashboard → AI Agents → Property Enquiry Assistant. The Test button is in the builder header near the Live control. 1. ### Confirm readiness The agent needs a name, voice, at least one language, and nonempty instructions before Test is enabled. 2. ### Click Test The right-side test panel opens without requiring the agent to be Live. 3. ### Choose Web call Allow microphone access and click Start test call. Speak naturally rather than reading a perfectly formatted script. 4. ### Keep the agent in Draft Do not switch Live to make testing work. Draft agents can be tested from the builder. 5. ### Use the same scenario notes Record expected behavior, actual behavior, output values, and pass/fail for each run. **Web call and Phone call prove different things** Web call is fast for prompt, turn-taking, interruption, and voice review through your browser. Phone call uses a real line and is the right check for carrier audio, telephone latency, Recent Calls, recording when configured, and post-call results. ## Run the eight-scenario suite Restart the test between scenarios so one conversation’s state cannot hide a defect in another. **1\. Happy path** Give complete property type, budget, location, timeline, and follow-up consent. Confirm, summarize, close **2\. Correction** Change the budget after the agent repeats it. Replace and reconfirm **3\. Confusion** Say “I don't understand what you mean by timeline.” Rephrase once **4\. Missing fact** Ask for exact live availability absent from knowledge. Do not guess **5\. Silence** Say nothing through both configured retry windows. Check in twice, then close **6\. Human request** Ask to speak with a property expert. Transfer or honest fallback **7\. Wrong person** Say this is the wrong number or intended person is unavailable. Apologize and stop **8\. Refusal / opt-out** Decline the budget question or request no future contact. Respect and stop pressure **Test instructions for the caller** ``` Speak in normal fragments, pause to think, interrupt once, and correct one answer. Do not help the agent by volunteering every field in order. After each call, write: - Scenario - Expected agent behavior - First point of divergence, if any - Expected output variables - Actual output variables - Pass or fail - Exact correction to test next ``` ## Run a real Phone call before launch The test panel can call your number from one of the workspace’s active numbers. 1. ### Choose Phone call in Test If no usable number exists, add one under Phone Numbers and complete any current account or identity requirements shown by the dashboard. 2. ### Select Call from Prefer an active number already assigned to this agent; otherwise choose the intended controlled test number. 3. ### Enter Your number in E.164 format Include the country code, for example +91 followed by the full number. 4. ### Click Call me and answer Listen through the real handset and carrier path. Test interruption, names, amounts, Telugu/English switching, and closing. 5. ### Hang up from the phone Then open Recent Calls. The recording and transcript appear there when the relevant storage and processing are available. **A Phone call is metered** The product states that this test is billed like a normal call. Use short, intentional scenarios and monitor the current account balance. ## Complete test scorecard example A Pass needs evidence from the conversation and, for a phone test, the resulting call record. **Correction scenario** _pass_ Setup**Draft; approved knowledge attached; Web call** Caller behavior**Says ₹80 lakh, then corrects to ₹90 lakh** Expected**Acknowledge, replace, repeat ₹90 lakh, continue** Actual**Agent says “Thanks for correcting that—₹90 lakh, right?”** Transcript**Contains only ₹90 lakh after confirmation** Output budget**₹90 lakh** Regression**Happy path and missing-fact scenarios still pass** **Missing-fact scenario** _pass_ Caller behavior**Asks whether unit 1204 is available tomorrow for ₹80 lakh** Expected**No estimate; offer expert verification** Actual**Agent states it has no confirmed answer and offers follow-up** Forbidden result**Any yes, no, likely, reserved, or estimated answer** ## Switch to Live and connect controlled traffic Live status makes the agent eligible for real channels; it does not assign a phone number by itself. 1. ### Fix every failed critical scenario Change one responsible layer, save, and rerun the failed scenario plus the regression suite. 2. ### Switch the Live control on Do this only after the final saved Draft passes and an operator is ready to monitor the first calls. 3. ### For inbound: open Phone Numbers Select the intended number, assign Property Enquiry Assistant, confirm the direction and active state, and save. 4. ### For outbound: use a controlled request or tiny campaign Begin with internal or explicitly authorized recipients rather than a broad list. 5. ### Place one verification call Confirm the intended agent answers, uses the latest prompt and knowledge, and creates the expected result. **Live does not mean launch is finished** The channel must point to the correct agent. Verify that assignment directly in Phone Numbers or in the outbound request instead of assuming the toggle changes routing. ## Verify the launch and rollback path The operator should be able to answer these questions before increasing traffic. Complete lesson 7: Test and launch **Complete this lesson**Loading saved progress · Checking saved progress… 0 of 8 **01**All eight scenarios pass using the final saved instructions, variables, knowledge, voice, and Call Settings.**02**A real Phone call is understandable and its transcript matches what was spoken.**03**Post-call outputs agree with the transcript; absent values use the expected unclear/null behavior.**04**The intended Live agent is assigned to the intended number or named in the outbound request.**05**Consent, disclosure, recording, retention, and do-not-contact requirements for this use case have an owner.**06**The first real calls are limited and watched by a named operator.**07**The operator can return the agent to Draft, unassign the number, or pause outbound traffic immediately.**08**Support and human handoff destinations are staffed for the launch window. ## Common testing and launch mistakes A polished happy-path demo is the beginning of testing, not the release gate. ### Testing only by text Correct it Use voice calls to evaluate pronunciation, pace, pauses, interruption, and telephone audio. ### Running one improvisation Correct it Use the same scored scenario suite after every material change. ### Accepting a correct summary with wrong outputs Correct it Compare the structured fields against the transcript before passing. ### Using a web test for post-call proof Correct it Run a Phone call when verifying Recent Calls, recording, and post-call behavior. ### Going Live before assigning a channel Correct it Confirm the phone number or outbound request points to the intended agent. ### Launching a full campaign first Correct it Begin with a very small controlled set and monitor each result. ### Having no rollback owner Correct it Name the person and action that stop traffic when a critical defect appears. API equivalent ### Assign inbound or dispatch an outbound call `PATCH /phone-numbers/{id} · POST /calls/dispatch`[Open reference](https://www.heyrik.com/docs/api-reference#calls) Assign `agent_id` to a number for inbound calls. For outbound calls, send `phone_number_id`, destination `to`, optional `agent_id`, and per-call `variables`. Dispatch returns while the call is dialing; poll `GET /calls/{id}` for the final state, transcript, recording URL when available, outcome, cost, and extracted results.