Client lookup by number
At the moment of a call the app searches Bitrix24 for a contact, company or lead by phone number — in several formats (+7 and 8) so the match is found reliably. The call is instantly linked to the right client card.
Client name from Bitrix24 on the incoming call screen
A new capability: if the number isn't in the phone's contacts, the app finds the client in Bitrix24 and shows their name right on the full-screen incoming call screen — before you pick up. You immediately see who's calling, even if the contact exists only in the CRM. Enabled with a single toggle.
Pop-up call card
On an incoming or outgoing call, a card pops up in Bitrix24 for the responsible employee with the client's name and a link to the deal or contact. The manager doesn't have to look the client up by hand — the details are already there.
Auto-creation of a lead or deal
A call from an unknown number can automatically create a record in the CRM. The app respects the portal mode: in classic Bitrix24 a lead is created, in simple mode a deal with a contact. Nothing needs to be configured by hand.
Call logging in Bitrix24 telephony
Incoming and outgoing calls are logged in Bitrix24 telephony: direction, duration and status (answered, missed). Only the fact of the call is saved — the conversation audio is not recorded and is not sent anywhere. The call history builds up right in the client card, next to the deal or contact.
Flexible call scenarios
For each call type — incoming or outgoing, from a known or unknown number — you choose the action yourself: do nothing, just log the call or create a record in the CRM. No extra records pile up, and the ones you need aren't lost.
Tasks for calls
After a call the app can create a task in Bitrix24 itself — for example, to call back a missed call. Configured by scenario and outcome (answered or missed), with a due date, an observer and a title and text template. The task is linked to the found client.
No server of your own
The integration works through a Bitrix24 inbound webhook — the app talks to the portal directly. No intermediate server is needed, and the webhook secret is stored on the device in encrypted form. There's also an exclusion list: no records or tasks are created for service numbers.