Skip to content

UniTalk (manager calls) ​

UniTalk is a telephony connector that brings a human sales manager's phone calls — plus each call's recording and transcript — into the matching client's MyChatBot chat, so the whole conversation history lives in one place. It works like the Ringostat call connector: a person (not an AI voice assistant) makes and takes the calls on their UniTalk line, and MyChatBot logs the result.

In the app

Channels → select your assistant → Calls UniTalk. App URL: https://app.mychatbot.app/channels

At a glance ​

ItemStatus
What it isA human-manager phone connector: calls + recordings + transcripts flow into the client chat
Who talksA real manager on their UniTalk line — not an AI voice assistant
How you connect itSelf-serve: Channels → your assistant → Calls UniTalk → Connect UniTalk
What you needYour UniTalk API Key, a SIP Line, and your Virtual Number

What it does ​

Once connected, UniTalk:

  • Log inbound calls (a client rings your manager) into that client's chat, with the call recording and an auto-transcript attached.
  • Log missed inbound calls too: the client's chat shows "This call was not answered", so your team can see who to call back. A missed call doesn't change the client's funnel status or who their manager is, so it doesn't start a follow-up. Unanswered outgoing calls aren't logged.
  • Support outbound click-to-call: a manager can dial a client — the call rings the manager's line first, then connects to the client.
  • Keep call history alongside your other channels, so analytics and follow-up see calls the same way they see chats.

The manager talks on their own UniTalk phone or softphone — calling doesn't happen inside the MyChatBot browser tab.

When to use it ​

Choose UniTalk when a human team handles customer phone calls through the UniTalk cloud phone system and you want those calls captured in MyChatBot. If you already use Ringostat for the same thing, UniTalk is the equivalent option for UniTalk lines.

If instead you want an AI to answer or make calls automatically, that's a different feature — use the AI voice Calls channel, not UniTalk.

Connect it ​

  1. Have your UniTalk cloud phone account ready: your UniTalk personal-account API key, a manager's SIP line, and your virtual number.
  2. In MyChatBot, open Channels, select the assistant whose chats should receive the calls, and open Calls UniTalk.
  3. Under Connect UniTalk, fill in API Key, SIP Line, and Virtual Number (international format, e.g. +380…) — all three are required — and click Connect.
  4. In your UniTalk dashboard, set the call webhook to https://api.mychatbot.app/webhook/unitalk so completed calls are sent to MyChatBot. This step is done by hand — MyChatBot doesn't configure it for you.
  5. The channel starts off. Turn on Connect agent to this channel when you're ready to go live.

To disconnect, use Revoke Channel in Connection Details.

SIP lines and managers ​

After connecting, Connection Details shows a SIP lines roster fetched from UniTalk (SIP line, operator, and phone number where UniTalk returns it):

  • Refresh lines reloads the roster from UniTalk; Sync all lines adds a channel for every line not yet connected.
  • Pick the Default SIP line used when a manager has no line of their own.
  • Under Manager sync, assign each operator line to a team member — or choose Create new operator — then click Sync managers. Inbound calls on a line are attributed to its assigned manager, and outbound calls use the manager's line when bound. A newly created operator gets a placeholder login until an admin sets a real email in Team settings.

TIP

Telephony minutes are billed by UniTalk directly, on your UniTalk account. MyChatBot only downloads and stores the finished recording and transcript — it doesn't carry the call audio itself.

A few limits to know

  • A click-to-call started from an existing chat may be logged as its own call entry rather than merged back into that same thread.
  • Calls are matched to a client by phone number, so shared or forwarded numbers can group calls in unexpected ways — the same caveat that applies to any phone-based channel.

See also ​