Connect Kallix to Sendbird.
A phone call when the app isn't enough.

A phone call as the fallback

When a user doesn't respond in the app, your backend asks Kallix to call their phone number through the REST API.

Callbacks requested in chat

A user asks for a call in a Sendbird channel, your backend picks up Sendbird's webhook and starts a Kallix call.

Outcomes back in the conversation

Kallix's signed webhook gives your backend the outcome and captured fields, ready to post into the user's channel through Sendbird's Platform API.

Built by your developers

There's no Sendbird setting in the Kallix dashboard. It's a few API requests in your own backend, in each direction.

• Customer supportUsers who ask for a call in your app's support chat get one, and the result lands back in the thread.Use case
• KYC verificationWhen a user stalls during in-app onboarding, a call explains the next step and records where they got stuck.Use case
• Delivery updatesIf a buyer doesn't reply to in-app delivery messages, call them to agree a slot and post it to the order chat.Use case

1. 1

   Pick the moments

   Decide which in-app events should lead to a phone call, such as a callback request or a message left unanswered.

2. 2

   Listen to Sendbird

   Turn on Sendbird's webhooks for those events and handle them in your backend.

3. 3

   Start the call

   Your backend calls the Kallix REST API with the agent, the user's phone number and variables such as name and order ID.

4. 4

   Post the result

   Handle Kallix's signed webhook for the analysed call and send the outcome to the user's channel with Sendbird's Platform API.

Building something custom? Read about webhooks and the REST API.

• WeWebhooks