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

# What Is a Voice Bot? How AI Voice Agents Handle Calls

> A voice bot holds spoken conversations on phone calls. See how the pipeline works, where each turn loses time, how barge-in works, and India's 2026 A2P rules.

*November 3, 2026 · By [Piyush Sahoo](https://www.linkedin.com/in/piyush-s713/)*

A voice bot is software that holds a spoken conversation over a phone call or microphone, with no person on its side of the line. It detects when you stop talking, turns your speech into text, decides what to do, and speaks a reply. An AI voice agent is a voice bot driven by a language model.

Most explanations stop at that pipeline. This guide follows what happens on a real phone line: the time budget for one turn, the mechanics of interruption, what 8 kHz audio changes, why Indian speech is a harder test, and the rules that apply before an outbound bot dials anyone.

> [!NOTE]
>
> **Key takeaways**
>
> * **"Voice bot" covers a range.** Ask who decides the next step: a menu tree, an intent classifier, or a language model. That answer predicts how the bot will fail.
> * **The clock is the product.** One published guide targets about 1,000 ms per turn at the 95th percentile, while human answers commonly start within 200 ms. Transport, transcription, and the model's first token each take a large share.
> * **Interruption has a memory problem.** Stopping the audio is the easy half. The bot must also forget words the caller never heard.
> * **Test Indian speech on phone audio.** A shared code-switching benchmark on Hindi-English and Bengali-English started at about 32% word errors.
> * **India now regulates the automation itself.** TRAI's Third Amendment makes senders declare automated calls in advance, and treats undeclared ones as unsolicited. Those rules start no earlier than mid-November 2026.

## What is a voice bot, and how is it different from a voice agent?

The terms overlap, so define them by behaviour. Voice assistant, voice AI, voice bot, and conversational IVR often get treated as one family. A useful line runs inside that family: voicebot is the broad term that includes scripted systems, while "AI voice agent" usually implies flexible reasoning, multi-turn state, and tools.

The more useful test is who chooses the next step:

| Type | Who decides the next step | What the caller can do | How it usually fails |
| - | - | - | - |
| **Touch-tone IVR** | A designed menu tree | Press keys | The need isn't on the menu |
| **Speech-enabled menu** | A menu tree plus a phrase recogniser | Say listed phrases or press keys | It mishears a phrase, or the caller goes off-list |
| **Intent-based bot** | A classifier plus dialogue rules | Speak freely within trained intents | The request falls outside the trained set |
| **LLM voice agent** | A language model, bounded by a prompt and tools | Speak freely, across several turns | A confident wrong answer, or the wrong tool call |
| **Speech-to-speech agent** | One model that takes audio and returns audio | Speak freely, sometimes while it talks | The same, with fewer stages you can inspect |

If you know [IVR systems](https://www.vobiz.ai/docs/blogs/what-is-an-ivr.md), the top two rows will look familiar. A chatbot can share the reasoning of the lower rows, but it never deals with silence, overlap, or a noisy line. Consumer assistants on a phone or speaker are a different product again, because a business voice bot usually has one narrow job and access to your systems.

## How does a voice bot handle a phone call?

Two layers do the work. The telephony layer gets audio to and from the caller. The speech and reasoning layer runs once per turn.

![Architecture of a voice bot on a phone call. A caller reaches a telephony provider through the phone network. A SIP trunk or WebSocket stream carries audio to turn detection, speech to text, agent logic with tools and data, and text to speech, and the reply returns over the same transport. A speech-to-speech model can replace three stages, and a human handoff is the exit.](https://mintcdn.com/vobizai/z5oX7_m8UPZK5FG2/images/blog/what-is-a-voice-bot/pipeline-light.svg?fit=max\&auto=format\&n=z5oX7_m8UPZK5FG2\&q=85\&s=854f9be83ce2230cf058cb090c227d9c)

The four stages each have one job and one common way to fail:

1. **Turn detection.** It decides that the caller has finished. [LiveKit's documentation](https://docs.livekit.io/agents/logic/turns/) describes the options, from plain voice activity detection to a model that weighs both the meaning and the sound of speech. A trigger-happy setting talks over people, and a cautious one leaves dead air.
2. **Speech to text.** It produces a running transcript. A wrong account number here poisons everything downstream, so [transcription quality on telephone audio](https://www.vobiz.ai/docs/blogs/what-is-voice-transcription-asr.md) deserves its own test set.
3. **Agent logic.** Rules or a language model choose the reply and any tool call. A slow tool stalls the whole turn, because the caller hears nothing while it runs.
4. **Text to speech.** It generates audio, ideally streaming from the first words of the reply. If it reads ₹1,50,000 digit by digit, the caller loses trust quickly.

OpenAI's voice agent guide lists three architectures, and two of them frame the main choice. A [chained pipeline suits you when each stage must be visible or replaceable](https://developers.openai.com/api/docs/guides/voice-agents), for example to run a policy check on text before the bot speaks. A single speech model gives you fewer parts to connect and fewer points at which to intervene. The third, a full-duplex live model, keeps talking while a separate backend does the work.

## Where does the time go in a single turn?

Time starts when the caller stops speaking and ends when they hear the bot. This is the turn gap. [Deepgram's guide](https://deepgram.com/blog/real-time-voice-ai-stack-agents-architecture-guide) suggests a 95th percentile turn under about 1,000 ms and gives planning figures for each stage. Those figures use different measurement boundaries, so treat them as a starting yardstick rather than a sum.

![Range chart of one voice bot turn. SIP or PSTN transport adds 200 to 400 milliseconds, speech to text takes 200 to 500, LLM first token is planned at 200 to 400, and text to speech first byte can be as low as 80. Markers show the human response peak at 0 to 200 milliseconds, 700 milliseconds, where long human gaps start to signal reluctance, and a 95th percentile turn target of about 1,000 milliseconds.](https://mintcdn.com/vobizai/vn3KxdUq6H3224WW/images/blog/what-is-a-voice-bot/turn-clock-light.svg?fit=max\&auto=format\&n=vn3KxdUq6H3224WW\&q=85\&s=6f7d78183a6fa947598f6bcda91c8ec3)

Two findings from conversation research show why this gap matters:

* **People answer fast.** Across ten languages, [response timing to questions peaks between 0 and 200 ms](https://pmc.ncbi.nlm.nih.gov/articles/PMC2705608/). That sample didn't include an Indian language, so treat it as a broad human baseline.
* **Silence carries meaning.** Corpus work links [gaps of 700 ms or more with disagreeing or declining responses](https://pmc.ncbi.nlm.nih.gov/articles/PMC4464110/). A bot that always pauses for a second can sound reluctant, even when its answer is yes.

These levers move the budget most, so spend your effort there:

| Lever | What to do | The trade-off |
| - | - | - |
| **End-of-turn detection** | Replace a fixed silence timer with a model | Cutting the timer alone means interrupting people mid-thought, which feels worse than waiting |
| **Model first token** | Choose by time to first token, then stream | A faster model may reason less well, so split hard reasoning into a backend call |
| **Tool calls** | Speak a short bridge such as "let me check that", and set a timeout on every tool | Deepgram's guide cites work putting [tool calls at 30 to 80% of latency](https://deepgram.com/blog/real-time-voice-ai-stack-agents-architecture-guide) before the final answer starts |
| **Placement** | Keep media, speech, and reasoning services close together and near your callers | Regional capacity for a given model may be limited, so check it early |

Measure the slowest turns as well as the median. A caller remembers the four-second silence, not the average. Record each stage separately, or you can't tell a slow model from a slow network.

## How does barge-in work?

Barge-in means the caller can talk over the bot and be heard. It's the feature that separates a conversation from a recording, and it's harder than it looks because not every overlap is an interruption.

In a sample of 200 overlaps from a corpus of English telephone conversations, [73% involved a backchannel](https://pmc.ncbi.nlm.nih.gov/articles/PMC4464110/) such as "yeah" or "mm-hm". Those sounds mean "keep going". A bot that stops at every one will stall constantly. [LiveKit's adaptive interruption handling](https://docs.livekit.io/agents/logic/turns/) targets exactly this distinction, and the same page covers false positives, when noise triggers a stop and no words follow.

![Two timelines. In the first, the caller says mm-hm during playback, and the app keeps playing. In the second, the caller says no, the other one. The app confirms speech, clears queued playback, cuts unheard words from conversation history, and answers the new request.](https://mintcdn.com/vobizai/z5oX7_m8UPZK5FG2/images/blog/what-is-a-voice-bot/barge-in-light.svg?fit=max\&auto=format\&n=z5oX7_m8UPZK5FG2\&q=85\&s=5c54f9d0040340d516732abf6ae85ede)

The memory step is the one teams miss. The model generates faster than the phone plays, so its history can hold a sentence the caller never heard. On a managed platform, the platform owns this problem. If you own the pipeline, track playback position with markers and rewrite the history at the point of interruption.

## What does phone audio change?

A voice bot demo on a laptop microphone flatters every stage. A phone call is harder in four ways.

**The audio is narrow.** [G.711](https://en.wikipedia.org/wiki/G.711), the long-standing telephone codec, samples at 8 kHz, passes roughly 300 to 3,400 Hz, and runs at 64 kbps. Consonants such as "s" and "f" become hard to separate, and spelled-out names suffer most. Send your speech engine what the call actually gives you, and don't assume a higher upstream sample rate adds detail that the phone leg removed.

**The transport has a character.** SIP calls carry audio over [RTP](https://datatracker.ietf.org/doc/html/rfc3550), usually on UDP, where a lost packet simply disappears. [WebSocket](https://datatracker.ietf.org/doc/html/rfc6455) streams run over TCP, where a lost packet is resent and later audio waits for it. Neither is free: one loses a fragment, and the other can add jitter on a poor network.

**The stream has a bandwidth cost.** Base64 text [adds a third to the raw size](https://datatracker.ietf.org/doc/html/rfc4648), and slightly more once each frame is padded. [Stream formats on Vobiz](https://www.vobiz.ai/docs/concepts/streaming-websockets.md) are documented by frame size. We calculated the load for one direction of one call, at 20 ms frames, before JSON and TLS overhead:

| Format | Raw bytes per 20 ms | Raw rate | With Base64 | For 100 concurrent calls |
| - | -: | -: | -: | -: |
| μ-law, 8 kHz | 160 | 64 kbps | 86.4 kbps | 8.6 Mbps |
| L16, 8 kHz | 320 | 128 kbps | 171.2 kbps | 17.1 Mbps |
| L16, 16 kHz | 640 | 256 kbps | 342.4 kbps | 34.2 Mbps |
| L16, 24 kHz (outbound only) | 960 | 384 kbps | 512 kbps | 51.2 Mbps |

**Each call holds more than a channel.** A bot call occupies a telephone channel and also an open speech-to-text session, a model stream, a text-to-speech stream, and server memory. Size channels as you would for any line: 1,000 calls in a busy hour at 3 minutes each is 50 erlangs, which needs 64 channels at 1% blocking by our Erlang B calculation. The [SIP trunking guide](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) walks through that math. Then check that your speech and model providers allow the same concurrency, because their limits often arrive first.

Outbound bots face one more phone-only problem: voicemail. A bot that greets on answer talks over the machine it's trying to classify. [Answering machine detection](https://www.vobiz.ai/docs/blogs/what-is-answering-machine-detection.md) works better when the bot stays silent until the result arrives.

## Why is Indian speech a harder test?

Callers in India often move between languages inside one sentence, and an off-the-shelf demo rarely shows what that costs.

The evidence is sobering. The [MUCS 2021 challenge](https://arxiv.org/abs/2104.00235), built on Hindi-English and Bengali-English code-switched speech among other sets, reported a baseline of 32.45% word error on its code-switching test. A [later paper on the same problem](https://arxiv.org/pdf/2203.16578) reached 21.77 on Hindi-English and 28.27 on Bengali-English. That's still roughly one word in four or five, and these are older research systems, so treat them as a warning and test on your own calls.

Build your evaluation around what breaks in Indian deployments:

| What callers do | Why it breaks | What to test or change |
| - | - | - |
| Mix Hindi and English: "mera EMI date change karna hai" | One-language models lose words at the switch point | Score on recorded phone calls from your own audience, with both scripts accepted in the reference |
| Say numbers in another language or as "double five" | One wrong digit voids a phone number, amount, or date | Read the value back and confirm, or switch to key presses |
| Use lakh and crore | A reply read in millions confuses, and a wrong amount misleads | Normalise amounts before text to speech, and listen to the result |
| Speak from a street or a shop | Other voices can trigger barge-in | Test noise cancellation and a stricter interruption threshold |
| Have a regional name or locality | Speech engines guess at rare words | Add expected terms as hints where your engine supports them, and confirm spellings |

Key presses still matter here. [RFC 4733](https://datatracker.ietf.org/doc/html/rfc4733) carries DTMF as events rather than speech, so a keypad entry skips speech recognition altogether. Use it for a PIN, a date of birth, or any value the caller shouldn't say aloud near other people.

## Which rules apply to a voice bot in India?

India now regulates the method of calling as well as its content. These points come from regulator documents, where we could read them. They change often, so confirm the current text and take legal advice.

![Five checks before an outbound bot calls in India. Declare automated calling and caller ID ranges to the originating provider. Pick the series: 140xx for promotional calls, 1600xx for service calls by entities regulated by RBI, SEBI, IRDAI, or PFRDA, and government. Check consent and Do Not Disturb. Design the opening, the human exit, and recovery call hours. Plan notice, retention, and deletion for personal data.](https://mintcdn.com/vobizai/z5oX7_m8UPZK5FG2/images/blog/what-is-a-voice-bot/india-preflight-light.svg?fit=max\&auto=format\&n=z5oX7_m8UPZK5FG2\&q=85\&s=d7f255c871a73cd1c7a4768c80f6f5bd)

| Topic | What it says | Source and date |
| - | - | - |
| **A2P definition** | A voice call an application or automated platform starts without direct human dialling, including artificial voice | [TCCCPR Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf), September 2026 |
| **Declaration** | Senders declare A2P use and caller ID ranges to the originating provider in advance. Undeclared calls count as unsolicited | [TRAI press release 119/2026](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), September 2026 |
| **Termination charge** | Up to ₹0.05 per minute between operators on A2P calls, with 140xx, 1600xx, and 1601xx series exempt | [TCCCPR Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf), September 2026 |
| **Number series** | 140xx for promotional calls from any sector. 1600xx for service calls by entities regulated by RBI, SEBI, IRDAI, or PFRDA, and for government | [TRAI press release 91/2026](https://www.trai.gov.in/sites/default/files/2026-07/PR_No91of2026.pdf), July 2026 |
| **Complaint trigger** | Action can start at 3 or more unique complaints in ten days, when an AI system has also flagged the caller ID | [TRAI press release 119/2026](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), September 2026 |
| **Inquiries** | A written or digital inquiry supports commercial calls for seven days, and the sender keeps verifiable proof | [TRAI press release 119/2026](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), September 2026 |
| **Loan recovery** | Regulated entities must make sure they and their agents don't phone about overdue loans outside 8 am to 7 pm. New [amendment directions](https://www.rbi.org.in/ScriptS/BS_PressReleaseDisplay.aspx?prid=63305) apply from 1 January 2027, and [RMAI's summary](https://rmaindia.org/rbis-new-loan-recovery-directions-2026-what-banks-and-nbfcs-must-do-before-january-2027/) says they keep this window unless the borrower asks otherwise | [RBI circular](https://rbi.org.in/Scripts/NotificationUser.aspx?Id=12378\&Mode=0), August 2022, and RBI press release, August 2026 |
| **Personal data** | Rules set an 18-month phased timeline and need standalone, plain consent notices | [PIB on the DPDP Rules](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2190014\&reg=3\&lang=2), November 2025 |

Four points deserve a closer look.

**The trigger is the technology, not the script.** TRAI's reasoning in the [Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) rejected requests to exclude calls with a live human agent, and said the rules apply to all A2P calls rather than only commercial ones. It also notes that a network may not be able to tell an artificial voice from a real one, which is why the duty falls on declaration. An outbound voice bot fits this wording. An inbound bot that only answers calls doesn't appear to, since the definition turns on who starts the call. That's our reading, so confirm it with your counsel.

**Check the start date for your launch.** The notification is dated 18 September 2026, and the A2P declaration and charge start 60 days after Gazette publication. We could not confirm the publication date. Publication can't come before the notification, so those two provisions can't start earlier than mid-November 2026. Most other provisions start after 30 days, and the rule that pairs complaints with AI flags starts after 90 days.

**Enforcement already reaches SIP.** [TRAI's explanatory text](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf) reports that in April 2026, 15,736 of 20,591 disconnections were SIP or PRI connections, roughly three in four. Our [SIP trunking guide](https://www.vobiz.ai/docs/blogs/what-is-sip-trunking.md) covers the wider penalties.

**Say that it's automated.** Confirm with your counsel whether a rule requires business calls to say they're AI. We recommend the practice either way: name the business, say it's an automated assistant, and offer a person early.

The DPDP timeline matters for recordings and transcripts, since both usually identify a person. The DPDP Rules' 18-month phased timeline, counted from November 2025, runs to about May 2027, so design for notice, consent, security, and breach duties now. If you also call the US, the FCC [confirmed in February 2024 that "artificial or prerecorded voice" limits cover current AI-generated voices](https://docs.fcc.gov/public/attachments/FCC-24-17A1.pdf), which brings those calls under TCPA consent rules.

## Which kind of voice bot should you build?

Start with the simplest thing that does the job. Each step down this map adds cost and adds ways to fail, so a generative model isn't automatically the upgrade.

![Decision map. If callers' needs fit a few fixed choices, use a speech-enabled menu. If every sentence must be approved in advance, use a scripted intent bot. If you don't need to own each pipeline stage, use a managed platform over a SIP trunk. Otherwise, build your own pipeline over a WebSocket stream. Every branch keeps a human exit.](https://mintcdn.com/vobizai/z5oX7_m8UPZK5FG2/images/blog/what-is-a-voice-bot/decision-map-light.svg?fit=max\&auto=format\&n=z5oX7_m8UPZK5FG2\&q=85\&s=b24585d0f478d400aac49124f4e733bf)

The last two branches split on ownership, and [SIP vs WebSockets](https://www.vobiz.ai/docs/concepts/sip-vs-websockets.md) compares them in detail:

| | Managed platform over SIP | Own pipeline over WebSocket |
| - | - | - |
| **Turn-taking and interruption** | The platform handles them | You build them |
| **Model choice** | What the platform supports | Anything you can connect |
| **Scaling** | Add channels, and the platform scales its own side | You scale workers as well as channels |
| **Existing PBX** | SIP fits naturally | No standard bridge |
| **Best for** | Reaching production quickly | Custom logic, tight data control, high volume |

## What goes wrong after launch?

A bot that passes a demo can still fail in three ways. Plan for each one before go-live.

**It says something false.** A generated answer sounds equally sure whether it's right or wrong. Keep facts such as balances, dates, and policies in tools, and let the model phrase them rather than recall them. Run a check on the text before speech when the wording carries legal weight.

**It gets talked into something.** A caller's speech is untrusted input to your model, so [direct prompt injection, as OWASP defines it](https://genai.owasp.org/llmrisk/llm01-prompt-injection/), applies to a phone line too. Give each tool only the access it needs. Enforce identity checks and limits in your backend rather than in the prompt, because the model shouldn't be the last line of defence.

**It looks successful while callers suffer.** Containment measures how many calls never reached a person, and containment targets can discourage human access. Read the numbers together:

| Metric | What it tells you | The trap |
| - | - | - |
| **Task completion** | Did the booking or update actually happen? | Check the system of record, not the transcript |
| **Containment** | How many calls stayed with the bot | High containment can mean no way out |
| **Repeat contact** | Did the caller come back within days? | The honest check on containment |
| **Turn gap at the slowest turns** | How the worst moments felt | Averages hide them |
| **False interruptions** | How often the bot stopped for nothing | Only visible if you log stop events |
| **Handoff success** | Did a person pick up, with context? | A transfer into an empty queue isn't a success |

Published containment and cost-saving ranges rarely state the call mix behind them, so set your own baseline from a small pilot.

## How Vobiz connects a voice bot to the phone network

Vobiz provides the telephony layer. You bring the bot, or use a platform that provides one.

* **Managed platforms.** Connect [Vapi](https://www.vobiz.ai/docs/integrations/vapi-dashboard.md), [Retell AI](https://www.vobiz.ai/docs/integrations/retellai-dashboard.md), [ElevenLabs](https://www.vobiz.ai/docs/integrations/elevenlabs-dashboard.md), or [LiveKit](https://www.vobiz.ai/docs/integrations/livekit.md) over a [SIP trunk](https://www.vobiz.ai/docs/concepts/sip-trunking.md). The [inbound](https://www.vobiz.ai/docs/guides/ai-voice-agent/inbound.md) and [outbound](https://www.vobiz.ai/docs/guides/ai-voice-agent/outbound.md) guides show the shared pattern.
* **Your own pipeline.** Return a [`<Stream>` element](https://www.vobiz.ai/docs/xml/stream) in VobizXML, or [start a stream over REST](https://www.vobiz.ai/docs/audio-streams/start-audio-stream.md), and [your WebSocket server](https://www.vobiz.ai/docs/integrations/websockets.md) receives call audio. [Pipecat](https://www.vobiz.ai/docs/integrations/pipecat.md) also uses this path. Stream status arrives through webhooks (callbacks) at `statusCallbackUrl`.
* **Audio formats.** [Inbound stream audio](https://www.vobiz.ai/docs/concepts/streaming-websockets.md) is L16 at 8 or 16 kHz, or μ-law at 8 kHz. Outbound playback adds L16 at 24 kHz, though the phone leg may use a lower-rate codec.
* **Barge-in.** Send [`clearAudio`](https://www.vobiz.ai/docs/xml/stream/clear-audio) to drop queued playback. Use a [`checkpoint`](https://www.vobiz.ai/docs/xml/stream/checkpoint-event) to learn when audio has finished playing, through a `playedStream` event. Cleared audio may not return that event, so give your logic a timeout. The [Stream events visualizer](https://www.vobiz.ai/docs/resources/stream-events-visualizer.md) steps through the sequence.
* **Scripted bots.** [`<Gather>` accepts speech and key presses](https://www.vobiz.ai/docs/xml/gather/detecting-speech-inputs) together with `inputType="dtmf speech"`, biases recognition with `hints`, and can send partial transcripts through `interimSpeechResultsCallback`. [`<Speak>`](https://www.vobiz.ai/docs/xml/speak) reads replies aloud, and [supported languages](https://www.vobiz.ai/docs/xml/gather/supported-languages.md) are listed per locale.
* **India-first speech.** [Sarvam's Samvaad platform](https://www.vobiz.ai/docs/integrations/sarvam.md) can rent numbers with Vobiz embedded, or you can connect a Vobiz account you already have.
* **Handoff.** The [Transfer a Call API](https://www.vobiz.ai/docs/call/transfer-call.md) redirects a live call to a new VobizXML URL, which can [`<Dial>`](https://www.vobiz.ai/docs/xml/dial) a person. Set `callerId` to a number your account owns or is authorised to use. [Agent-to-agent handoff](https://www.vobiz.ai/docs/solutions/agent-to-agent-handoff.md) describes the full pattern.
* **Voicemail.** [Machine detection](https://www.vobiz.ai/docs/call/machine-detection.md) offers starting profiles for AI callers, plus guidance on holding the first utterance until the result arrives.
* **Capacity and quality.** Check [concurrency](https://www.vobiz.ai/docs/platform/capacity/concurrency.md) and [CPS](https://www.vobiz.ai/docs/platform/capacity/cps.md), and model a campaign in the [calculator](https://www.vobiz.ai/docs/resources/calculator.md). Each [call detail record](https://www.vobiz.ai/docs/cdr.md) reports `mos`, `jitter`, and `packet_loss`.
* **Recording.** Trunks store `recording`, `enable_transcription`, and `pii_redaction` settings, listed in the [Trunks API](https://www.vobiz.ai/docs/trunks/retrieve-trunk.md).
* **India.** [Calling regulations](https://www.vobiz.ai/docs/compliance/india/calling-regulations.md) cover KYC, caller ID, and media anchoring. [DLT registration](https://www.vobiz.ai/docs/best-practices/dlt-registration.md) and [140 and 160 series acquisition](https://www.vobiz.ai/docs/best-practices/140-160-acquisition.md) cover commercial numbers. These series are outbound only, so pair them with a DID for inbound calls. The [UCC page](https://www.vobiz.ai/docs/compliance/india/ucc.md) covers complaints.

Test calls are billed to your account and reach real people. Run them with your own Auth ID and Auth Token, confirm each number first, and check that you have consent. Current rates are on the [Vobiz pricing page](https://www.vobiz.ai/pricing/).

## Frequently asked questions

> [accordion] What is a voice bot in simple words?
>
> A voice bot is software that talks with people over a call or microphone. It listens, works out what you want, and answers aloud. Simple bots follow a fixed script. Advanced ones use a language model and can act, for example by booking an appointment or looking up an order.

> [accordion] How does a voice bot work?
>
> Each turn runs through four stages. The bot detects that you have stopped talking, converts your speech to text, decides on a reply or action, and converts that reply to audio. A telephony provider carries the audio between the phone network and those stages.

> [accordion] What is the difference between a voice bot and an IVR?
>
> An IVR walks callers through a menu that someone designed in advance, usually with key presses. A voice bot lets callers state their need in their own words and works out the next step. Many voice bots still accept key presses for sensitive input such as a PIN.

> [accordion] Is a voice bot the same as an AI voice agent?
>
> Not quite. Voice bot is the broad term, and it includes scripted systems. AI voice agent usually means a bot built on a language model that keeps context across turns and calls tools to finish tasks. Vendors use the words loosely, so ask who decides each next step.

> [accordion] Are AI voice bots legal in India?
>
> We found no Indian law that bans them, but outbound bots carry duties. TRAI's Third Amendment treats automated calls as A2P calls, which senders must declare in advance. Rules on consent, Do Not Disturb, and number series also apply. Check the current text and take legal advice for your case.

> [accordion] How fast should a voice bot respond?
>
> Aim as low as you can without cutting callers off. Human answers commonly start within 200 ms, and one published guide targets a 95th percentile turn under about 1,000 ms. Measure from the caller's last word to the bot's first sound on real calls, including your slowest turns.

## Further reading on Vobiz

* [AI voice agent solution overview](https://www.vobiz.ai/docs/solutions/ai-voice-agent.md) · [Build an AI voice agent](https://www.vobiz.ai/docs/guides/ai-voice-agent.md) · [All integrations](https://www.vobiz.ai/docs/integrations.md)
* [Voice streaming over WebSockets](https://www.vobiz.ai/docs/concepts/streaming-websockets.md) · [SIP vs WebSockets](https://www.vobiz.ai/docs/concepts/sip-vs-websockets.md) · [SIP vs WebSocket visualizer](https://www.vobiz.ai/docs/resources/sip-vs-websocket-visualizer.md)
* [What is an IVR?](https://www.vobiz.ai/docs/blogs/what-is-an-ivr.md) · [What is a voice API?](https://www.vobiz.ai/docs/blogs/what-is-a-voice-api.md) · [Intelligent call escalations](https://www.vobiz.ai/docs/blogs/intelligent-call-escalations.md)

## Sources

**Indian regulators**

* TRAI, [Press release 119/2026 on the Third Amendment](https://www.trai.gov.in/sites/default/files/2026-09/PR_No119of2026.pdf), 18 September 2026.
* TRAI, [TCCCPR Third Amendment Regulations, 2026](https://www.trai.gov.in/sites/default/files/2026-09/Regulation_18092026.pdf), 18 September 2026.
* TRAI, [Press release 91/2026 on the 1600 and 140 series](https://www.trai.gov.in/sites/default/files/2026-07/PR_No91of2026.pdf), 10 July 2026.
* RBI, [Outsourcing of Financial Services: Responsibilities of regulated entities employing Recovery Agents](https://rbi.org.in/Scripts/NotificationUser.aspx?Id=12378\&Mode=0), 12 August 2022.
* RBI, [Amendment Directions on conduct in recovery of loans and engagement of recovery agents](https://www.rbi.org.in/ScriptS/BS_PressReleaseDisplay.aspx?prid=63305), press release, 6 August 2026.
* PIB, [Government notifies DPDP Rules to empower citizens and protect privacy](https://www.pib.gov.in/PressReleasePage.aspx?PRID=2190014\&reg=3\&lang=2), 14 November 2025.

**US regulator**

* FCC, [Declaratory Ruling on AI technologies and the TCPA (FCC 24-17)](https://docs.fcc.gov/public/attachments/FCC-24-17A1.pdf), February 2024.

**Standards and security**

* IETF, [RFC 3550: RTP](https://datatracker.ietf.org/doc/html/rfc3550), July 2003.
* IETF, [RFC 4648: Base16, Base32, and Base64 Data Encodings](https://datatracker.ietf.org/doc/html/rfc4648), October 2006.
* IETF, [RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals](https://datatracker.ietf.org/doc/html/rfc4733), December 2006.
* IETF, [RFC 6455: The WebSocket Protocol](https://datatracker.ietf.org/doc/html/rfc6455), December 2011.
* OWASP, [LLM01: Prompt Injection](https://genai.owasp.org/llmrisk/llm01-prompt-injection/).

**Reference**

* Wikipedia, ["G.711"](https://en.wikipedia.org/wiki/G.711).

**Research**

* Stivers et al., [Universals and cultural variation in turn-taking in conversation](https://pmc.ncbi.nlm.nih.gov/articles/PMC2705608/), PNAS, 2009.
* Levinson and Torreira, [Timing in turn-taking and its implications for processing models of language](https://pmc.ncbi.nlm.nih.gov/articles/PMC4464110/), Frontiers in Psychology, 2015.
* Diwan et al., [Multilingual and code-switching ASR challenges for low resource Indian languages](https://arxiv.org/abs/2104.00235), 2021.
* Chadha et al., [Code Switched and Code Mixed Speech Recognition for Indic languages](https://arxiv.org/pdf/2203.16578), 2022.

**Vendor documentation and guides**

* Deepgram, [Real-time voice AI stack for agents: Architecture guide](https://deepgram.com/blog/real-time-voice-ai-stack-agents-architecture-guide).
* LiveKit, [Turn detection and interruptions](https://docs.livekit.io/agents/logic/turns/).
* OpenAI, [Voice agents guide](https://developers.openai.com/api/docs/guides/voice-agents).

**Industry summary**

* Risk Management Association of India, [RBI's new loan recovery directions 2026](https://rmaindia.org/rbis-new-loan-recovery-directions-2026-what-banks-and-nbfcs-must-do-before-january-2027/).

> [card] [Connect your voice bot to Vobiz](https://www.vobiz.ai/docs/guides/ai-voice-agent.md)
>
> Put your voice bot on a real phone number with a SIP trunk or a WebSocket stream.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.