Build a VAANI voicebot¶
VAANI owns the reusable voice runtime. Your bot owns the conversation and business work.
VAANI
1.0.0rc43is the current private runtime in Google Artifact Registry. It contains the merged #173–#177 provider-reliability work and uses immutable Birla presetbirla-prod-v42@14. Itsrheavoice is a controlled A/B setting, not cosmetic tuning.create-vaani-app0.2.1rc19generates projects pinned to the audited rc43 runtime, andvaani-evals0.1.1supports compatible Vaani 1.x releases. See Release status.
The rc43 private-publication record, including exact hashes and validation scope, are in release status. Credentialed GCS, Ozonetel/Salesforce, and consumer-owned LiveKit/SIP validation were not run.
Start here¶
- Authenticate, install, and generate a project.
- Run a real browser voice call.
- Use the project map.
- Configure development and production.
- Add prompts, caller data, and tools.
- Test, then deploy and operate.
Deployments that need a bounded accept/reject decision before Assistant setup can use the LiveKit job-admission hook.
For remote simulated-user evaluation, use the dedicated fail-closed evaluation worker; the older release-evidence transport alone does not prove business-provider safety.
The generated project pins the approved private runtime. Never install the
unrelated public-PyPI package with a bare pip install vaani.
Who owns what¶
| Your bot and deployment | VAANI |
|---|---|
| greeting, prompts, and customer lookup | LiveKit worker and media path |
| business state and API tools | configured STT, LLM, and TTS |
| secret values and named transfer destinations | turn taking, VAD, interruption, and silence timing |
| frontend, tokens, SIP, and infrastructure | standard call tools and live transcripts |
| monitoring and business reports | lifecycle evidence and one terminal CallResult |
Choose a reviewed preset rather than assembling provider clients. Exact artifact versions, digests, live-smoke scope, custom-domain publication steps, and known boundaries remain in Release status.
For a large consumer, see the scoped Loyalty v4.2 example.