Integrations & Sync
Telephony SDK & SIP
How Sarj connects to your existing phone lines and call centre, and how you decide which calls it answers.
You do not need to replace your call centre to use Sarj. It connects to the telephony you already run, takes the calls you route to it, and passes calls back to your agents when a person is needed.
Two ways to connect
Telephony SDK
Sarj's low-latency telephony SDK connects it to existing call-centre platforms, keeping the audio path short so conversations stay natural.
Standard SIP
Sarj can also connect over standard SIP, which most enterprise phone systems and carriers support.
Your Sarj deployment team works with your telephony team or provider to choose the right option and set it up.
Deciding which calls reach Sarj
Start with a share
Route one line, one menu option, or a share of calls to Sarj while your current setup handles the rest. Widen it as results hold.
Route by need
Send the calls Sarj handles best, such as status checks or bookings, and keep sensitive queues with your team from the start.
Outbound
For outbound use cases such as lead follow-up or payment reminders, Sarj places calls on numbers you provide and approve.
Latency
Sarj's recognition, reasoning and speech run on one streaming pipeline with sub-120ms conversational latency. Network paths matter too: hosting in the Kingdom keeps the audio close to your callers. See Data Residency & Hosting.
Transferring to your agents
When a call needs a person, Sarj transfers it into your existing queues with the transcript and collected details attached. See Agent Handoff Rules.