Yes. Krokul CRM integrates with Dialpad. Each Dialpad call is logged on the contact and the open deal with its duration, recording and AI recap, a missed call or voicemail opens a call-back task, and SMS conversations appear in the Krokul inbox with replies sent back through Dialpad. A click on a phone number in Krokul rings the Dialpad app of the manager. The link runs through the Krokul app in Zapier, Make or Albato, or through the Krokul API and webhooks.
Automation platformsZapierMakeAlbato
Dialpad posts a call event with the state hangup when a conversation ends. Krokul finds the external party by phone and writes a call record with direction, Dialpad user and duration on the contact and its open deal. Later states of the same call add to that record. recording brings the player link, and recap_summary brings the Dialpad Ai summary. Nobody retypes the call notes.
The states missed and voicemail_uploaded mean a customer did not get through. Krokul creates a task for the owner of that contact, due the same day, with the voicemail link attached. Calls from unknown numbers go to the person you pick in the settings.
An inbound Dialpad SMS event becomes a message in the Krokul inbox thread of that contact. A reply typed in Krokul goes out through the Dialpad SMS send endpoint from the number of the user. The client company feed shows both sides of the thread.
A manager clicks a number on the contact card, and Krokul asks Dialpad to initiate the call in the web or desktop app of that user. A Contact created in Krokul appears in Dialpad, and Dialpad contact events update Krokul, so agents see names on incoming calls.
| Dialpad | Direction | Krokul | When |
|---|---|---|---|
Call event (hangup, recording) | Dialpad → Krokul | Call record with player on the contact and the open deal | The call ends; the recording is ready |
Call event (call_transcription, recap_summary) | Dialpad → Krokul | Transcript and summary on the call record | Dialpad finishes processing |
Call event (missed, voicemail_uploaded) | Dialpad → Krokul | Call-back task for the contact owner | A caller does not reach anyone |
| SMS event (inbound) | Dialpad → Krokul | Message in the inbox thread | A customer texts a Dialpad number |
| SMS send | Krokul → Dialpad | Reply from the inbox thread | A manager answers in Krokul |
| Initiate call | Krokul → Dialpad | Phone number on the contact card | The manager clicks the number |
| Contact | Krokul ↔ Dialpad | Contact | A contact is created or changed on either side |
Yes. Krokul integrates with Dialpad through the Krokul app in Zapier, Make and Albato, and through its API and webhooks. Calls, recordings, recaps and SMS land on the contact and the deal.
The call event with the state hangup logs the call. Recording, transcript and recap arrive in later events of the same call, and Krokul adds them to one record.
No. Dialpad documents that its initiate call endpoint needs the web or desktop app, or a CTI app. The mobile apps and desk phones do not take the request.
Dialpad includes message content only for keys and OAuth apps with the message_content_export scope. Grant that scope, and the text arrives with the event.
Dialpad remains the phone system. Numbers, routing, call centers and Dialpad Ai live there. SMS text reaches Krokul only when the Dialpad key or OAuth app holds the message_content_export scope, because Dialpad leaves message content out by default.
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.
Dialpad is a trademark of Dialpad, Inc. Krokul is not affiliated with Dialpad.