Yes. Krokul CRM has a native integration with the UniTalk cloud PBX. After every conversation, UniTalk sends a CALL_END event, and Krokul records the call in the contact feed and the open deal with its direction, duration and a link to the recording. A call nobody answered becomes a «Call back» task, and a number on the contact card is dialed through the UniTalk API.
When a call ends, UniTalk sends a CALL_END event with the numbers, direction, state and talk time in seconds. Krokul looks up the contact by the client number. On an incoming call that number sits in the from field, on an outgoing call in the to field. The call lands in the contact feed and the deal feed together with its duration and recording. The player opens right there.
The NOANSWER or BUSY state means no conversation took place. Krokul creates a «Call back» task with the client number, linked to the contact and the deal. The task shows up in the manager task list, and the task.created webhook tells outside systems about it.
If the number is not in the database, Krokul creates a contact and a «Call» deal with that number in the pipeline you chose when connecting. A repeat call from the same client attaches to the deal that is already open. One client does not produce duplicate deals.
When «Request to your API» is on in a UniTalk incoming scenario, the PBX sends a ROUTE event with the client number. Krokul finds the contact and returns the extension of the contact manager and the client name for the SIP client. A regular client reaches the same manager, and if that manager is busy, UniTalk carries on with the scenario.
The manager clicks a number on the contact card, and Krokul calls the UniTalk method /calls/originateC2c with the client number and the manager extension as a forwarding step. The finished conversation comes back to the deal through the same CALL_END event.
| UniTalk | Direction | Krokul | When |
|---|---|---|---|
| CALL_END event (from, to, direction, secondsTalk, state) | UniTalk → Krokul | Call in the contact feed and the open deal | After every finished call |
| link field in CALL_END | UniTalk → Krokul | Recording player on the call | The conversation took place (ANSWER state) |
| NOANSWER, BUSY state | UniTalk → Krokul | «Call back» task with the number | A call with no answer |
| A number missing from the database | UniTalk → Krokul | New contact and «Call» deal | The first call from a client |
| ROUTE request (from, outerNumber) | UniTalk ↔ Krokul | Extension of the responsible manager and client name | At the moment of an incoming call |
| /calls/originateC2c method | Krokul → UniTalk | Number on the contact card | The manager clicks the number |
| /history/get history | UniTalk → Krokul | Calls missed during a connection outage | After the connection is back |
Yes, a native one. UniTalk calls reach the Krokul contact and deal cards with their duration and recording, missed calls become tasks, and managers call clients from the card.
Two handlers with the POST method and a JSON body, one for the CALL_NEW event and one for the CALL_END event. CALL_END records the call, and CALL_NEW stays in the integration log.
Receiving calls needs no key, the handler address is enough. A key from the API part of the integrations section is needed to call from the card and to query the call history.
By the client phone number. For an incoming call it is the number that called, for an outgoing call the number the manager dialed. If there is no contact yet, Krokul creates one.
Numbers, extensions, incoming scenarios, voice menus and queues are set up in the UniTalk account. The audio stays in UniTalk, and Krokul keeps the link from the link field, which UniTalk sends only for the ANSWER state.
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.
UniTalk is a trademark of its owner. Krokul is not affiliated with UniTalk.
