# Binotel + Krokul CRM

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.

**Status:** Via API and webhooks. **Automation platforms:** Albato.

## What your team gets

### The caller is known before you answer

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.

### The conversation goes into the client history

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.

### A missed call does not get lost

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.

### One click on the card starts a call

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.

### The same clients in both systems

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.

## What moves between Binotel and Krokul

| Binotel | Krokul | Direction | When |
|---|---|---|---|
| API CALL SETTINGS request (client number, call type) | Contact name, responsible manager, link to the card | Binotel ↔ Krokul | At the moment of an incoming call |
| API CALL COMPLETED message | Call in the contact feed and the deal feed | Binotel → Krokul | After every completed call |
| Call recording (stats/call-record) | Player in the call record | Binotel → Krokul | When the manager opens the call |
| Missed call | «Call back» task | Binotel → Krokul | A call with no answer |
| Unknown number | New contact and deal | Binotel → Krokul | The first call from a client |
| Request for a call from an internal number to an external one | Number button on the contact card | Krokul → Binotel | The manager clicks the number |
| Client (CUSTOMERS) | Contact and responsible manager | Krokul → Binotel | A contact is created in Krokul |

## How to connect today

### Krokul app in Albato

1. Connect the Krokul app in Albato with a Krokul API key, and Binotel with a key from the PBX account.
2. Link the Binotel trigger Call is completed to the Krokul action «Add Activity» on the contact found by phone.
3. Link the Krokul trigger «New Contact» to the Binotel action New client, so the client appears in the PBX.
4. For a call from the card, use the Binotel action Internal to external number call request.

### Your own flow through the Krokul API and webhooks

1. Issue a Krokul API key with scopes for contacts, deals, activities and tasks.
2. Ask Binotel support to set the URL of your handler for API CALL COMPLETED and API CALL SETTINGS.
3. On a completed call, find the client by number with `contact/api-find`, record the call with `activity/api-create`, and add `task/api-create` for a missed one.
4. Subscribe a Krokul webhook to `contact.created`, check `x-crm-signature` and pass the new client to Binotel through its REST API.

**Triggers:** Incoming call; Call is completed.

**Actions:** New client; Internal to external number call request; External to internal number call request.

### For integrators

Binotel has three mechanisms for a CRM. API CALL SETTINGS asks your system about the client during a call, API CALL COMPLETED reports every completed call, and the REST API returns recordings and clients. On the Krokul side, `contact/api-find` looks a person up by phone, the Binotel call ID is stored as an `externalRef` and filters out repeats, and webhooks are signed with HMAC and have a delivery log.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul work with Binotel?

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.

### What does a manager see during an incoming Binotel call?

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.

### How does Krokul match a call to a client?

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.

### Where are Binotel call recordings stored?

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.

## Limits

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.

## Related services

- [Ringostat](https://krokul.com/en/integrations/ringostat/index.md)
- [RingCentral](https://krokul.com/en/integrations/ringcentral/index.md)
- [Aircall](https://krokul.com/en/integrations/aircall/index.md)
- [Twilio](https://krokul.com/en/integrations/twilio/index.md)
- [Telegram](https://krokul.com/en/integrations/telegram/index.md)

[Phone and calls](https://krokul.com/en/integrations/category/telephony/index.md)

Binotel is a trademark of its owner. Krokul is not affiliated with Binotel.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs