Appearance
Connect Calls Ringostat
Connect your Ringostat telephony so real phone calls — inbound and outbound — land in the same client chats as your text channels. Each answered call is recorded, transcribed, and speaker-labeled (manager vs. client) right inside the conversation, and your managers can place outbound calls straight from the chat with one click.
Use this channel when your business already runs on Ringostat as its phone system and you want human calls, recordings, and searchable transcripts to sit alongside everything else in MyChatBot. This is a human-telephony connector — real people talk on the phone; there's no AI answering the call. (For an AI voice assistant that talks to callers, use the separate Calls channel instead.)
At a glance
| You need | Where | Result |
|---|---|---|
| Your Ringostat Auth Key, Project ID, and SIP Number | From your Ringostat account | Credentials ready to paste |
| An assistant to connect | Channels → your assistant → Calls Ringostat | Assistant selected for the channel |
| The channel connected | Connect button on the setup form | "Connection Details" appear |
| Two MyChatBot webhooks (incoming + outgoing) added in Ringostat | Your Ringostat dashboard (not in MyChatBot) | Ringostat sends call events to us |
| The bot switched on | Connect agent to this channel toggle | Calls start flowing into chats |
Connect in 5 steps:
- Open Channels and select your assistant.
- Open the Calls Ringostat channel.
- Enter your Auth Key, Project ID, and SIP Number, then click Connect.
- In your own Ringostat dashboard, register two MyChatBot webhooks, one for incoming and one for outgoing calls.
- Turn on Connect agent to this channel to start ingesting calls.
In the app
Everything on this page lives under Channels → your assistant → Calls Ringostat. App URL: https://app.mychatbot.app/channels
Before you start
You'll need three values from your Ringostat account:
| Field | What it is |
|---|---|
| Auth Key | Your Ringostat API authorization key |
| Project ID | The identifier of your Ringostat project |
| SIP Number | The manager's Ringostat phone number (SIP account), in international format (e.g. +380...) |
The SIP Number is the number your calls run through — it's the line your managers use to make and receive calls in Ringostat.
Connect the channel

- Go to Channels and select the assistant you want to connect.
- Open the Calls Ringostat channel. You'll see the Connect Ringostat form.
- Fill in all three fields:
- Auth Key
- Project ID
- SIP Number — enter it in international format (the field defaults to a
+380prefix).
- Click Connect.
On success you'll see a Ringostat Channel Connected confirmation, and the form is replaced by a Connection Details panel showing your SIP Number, Auth Key (hidden by default — use the eye icon to reveal it), and Project ID.
Fill in every field
If any of the three fields is empty, you'll see "Please fill in all the fields." All three are required to connect.
Already connected?
If you see "This Ringostat channel is already connected to the system," that SIP number is already connected elsewhere in MyChatBot. Connecting the same SIP number again on the same assistant doesn't create a second channel — it keeps the existing one.
Register the webhooks in Ringostat
This is the step that's easy to miss — and calls won't appear without it.
MyChatBot doesn't register anything on Ringostat's side for you. You need to open your own Ringostat dashboard and add the MyChatBot webhook there, so Ringostat sends each completed call to us. The URL is the same for every account:
https://api.mychatbot.app/webhook/ringostatThe webhook is set up on Ringostat's side
Connecting the channel in MyChatBot does not register the webhook. Until you add the MyChatBot webhook in your Ringostat dashboard, no calls will flow in.
Create two webhooks: incoming and outgoing
Ringostat reports incoming and outgoing calls as separate events, so you need two webhooks pointing at the same URL. With only the first one, outgoing calls never reach MyChatBot.
In Ringostat, open the project's integrations with external systems (Налаштування інтеграції з зовнішніми системами) and add a new notification for each row below:
| Setting | Webhook 1: incoming calls | Webhook 2: outgoing calls |
|---|---|---|
| Назва (Name) | Any name, e.g. MyChatBot incoming | Any name, e.g. MyChatBot outgoing |
| Подія (Event) | Після дзвінка (After call) | Після вихідного дзвінка (After outgoing call) |
| HTTP метод (HTTP method) | POST | POST |
| Напрямок (URL) | https://api.mychatbot.app/webhook/ringostat | https://api.mychatbot.app/webhook/ringostat |
type in the request body | in | out |
Leave the other events (before the call, on pickup, on forwarding) alone. MyChatBot only uses the after-call events.
Fill in the request body
Both webhooks use the same request body (Тіло запиту). Only the type value differs. Add one parameter per row with + Додати параметр (Add parameter):
- Ключ (Key): type the key exactly as written below, in lowercase Latin letters.
- Значення (Value): either type a fixed value as Текст (Text), or pick the Ringostat variable that holds that piece of call data.
| Key | Value | Required |
|---|---|---|
project_id | Type your Project ID as text. It must be exactly the Project ID you entered when connecting the channel in MyChatBot. | Yes |
type | Type in as text in the incoming webhook and out in the outgoing one. | Yes |
number_call | The variable with the caller's number (the number that placed the call). | Yes |
sip_number | The variable with the dialled number (the number that received the call). | Yes |
call_status | The variable with the call status (Ringostat's disposition, such as ANSWERED, PROPER, NO ANSWER or BUSY). | Yes |
call_id | The variable with the call's unique ID. | Recommended |
recording_wav | The variable with the link to the call recording. | For recordings and transcripts |
conversation_time | The variable with the talk time, in seconds. | For recordings and transcripts |
call_duration | The variable with the total call duration, in seconds. | Recommended |
call_waiting | The variable with the waiting (ringing) time, in seconds. Used to trim the ringtone from the start of the recording. | Recommended |
calldate | The variable with the call's date and time. | Optional |
Keep number_call and sip_number mapped to the same two variables in both webhooks: caller in number_call, dialled number in sip_number. MyChatBot uses type to tell which one is the client. On an incoming call the caller is the client. On an outgoing call (type = out) the dialled number is the client. Both values must be phone numbers, not SIP logins. A call where either one isn't a phone number is skipped.
Keys and values must match exactly
MyChatBot finds your channel by project_id and decides what to do with a call by call_status and type. Ringostat gets no error back, so check these carefully:
- If
project_idis missing or differs from the Project ID in MyChatBot, every call is skipped. - Only calls whose
call_statusisANSWEREDorPROPERare logged, plus missed incoming calls. Mapcall_statusto Ringostat's status variable. Never type a fixed value. - Any
typeother thanoutis treated as an incoming call. If the outgoing webhook doesn't sendout, outgoing calls land in a chat under your own line's number instead of the client's.
Without recording_wav and conversation_time, an answered call still opens the client's chat, but no recording or transcript is added. Without calldate, the call time is estimated from when Ringostat sent the event.
Check it works
Once both webhooks are saved, make one test call in each direction and keep talking for a few seconds, then hang up. Within a couple of minutes, both calls should appear in the client's chat with a recording card. If one direction is missing, re-check that direction's webhook.
Turn it on
The channel is created switched off. While it's off, incoming calls are silently ignored.
- Turn on Connect agent to this channel at the top of the channel page to go live.
- Turn it off to pause the channel without disconnecting — calls stop flowing in while it's off.
- Use Revoke Channel to remove the connection entirely.
Off means calls are dropped
While the channel is off, Ringostat call events are ignored — no chat, no recording, no transcript. Switch on Connect agent to this channel before you expect calls to appear.
What happens on a call
Once connected and switched on, here's what you get for each call:
- A chat thread per client. All calls to and from the same client phone number group into one conversation, alongside that client's other channels. Inbound and outbound calls land in the same thread.
- The recording, playable in chat. Answered calls show a recording card with an audio player you can scrub and replay.
- A transcript, speaker-labeled. The recording is transcribed and split into turns labeled manager and client, so you can read the call without listening to it.
A few things to know about what gets ingested:
- Only answered calls with real conversation are transcribed. A missed incoming call still shows in the client's chat, marked "This call was not answered", so your team can see who to call back. It doesn't change the client's funnel status, so it doesn't start a follow-up. Unanswered outgoing calls aren't logged, and an answered call with no talk time opens the client's chat but adds no call card.
- Speaker labels are a best guess. The manager/client split is inferred from the recording and call direction, so it can occasionally be off on ambiguous calls. When the AI role split fails and the labels fall back to a guess from who spoke first, the transcript still shows the turns, but AI conversation analytics does not grade the manager on that call or report per-role talk time.
- No typing back into a call thread. Because a phone call isn't a text conversation, the message input is hidden in Ringostat chats — you reply by calling back.
Outbound click-to-call
You can place outbound calls to a client without leaving the chat.
- Open the client's chat (any Ringostat conversation, or a chat where you have the client's phone number).
- Click Start Call.
- Ringostat rings your manager's SIP number first, then dials the client.
The call itself connects immediately, but the recording and transcript only appear after the call ends and Ringostat sends us the completed-call event. Give it a moment after hanging up for the recording card to show up.
You can also use Calls Ringostat as a follow-up/outreach channel in Automations — for example, to auto-dial a lead who filled out a form. The lead must have a phone number for the call to go out.
How billing works
Ringostat calls are billed simply: one "Call" message per transcript, and nothing else on the MyChatBot side.
- Each call that produces a speaker-labeled transcript costs one message, deducted from your plan's message balance.
- There's no per-minute or per-call-duration charge. A call is at most one billed message, regardless of how long it lasted.
- Calls with no transcript — missed, voicemail, or no talk time — cost nothing on MyChatBot.
Two separate bills
Your Ringostat telephony minutes are billed by Ringostat directly, outside MyChatBot. MyChatBot only charges the single "Call" message when a transcript is produced.
Managing the connection
| Action | Where |
|---|---|
| View or reveal your credentials | The Connection Details panel (eye icon reveals the Auth Key) |
| Pause the channel | Turn off Connect agent to this channel |
| Disconnect entirely | Revoke Channel |
Troubleshooting
Calls aren't appearing in chats.
- Confirm Connect agent to this channel is turned on — the channel starts off, and calls are dropped while it's off.
- Confirm you've registered the MyChatBot webhook in your Ringostat dashboard. Without it, Ringostat never sends us the calls.
- Check that the webhook's
project_idis exactly the Project ID shown in Connection Details. - Remember that only answered calls with real talk time produce a transcript. A missed incoming call shows as "This call was not answered", with no recording; an unanswered outgoing call isn't logged at all.
Incoming calls appear, outgoing calls don't.
Outgoing calls need their own webhook on the Після вихідного дзвінка (After outgoing call) event, with type set to out. The Після дзвінка (After call) webhook doesn't cover them. See Create two webhooks.
Calls appear under the wrong phone number.
number_call and sip_number are swapped, or type doesn't match the event. Map the caller to number_call and the dialled number to sip_number in both webhooks, with type set to in on the incoming one and out on the outgoing one.
Still stuck?
- Check the MyChatBot documentation for updated information.
- Contact our support team at support@mychatbot.app.
- Include your Project ID, SIP Number, and a rough time of a test call for faster resolution.
