> ## Documentation Index
> Fetch the complete documentation index at: https://dialnexa.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Web Calls In DialNexa

> Understand DialNexa web calls, browser-based call sessions, web call creation, termination, microphone audio, transcripts, recordings, and monitoring.

Web calls in DialNexa are Voice AI calls started through a browser or web experience instead of a phone number route. They are useful for testing agents, embedded experiences, and situations where you want to remove the phone network from the first round of debugging.

<Tip>
  A web call removes the phone network from the path. It does not remove microphone problems, unclear prompts, or the need to review evidence.
</Tip>

## Web Call Versus Phone Call

| Area             | Web call                                                                    | Phone call                                                                       |
| ---------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Entry path       | Browser or embedded web surface.                                            | Plivo number, SIP trunk, batch campaign, workflow call node, or outbound launch. |
| Route dependency | May not require a phone number.                                             | Depends on number assignment or outbound route.                                  |
| Audio source     | Browser microphone.                                                         | Phone network or SIP media path.                                                 |
| Review path      | Call History and call detail.                                               | Call History and call detail.                                                    |
| Best use         | Agent testing, demos, embedded web experiences, and microphone-based flows. | Production inbound and outbound phone traffic.                                   |

## What To Review

Use the same evidence discipline as phone calls.

<CardGroup cols={2}>
  <Card title="Transcript" icon="file-text" href="/monitoring/transcripts-recordings-and-summaries">
    Did browser audio become accurate text?
  </Card>

  <Card title="Recording" icon="headphones" href="/voice-ai/background-noise-denoising-and-audio-quality">
    Was the microphone clear enough?
  </Card>

  <Card title="Status" icon="activity" href="/reference/statuses">
    Did the web call complete, fail, or terminate early?
  </Card>

  <Card title="Post-call fields" icon="list-checks" href="/monitoring/post-call-analysis-results">
    Were structured outcomes extracted correctly?
  </Card>
</CardGroup>

## Creation And Warmup Behavior

When you create a web call, DialNexa validates the organization, wallet balance, selected agent, and published version before creating a web call session. The response returns a `session_id`, `call_id`, and websocket URL when Speech returns a usable session.

Provider warmup is non-blocking for web calls. DialNexa can return the websocket URL while provider connections continue warming in the background, so the browser can connect without waiting for every provider to finish setup.

If Speech cannot create a usable session, DialNexa returns a `502` error with the stored failure message instead of returning a fake successful session. Treat that as a creation failure and check the agent version, provider readiness, wallet, and server error detail.

## Browser Audio Checks

<Steps>
  <Step title="Grant microphone permission">
    The browser must allow microphone access before the call can capture usable audio.
  </Step>

  <Step title="Use headphones for testing">
    Headphones reduce echo from the agent voice re-entering the microphone.
  </Step>

  <Step title="Speak at production pace">
    Do not perform slow demo speech if real users will interrupt, pause, or answer briefly.
  </Step>

  <Step title="Compare with a phone call">
    If a web call works but phone calls fail, the issue is likely telephony path, carrier audio, or number routing.
  </Step>
</Steps>

## Web Call Questions

<AccordionGroup>
  <Accordion title="Can a web call be terminated?">
    Yes. DialNexa includes a web call termination path and stores the resulting call state.
  </Accordion>

  <Accordion title="Does it use the same agent settings?">
    The selected agent version still controls prompt, voice, model, transcriber, functions, and post-call analysis.
  </Accordion>

  <Accordion title="Can I use web calls to validate production phone behavior?">
    Use web calls to validate the agent. Use phone calls to validate the telephony path.
  </Accordion>
</AccordionGroup>

## Related Reading

<CardGroup cols={2}>
  <Card title="Call History" icon="activity" href="/monitoring/call-history">
    Find web call records.
  </Card>

  <Card title="Call Detail Page" icon="panel-right" href="/monitoring/call-detail-page">
    Inspect the call.
  </Card>

  <Card title="Phone Numbers" icon="phone" href="/calls/phone-numbers">
    Compare phone-routed calls.
  </Card>

  <Card title="Audio Quality" icon="waves" href="/voice-ai/background-noise-denoising-and-audio-quality">
    Review browser audio issues.
  </Card>
</CardGroup>