Compare browser tests and live calls
Browser tests and live calls share the voice runtime, transcript capture, call storage, and credit billing, but they do not represent the same deployment state.
| Behavior | Browser voice test | Live phone call |
|---|---|---|
| Configuration | Current draft snapshot authorized for the test session | Published configuration resolved when the call starts |
| Phone number | Not required | Inbound calls require an assigned active number |
| Call record | Created in Call Logs | Created in Call Logs |
| Contact record | Test contact is created | Caller contact can be created or enriched |
| Transcript | Saved when the test closes | Saved when the media session closes |
| Credit usage | Billed from test duration | Billed from answered live duration |
| Post-call AI analysis | Not currently run | Runs for a non-empty transcript |
| Tools | Available in private tests; shared tests can disable them | Filtered by attachment and connected integration state |
Private and shared browser tests
A private test can exercise attached tools. A shared test link follows its configured tool permission and can impose a maximum duration. Do not enable mutating tools on a shared test unless you intend external testers to invoke them.
Both test types require an authorized, unexpired test session and available workspace credits. A test creates stored operational data; it is not a disposable preview.
Test the draft, verify the published agent
- Use a private browser test while editing the draft.
- Inspect its Call Logs transcript and credit entry.
- Validate tool side effects in the destination integration.
- Publish the tested configuration.
- Place a real phone call through the assigned number.
- Verify duration, transcript, outcome, contact enrichment, and credits again.
A successful browser test does not prove phone routing, provider audio transport, caller ID, or published-version behavior. A successful live call does not prove that later unpublished draft changes work.
Interpreting test outcomes
Because browser tests do not run the live post-call analyzer, they may lack the enriched summary or classified outcome expected on live phone calls. Evaluate the transcript and tool result directly rather than waiting for live-only enrichment.