Calls by CRM entity
The Calls by CRM entity robot gathers telephony statistics for a lead, deal, contact, or company: the number of calls, total duration in seconds, the date, duration, and ID of the last call, plus a recording-exists flag (Y/N). A period start date can be set. It is used in Bitrix24 (Alaio) business processes to assess activity on a deal or client.
The robot queries Bitrix24 (Alaio) telephony statistics for a specific CRM entity and returns aggregated call metrics right into the business process. It takes the entity type (lead, deal, contact, company), its ID, and an optional period start date (ISO 8601) as input. It outputs: the number of calls, total duration in seconds, the last call date, the duration and ID of the last call, and a Has call recording Y/N flag. For deals, the robot first finds the related calls through CRM activities, because telephony statistics do not index deals directly. Use it to measure communication intensity on a deal before a stage change, flag cold clients with no calls, pass call durations into a report, or trigger a scenario when the entity has had no calls yet. Use the results in the conditions and fields of later process steps.
What input parameters does the robot accept?
| Parameter | Type | Required? | Default |
|---|---|---|---|
| Entity type | select | yes | LEAD |
| Entity ID | int | yes | |
| Period start date (optional, ISO 8601) | string | — |
What does the robot return?
| Parameter | Type |
|---|---|
| Number of calls | int |
| Total duration (seconds) | int |
| Last call date | string |
| Last call duration (seconds) | int |
| Last call ID | string |
| Has call recording (Y/N) | string |
Scenario: monitoring activity on a deal
- A deal has been in the In progress stage for more than 3 days
- The robot requests the calls for the deal and gets their count
- If the count equals 0, the process assigns the manager a task to call the client