Skip to content
MotherBot
Integrations

CallBix Integration

Bring the calls your sales team makes on their own phones into MotherBot, and put calls on their phones from chats and automations.

Note

CallBix is a separate product with its own per-user subscription, billed by CallBix. Calls are made on your team’s own SIM plans, so call charges are your mobile operator’s. Automatic call logging needs the CallBix Android app. In MotherBot, CallBix is included from the Growth plan.

What it does

  • Calls on the contact. Every incoming, outgoing and missed call the CallBix app logs is matched to the MotherBot contact with that number, with its outcome, notes, follow-up date, talk time and agent.
  • Callers become contacts. A call from a number you don’t have yet creates a contact with the source CallBix phone call (you can switch this off).
  • Ask someone to call. From Live Chat (web and mobile app), a chatbot or a workflow, put a Call now notification on an agent’s phone. They call on their own SIM, and the call comes back logged.
  • Automations on calls. Workflows can start when a call is logged, a call is missed, an outcome is saved, a recording is ready, or a follow-up is set.
  • Call lists and team alerts. Add customers to CallBix call lists for the power dialer, or send a push alert with a Call button to the team’s phones.

Connect CallBix

1

Create an API key in CallBix

In CallBix, open Automations & API and create a key. It starts with cb_live_.
2

Paste it into MotherBot

Go to Integrations → Calling → CallBix and paste the key. MotherBot checks it with CallBix before saving it, and stores it encrypted. Only the account owner can connect or disconnect CallBix.
3

Choose who gets call requests

In the CallBix card, pick a default person or team. A team means the next person in turn. Leave it on CallBix’s own routing to use what you set up in CallBix.

How calls reach MotherBot

There are two ways. Both can run at once, and a call that arrives both ways is still one call.

WaySpeedSet up in CallBixNeeds
Automatic fetchEvery 5 minutesNothingCallBix's call-log export (Growth plan and above in CallBix)
WebhookAbout 2 minutes after the callIntegrations → Webhook: paste the URL and signing secret from the CallBix card, and pick call.created, call.updated and recording.addedCallBix webhooks (Growth plan and above in CallBix). CallBix allows one webhook per workspace

Tip

Press Send test event in CallBix after adding the webhook. The CallBix card in MotherBot then shows when the last webhook arrived. Every webhook is checked against the signing secret, and anything older than five minutes is refused.

When you first connect, calls from the past 7 days are brought in so your contacts’ history isn’t empty. Those older calls never start automations — only calls made after you connect do.

Live Chat

Open a conversation and choose the CallBix tab (shortcut x b):

  • Ask someone to call: pick a person, a team, “Me”, or your default, add a note, and optionally add the customer to a call list.
  • Waiting to be called: requests nobody has called yet, with a Withdraw button.
  • Phone calls with your team: totals, each call's outcome, notes and agent, and the recording player where your CallBix plan keeps recordings.
  • Add to a call list in one tap.

The mobile app has the same tab under Actions. Recordings play on the web.

Chatbot blocks

BlockWhat it doesBranches
CallBix: Request a CallPuts a Call now notification on an agent's phone for this customer. Stores the agent's name.✓ sent · ✗ failed
CallBix: Add to Call ListAdds the customer to a CallBix call list.✓ on the list · ✗ failed
CallBix: Last CallReads the latest call with this customer: outcome, notes, time, agent, number of calls.✓ called before · ✗ never called
CallBix: Notify TeamSends a push alert to people's CallBix phones, optionally with a Call button.✓ sent · ✗ failed

When a block fails, {{callbix_error}} holds the reason in plain words. On Telegram, Instagram and web chat the blocks use a phone number the customer gave you — never the chat’s own id.

Workflows

Triggers (each one fires once per change, never for a repeat of the same call):

  • CallBix: Phone call logged — incoming, outgoing or missed.
  • CallBix: Customer's call missed — missed or declined. Fires only while the call is less than a day old.
  • CallBix: Call outcome saved — an agent saved or changed the outcome.
  • CallBix: Call recording ready.
  • CallBix: Follow-up scheduled.

Use {{trigger.outcome}}, {{trigger.notes}}, {{trigger.agentName}}, {{trigger.talkTime}} and {{trigger.followUpAt}} in later steps.

The CallBix step can ask an agent to call, add to a call list, notify the team’s phones, or look up the customer’s calls.

Tip

A popular first workflow: Customer’s call missed → send an approved WhatsApp template (“Sorry we missed your call — reply here or pick a time”) → wait for a reply → CallBix step: ask an agent to call.

Settings and permissions

  • Add callers who aren't contacts yet — on by default; stops at your plan's contact limit.
  • Ignore missed calls — missed and declined calls are not logged and don't start automations.
  • Fetch automatically — switch the 5-minute fetch off if you only want the webhook.
  • Team members need View integrations to see calls, and Use integrations to ask for calls or add to lists.
  • Disconnecting stops fetching and turns off the webhook URL. Calls already brought in stay on your contacts.

Previous

Shopify

Next

Google Sheets Add-on