Your providers, your usage
VaaniTalk uses the model-provider accounts you connect. API usage and provider charges stay directly between you and those providers; model credits are not bundled with VaaniTalk platform access.
Tools & actions
Connect conversations to real operations.
Add API actions, transfers and end-call behavior so your agent can complete work safely beyond the conversation.
Before you begin
Have provider credentials, a clear agent goal and a test scenario ready. Add telephony credentials only when you need phone calls.
Three-step quickstart
From provider key to a launchable agent.
Keep the first version focused: one outcome, one provider pipeline and a small set of realistic test conversations.
- 01
Connect your providers
Open Model Configurations and add the API credentials for the language, speech-to-text and text-to-speech providers you want to use.
Open provider setup - 02
Create your agent
Start a workflow, define the opening prompt and conversation goal, then add branches, tools and hand-off rules for real customer scenarios.
Create an agent - 03
Test, review, publish
Run a browser test, inspect the transcript and transitions, then connect the channel you want to launch—phone or an embedded web experience.
Follow the launch checklist
Explore the platform
Guides for every launch stage
Provider setup
Choose compatible language and speech services, add credentials and validate the pipeline.
Agent design
Turn a business outcome into prompts, conversation paths, context variables and safeguards.
Testing & launch
Test realistic paths, review run evidence and prepare a controlled production release.
Voice channels
Connect telephony or an embedded web agent and understand the channel-specific setup.
Tools & integrations
Call business APIs, transfer conversations and connect your agent to real operations.
Security & privacy
Plan access, data handling, recording consent and the controls needed for your use case.
Launch check
Ready means tested, traceable and intentional.
Voice agents interact with real people and real systems. Review the full path before connecting production traffic.
- Provider accounts have active billing or quota
- Prompts cover success, fallback and human hand-off paths
- A test run has been reviewed end to end
- Recording, calling and data-use consent meets your requirements
Build small. Prove it. Then scale.
Start with one workflow and a controlled audience. Use transcripts and run history to refine it before expanding channels or call volume.
Request accessCould not find the exact guide?
Send the page URL and your question—we will point you in the right direction.