Boni

Voice API

Programmable voice for Indian business calls.

Launch Indian business numbers, route inbound calls to your app, team, AI agent, Bow Chat, SIP endpoint, or custom voice stack, and keep call events measurable without exposing carrier complexity.

Starts at Rs 500 per number per month. Inbound included under fair use.

Voice control plane

Numbers, routes, events, AI handoff

API-ready

Number

India business line

Route

Webhook, team, AI, SIP

Connect

Bow Chat, app, PBX, agent stack

Event

Missed, answered, completed

Record

Log, recording, summary

Capabilities

Call infrastructure packaged for products and operations teams.

Boni keeps the telephony layer abstracted while giving buyers the controls they actually need: numbers, routing, call events, logs, recordings, and handoff.

Indian DID by API

Get a dedicated Indian business number, receive inbound calls under fair use, and route each call to the right workflow.

Business numbers

Set up Indian numbers for sales, support, branches, campaigns, marketplaces, and operations without exposing carrier setup.

Inbound call control

Route calls by number, branch, language, team, business hours, caller context, fallback, or custom policy.

Bring any voice endpoint

Route to a decision webhook, Bow Chat, hosted AI, a fallback phone, SIP, or an advanced voice endpoint when your stack needs it.

Call event webhooks

Use answered, missed, completed, failed, recording-ready, and handoff events to update your own systems.

Logs and recordings

Keep call records, disposition fields, recordings, notes, and reporting hooks connected to customer context.

India-ready voice AI

Build intake, qualification, summaries, multilingual handoff, and human escalation for Indian call patterns.

Entry points

Choose the starting point that matches your call workflow.

Start with the outcome you need: a number to receive calls, an API route for your product, or a team workspace through Bow Chat. Specialized connector setup lives in the relevant child page after the core route is clear.

India DID by API

For teams that want a simple Indian number, inbound routing, webhooks, logs, and a fast first call.

Open DID page

LiveKit connector

Use the dedicated LiveKit setup page only when LiveKit is the chosen destination for your voice application.

Open connector page

Vapi route

For teams whose voice agent already runs on Vapi and needs an Indian DID, fallback, and first-call validation.

Open Vapi page

Retell route

For teams whose Retell AI setup needs an Indian number, custom telephony handoff, and route evidence.

Open Retell page

Bow Chat Voice

For sales and support teams that want the same voice layer inside a customer operations workspace.

See Bow Chat Voice

Video walkthroughs

Watch the call routing layer that sits behind the API.

Boni Voice is strongest when the number feeds a visible workflow. These Bow Chat videos show how calls can route to teams, keep caller context, leave logs, and hand off to AI or human follow-up.

Voice routing demo

Inbound call routing demo

A Bow Chat calling demo used as Boni Voice proof: an inbound call reaches the team workspace, keeps caller context visible, and creates a follow-up trail instead of disappearing into one phone.

Get the India DID layer

Built for Indian call realities.

Indian voice operations involve language shifts, noisy environments, callbacks, missed-call behavior, branch routing, and handoff-heavy workflows. Boni Voice API is designed around those operational patterns.

Developer number launch

Start with a +91 business number, a scoped panel account, and a route you can test before sending real callers.

Marketplace calls

Connect buyers, sellers, drivers, agents, or vendors without losing visibility into the call journey.

Sales and support lines

Give teams dedicated business numbers with routing, missed-call recovery, and customer context.

Branch routing

Send calls to the right city, store, workshop, clinic, or field team without hardcoded manual rules.

AI intake

Let voice AI collect basic requirements, qualify intent, and hand off to humans when the conversation needs judgment.

Implementation

Start from the call journey, not the carrier setup.

1

Choose the number model

Use a dedicated business number or an assigned number pool for a branch, campaign, workflow, or product.

2

Define routing policy

Map each number to teams, time windows, queues, hosted AI, fallback paths, SIP targets, or external webhooks.

3

Operate calls

Receive inbound calls, log outcomes, and keep recordings or summaries available where enabled.

4

Improve workflows

Use call events and reports to tune staffing, follow-up, campaign attribution, and customer experience.

Voice API for platforms. Bow Chat Voice for teams.

Use Boni Voice API when you need programmable control in your own product. Use Bow Chat Voice when your sales or support team needs calling inside the customer workspace.

Team workspace

Calls can become customer events, missed-call tasks, notes, and follow-ups.

Controlled rollout

Keep provider details, secrets, routing policy, and recordings behind server-side systems.

FAQ

Can Boni support WhatsApp Cloud API Calling?

Yes. Boni can package WhatsApp Cloud API Calling as an API-first enterprise capability for eligible numbers, including enablement, routing, call events, logs, and Voice AI handoff.

Do I need a specific voice stack?

No. Boni Voice API is a general Indian business number and inbound routing product. You can route to webhooks, Bow Chat, hosted AI, SIP, fallback phones, or a custom endpoint. LiveKit has its own connector page when that is the stack you already use.

Is this only for support teams?

No. Boni Voice API can support sales, support, marketplaces, branches, campaigns, operations teams, and AI intake workflows.

Can this connect to Bow Chat?

Yes. Bow Chat can use the same voice layer to keep calls, missed-call tasks, customer records, notes, recordings, and summaries connected to team workflows.

Can we build voice AI for India?

Yes. Boni is designed for India-ready voice AI patterns such as multilingual intake, noisy real-world calls, structured capture, and human handoff.

Do you expose the underlying telephony infrastructure?

Public customers work with Boni Voice API, routing rules, events, logs, recordings, and integration support. Internal provider and infrastructure details stay abstracted.