Yes. Krokul CRM integrates with Ringostat. Every call from Ringostat call tracking reaches Krokul with its ad source and UTM tags, so the deal knows at once which campaign brought the client. The recording and duration of the conversation land in the contact feed, and a missed call becomes a task.
Automation platformsAlbato
The Ringostat «Incoming call» event after the call carries the client number and the utm_source, utm_medium and utm_campaign tags. Krokul creates a deal, writes the tags to it and sets the source. The Krokul report by source then shows how many paid deals each campaign brought.
When a client with an open deal calls again, Krokul creates no duplicate. The call lands in the feed of the existing deal. Krokul keeps the Ringostat REPEATED status next to it, so the marketer sees first and repeat calls separately.
The NO ANSWER or BUSY status in the after-call event creates a «Call back» task in Krokul with the client number. The task goes to the contact manager. A number with no contact goes to the person on duty.
The manager clicks a number on the card, and Krokul calls the Ringostat method that connects two numbers. In this request, caller carries the client number, callee carries the manager number or SIP account, and direction out makes the call outgoing in the Ringostat log. The conversation comes back to the deal through the «Outgoing call» event.
The «Call category set» event arrives when someone sets a category on a Ringostat call card. Krokul adds this category to the deal as a tag, and the pipeline can be filtered by it.
| Ringostat | Direction | Krokul | When |
|---|---|---|---|
| «Incoming call» event after the call (number, status, duration, recording, UTM) | Ringostat → Krokul | Deal with source and tags, call in the contact feed | After every incoming call |
| «Outgoing call» event after the call | Ringostat → Krokul | Call in the deal feed | After an outgoing call |
| NO ANSWER or BUSY status | Ringostat → Krokul | «Call back» task | A call with no conversation |
| REPEATED status | Ringostat → Krokul | Repeat call mark on the existing deal | A client calls again |
| «Call category set» event | Ringostat → Krokul | Tag on the deal | A category is set on the call card |
| Method that connects two numbers (caller, callee, direction) | Krokul → Ringostat | Number button on the deal card | The manager clicks the number |
| Call log (calls/list) | Ringostat → Krokul | Check of calls for a period | Once a day |
contact/api-find, creates a deal through card/api-create with the UTM tags and records the call through activity/api-create.Yes. The UTM tags and the source from Ringostat call tracking are written to the deal, so Krokul reports by source count calls together with sales.
The main event is «Incoming call» after the call. For the full picture, add «Outgoing call» after the call and «Call category set» if the team sets categories on calls.
Ringostat marks the webhook as «with error» and shows it on the error check page. Ringostat does not retry automatically, and Krokul picks up the missed calls from the calls/list log.
Yes. Krokul calls the Ringostat method that connects two numbers. The manager phone rings first, then the client, and the conversation comes back to the deal.
Tracking numbers, projects, the callback widget and ad channel analytics live in Ringostat. Ringostat does not retry a webhook that the receiver did not answer with 200 OK, so Krokul accepts the event at once and processes it after the reply.
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.
Ringostat is a trademark of its owner. Krokul is not affiliated with Ringostat.