Wani quick start

The order to set Wani up in: a carrier to dial through, a voice engine key, and the consent rules that gate recording. Each step links to its own guide rather than repeating it here.

Takes about 5 minutes to read, longer to complete each linked step.

1. 1 1. Connect a carrier

   Wani needs a telephony carrier to actually rent a number and carry call audio. Today that carrier is Vobiz -- it is the only one Wani's own telephony registry recognizes as active. Several other providers (Exotel, Smartflo, Pulse, InTalk, Twilio) can have a credential stored ahead of time, but none of them can carry a Wani call yet.

2. 2 2. Add a voice engine key (optional)

   A shared Deepgram key already lets every tier, including Free, place a call -- Deepgram is the only engine whose voice can speak on a live call, so it ships on every tier by default. Bringing your own Deepgram, ElevenLabs, or Sarvam key moves usage onto your own account instead of the deployment's shared one; Sarvam also unlocks the paid tiers' Indian-language voices.

3. 3 3. Know the recording and consent rules before you turn recording on

   If you plan to record calls for QA or compliance, Wani enforces a hard rule before any recording is written: a valid, non-expired consent reference must already exist, checked at the database layer rather than trusted to application logic. The three consent bases, their expiry windows, and what recording does not do yet (no automatic transcription) are covered in their own guide.

4. 4 What this quick start does not cover

   This page is an index, not a substitute for the guides it links to. It also does not state a latency figure for how quickly Wani responds on a call -- that number has not been measured on this deployment, and no page states one until it has.

Status: reviewed · reviewed by claude-sonnet-5