Yes. Krokul CRM integrates with the Binotel virtual PBX. A completed call lands on the contact card and the open deal with its duration and recording, and a missed call becomes a «Call back» task. During an incoming call, Binotel shows the manager the client name and a link to the client card in Krokul.
Automation platformsAlbato
On an incoming call, Binotel sends an API CALL SETTINGS request with the client number. Krokul finds the contact by phone and returns the name, the responsible manager and a link to the card. The manager sees who is calling before picking up.
After every completed call, Binotel sends an API CALL COMPLETED message. Krokul records the call in the contact feed with its direction, duration and result. The recording opens in a player right in the feed. A number that is not in the database gets a new contact and a deal named «Call» with the number.
When a client hangs up before anyone answers, Krokul creates a «Call back» task with the number and time of the call. The task goes to the manager of that client, or to the person on duty for a new number. Once the manager has called back and talked, the task can be closed from the card.
The manager clicks a number on the contact card, and Krokul sends Binotel a request for a call from an internal number to an external one. First the manager phone rings, then Binotel dials the client. Once finished, the conversation comes back to the deal through the same completion message.
A new Krokul contact appears in the Binotel clients section with the same number and responsible manager. This lets the PBX route a regular client call to that client manager.
| Binotel | Direction | Krokul | When |
|---|---|---|---|
| API CALL SETTINGS request (client number, call type) | Binotel ↔ Krokul | Contact name, responsible manager, link to the card | At the moment of an incoming call |
| API CALL COMPLETED message | Binotel → Krokul | Call in the contact feed and the deal feed | After every completed call |
| Call recording (stats/call-record) | Binotel → Krokul | Player in the call record | When the manager opens the call |
| Missed call | Binotel → Krokul | «Call back» task | A call with no answer |
| Unknown number | Binotel → Krokul | New contact and deal | The first call from a client |
| Request for a call from an internal number to an external one | Krokul → Binotel | Number button on the contact card | The manager clicks the number |
| Client (CUSTOMERS) | Krokul → Binotel | Contact and responsible manager | A contact is created in Krokul |
contact/api-find, record the call with activity/api-create, and add task/api-create for a missed one.contact.created, check x-crm-signature and pass the new client to Binotel through its REST API.Yes. Binotel calls reach the Krokul contact and deal cards with their recordings, and missed calls become tasks. You connect them through the Krokul app in Albato or through the API with Krokul webhooks.
The client name, the responsible manager and a link to the card in Krokul. Krokul returns this data to the API CALL SETTINGS request when the number is already in the database.
By phone number. If a contact with that number exists, the call lands in that contact feed and the open deal. For a new number, Krokul creates a contact and a deal.
In Binotel. Krokul keeps a link to the recording on the call and opens it in a player, without a copy of the audio in its own database.
Numbers, extensions, queues and routing rules are set up in the Binotel account. Call recordings stay in Binotel, and Krokul opens them from a link on the call.
Tell us which service you use and what should move between it and Krokul. We reply with the way to do it and when it will be ready.
Request received. We reply to your email.
Binotel is a trademark of its owner. Krokul is not affiliated with Binotel.
