Pulse
Connect your Pulse account to Voice Agents for inbound and outbound voice calling.
Setup has two parts: add your Pulse token on Voice Agents, then map your Pulse number’s WebSocket URL for inbound routing.
Before you start: an active Pulse account, your non-expiring bearer token, at least one CLI number (the caller-line-identity phone number Pulse assigns you), and Voice Agents access with permission to add telephony connections (Deploy → Phone Numbers).
Watch the setup
Add the connection on Voice Agents
Voice Agents needs one value — a non-expiring bearer token provided by Pulse.
Set up inbound routing
For inbound calls to reach Sarvam, map the WebSocket URL to your Pulse number using the Pulse API.
Run the following API call, replacing <token> with your Pulse bearer token and <clinumber> with your CLI number from Pulse:
A 2xx response means the mapping succeeded. A 401 means the bearer token is wrong or expired; a 4xx on clinumbername usually means the CLI number is incorrect. Fix the value and re-run.
After connecting
Once both sides are configured:
Add your phone number
In Voice Agents, open your Pulse connection under Deploy → Phone Numbers and add the CLI number. See Manage Phone Numbers.
Route calls to an agent
For incoming calls, create an Inbound deployment to route the number to an agent. To dial out, add the number to a Campaign.
Verify with a test call
Dial the number from a phone and confirm your agent answers. See Manage Phone Numbers for the test-call steps.
Outbound calling uses this same connection — dial out by adding the number to a Campaign. No separate credentials are required.