Break down Beeline Cloud PBX call stats right in chat
Connect Beeline Cloud PBX to the AI agent: extensions, call history, recordings and forwarding rules. The agent builds call stats and pulls up the right talk.
How the agent works with Билайн Облачная АТС
The agent calls the Beeline Cloud PBX through its API at cloudpbx.beeline.ru: first it reads the list of PBX extensions, then the call log, call recordings, forwarding rules and the extensions' number lists. From that it counts how many calls were answered and how many were missed, and breaks the result down by extension, across the users the connected API account opens up.
The agent pages through the call log of the whole PBX for the period you need, so the report is built from completed calls rather than from a live counter, and calls from a particular number are found in the same log. Call recordings are separate files: the agent finds the one you need by number and date, downloads it from the PBX and retells what was agreed with the client.
On the write side the agent does exactly what the PBX allows: start a two-way call from a named extension, turn on permanent call recording for a user, change forwarding on busy or to a mobile, add a nuisance number to the blacklist. By default it works read-only and builds reports, and before changing a setting it names the extension and the rule and waits for confirmation.
Access boundaries are set by the API account: the agent sees the extensions and the calls of the PBX it belongs to and never looks into other numbers. Long periods are paged through, and it holds the request rate so the PBX limits are not hit. Recordings are downloaded one at a time and only for a specific question, and when there is no data for the period it says so in words instead of showing an empty table.
Integration scenarios
Call stats for any period
The agent pulls the PBX call log for the period you need and shows how many calls were answered, how many were missed and by which extensions.
Call recordings
The agent finds the recording of the call you need by number and date, downloads the file from the PBX and retells what was agreed with the client.
Forwarding and blacklists
The agent sets up forwarding on busy or to a mobile and adds a nuisance number to the blacklist without opening the PBX console.
Outgoing call from an extension
The agent starts a two-way call from the extension you name and, if needed, turns on permanent call recording for that user.
Map of your extensions
The agent pulls the list of PBX extensions, matches internal numbers with names and shows who has recording switched on and where forwarding sends calls.
Morning missed-call digest
Every morning the agent takes the call log for the past day, picks out the missed calls and sends over the list of numbers broken down by extension.
Билайн Облачная АТС examples
Нашёл: вчера в 15:42, 8 минут 20 секунд, абонент 214.
Скачал запись из АТС и прослушал: договорились на отгрузку в четверг и скидку 7% при предоплате. Клиент просил счёт до конца недели.
Разговор с Кузнецовым
Document · DOCXHow to connect
Before you connect
- A Beeline Cloud PBX contract with console access
- Budget of 500 RUB a month incl. VAT for the API add-on
- 1
Sign in at cloudpbx.beeline.ru
The account is at cloudpbx.beeline.ru; sign in with the credentials from the Cloud PBX contract. Everything else happens under «Настройки» (Settings).
- 2
On the API tab turn on Интеграция по API
«Настройки» → the “API” tab → the «Интеграция по API» switch. The add-on is paid, 500 ₽ a month incl. VAT; while it is off, nothing reaches the PBX.
- 3
Collect the credentials on “API”
On “Version 2.0” press «Создать новый токен»: that is the Portal API token. “Version 1.0” hands out a «логин» + «пароль» pair instead; without a token, it works too.
FAQ
With an API token. In the cloudpbx.beeline.ru console open Settings and the API tab, enable the API integration service and press “Create new token” on the Version 2.0 tab; that token goes into the Portal API token field. The login and password pair for external systems is only issued on the Version 1.0 tab: without a token, it works too. The console's own login and password will not work.
PBX extensions, the call log, call recordings, forwarding rules and the extensions' number lists, as far as the connected API account allows.
It can: start a call from an extension, turn on call recording, change forwarding and extend the blacklist. By default it works read-only and builds reports.
Yes. API integration is enabled separately on the API tab and is billed as a paid service: while the toggle is off, requests to the PBX will not go through.