Voice Simulation

Separate text-tier reasoning and tool coverage from real-audio tests of transcription, speech, turn-taking, latency, and transport health.

Voice testing answers two different questions: does the agent choose the right behavior, and does the audio path deliver that behavior correctly? The platform treats these as separate tiers so a media failure does not look like a reasoning regression, and a correct transcript does not hide an audio problem.

Testing Tiers

Tier	What Runs	What It Validates
Text simulation coverage	Synthetic caller text through the production reasoning engine and tool path	Context graph navigation, response content, tool selection and results, state coverage, and configured evaluations
Real-audio testing	A controlled caller through the end-to-end voice path	Media attachment, transcription, speech rendering, barge-in and turn timing, latency, disconnect behavior, and capacity

Teams can reuse the same scenario intent and review criteria across the tiers, but the platform does not treat their evidence as one identical run. Text coverage does not exercise telephony or audio transport. Real-audio testing does.

Text Simulation Coverage

Text simulation runs the actual context graph, model decisions, tool execution, world-model access, and turn policies without allocating a live audio session. The caller side is generated as text.

Simulation effects are isolated by source:

• World-model writes retain simulation provenance.
• Simulation writes are excluded from production EHR delivery and production analytics.
• Surface delivery and the approval workflows that depend on it are disabled.
• Reads use current workspace state, not a frozen snapshot or temporary database branch.

Use dedicated test entities when a stable starting point matters. Saved cases, suites, forks, and coverage graphs make repeated runs comparable, but model sampling, current workspace data, and updated agent versions mean reruns are not guaranteed to be byte-for-byte identical.

Real-Audio Testing

Real-audio tests place a controlled caller on the production voice path. They validate behavior that a text simulation cannot observe:

• Audio session startup and media attachment
• Speech recognition and synthesized speech quality
• Barge-in, silence, and turn-boundary behavior
• End-to-end latency and disconnect handling
• Cold-start and concurrent-call capacity

These tests are slower and environment-dependent because they use the real media path. Run them for audio changes, pre-release smoke tests, and capacity validation rather than using them as a substitute for broad text-tier regression coverage.

Choosing a Tier

• Use text simulation coverage for context graph changes, prompt and tool regressions, saved-case suites, and systematic state exploration.
• Use real-audio testing for speech, timing, transport, or fleet changes.
• Use both when a release changes agent behavior and the voice path together.

Interfaces

The Developer Console Simulations workspace and the Platform API coverage resources manage text-tier cases, suites, runs, sessions, forks, and graphs. Agent Forge exposes the same supported coverage surface through forge platform simulation ... and the bridge shortcut forge platform sim bridge ....

Real-audio tests run through separate call-based test workflows. They are not configuration-space sampling jobs and do not use the retired sim create, sample, or evaluate endpoints.

See Simulation Coverage for the supported API contract and Agent Forge CLI for current commands.