How to connect a Tata Smartflo account to zoxaAI — the two credentials you bring, the one-time setup in the Tata portal, and how outbound and inbound agent calls stream audio to your agent.

Twilio and other international carriers cannot originate domestic calls within India (DoT/TRAI regulations). Smartflo is a licensed Indian operator, so it is the right choice for calling Indian numbers. If your calls are outside India, use Twilio or another provider instead.

Voice Streaming and Webhooks must be turned on by Tata for your account before setup will work. Raise a request with your Tata account manager first. This is the main onboarding step that takes time.

Generate your Auth Token from the Tata portal, not via the login API. Portal tokens do not expire; API-generated tokens expire after 60 minutes.

The one thing that trips people up: the API Key (for outbound) can only be created after your Voice Streaming endpoint exists in Tata — and that endpoint needs a URL that zoxaAI only shows after you save the config. So you create the config with just the Auth Token first, then come back and add the key. Follow the steps in order and it's smooth.

Outbound: place a call from the agent editor — Tata dials the customer, and on answer your agent speaks. Inbound: call a routed DID — the assigned agent answers.

Outbound calls require the Click-to-Call Support API Key on the configuration. Without it, outbound attempts return a clear error. Inbound-only accounts do not need it.

Tata only transfers calls to entities registered in your Smartflo account. For 10-digit mobile destinations, zoxaAI handles this for you: on the first transfer to a new number it automatically creates a phone-only user/agent in your Smartflo account (named zoxa-transfer-<number>, web login blocked) and completes the transfer — later transfers to the same number reuse it. Extensions and department IDs must already exist in your account. If auto-registration fails, the transfer returns destination_not_registered.

Smartflo accounts have a hard agent-seat cap (for example, "Number of Agents for calling: 2/5"). zoxaAI keeps auto-registered destinations ephemeral: entries named Zoxa Transfer <number> are deleted automatically when a call ends (a destination still on a live bridged call is kept and reclaimed by a later sweep), and if a registration ever hits the seat limit, idle entries are swept and the registration retried. Users you created yourself are never touched.

With a blind transfer the caller is connected to the destination immediately after the AI plays its message. The AI bot leg drops once the transfer is initiated. If the destination is unavailable, the Tata platform handles the failure — the AI is no longer on the call.