Setting up manager control in Bitrix24 CRM

Configuring Manager Monitoring in Bitrix24 CRM

A sales department without oversight is money leaking away unnoticed. A manager misses a follow-up call, a deal stalls at the same stage for two weeks, tasks get closed without any real work done. The CRM accumulates this data, but does nothing with it on its own — active configuration of monitoring tools is required.

Key Metrics for Monitoring

Before setting up notifications and reports, define exactly what you are tracking. Three main metric groups:

Activity: number of calls/emails/meetings per period, average response time to an inbound lead, percentage of tasks completed on time.

Pipeline quality: average time at each deal stage, percentage of deals stalled for more than N days with no activity, conversion between stages.

Results: value of closed deals, number of won/lost, reasons for lost deals.

Configuring Notifications for Stalled Deals

This is the most practical tool. A deal with no activity for more than X days triggers a notification to the manager's supervisor.

Configuration via CRM → Settings → Business Processes or via pipeline robots:

1. Open the deals pipeline
2. On the relevant stage, add a Robot → Notify with the condition: N days have passed since the last change
3. Notification recipient — the responsible supervisor (via the variable {=Document.ASSIGNED_BY_ID.manager})

Alternative via REST — subscribing to an event and using an external trigger:

// Webhook on deal stage change
CRest::call('event.bind', [
    'event'   => 'ONCRMDEALSTAGEIDCHANGE',
    'handler' => 'https://yourserver.com/crm-webhook.php',
]);

Manager Activity Reports

The built-in section CRM → Analytics → Manager Activity shows the number of calls, emails, and tasks for a given period. Key filters: period, responsible person, activity type.

Limitation of the built-in report: there is no breakdown by activity quality — a 10-second call and a half-hour meeting carry equal weight. If more detail is needed, build a custom report via crm.activity.list:

$activities = CRest::call('crm.activity.list', [
    'filter' => [
        'RESPONSIBLE_ID' => 42,
        '>=START_TIME'   => date('Y-m-d', strtotime('-7 days')),
        'COMPLETED'      => 'Y',
    ],
    'select' => ['ID', 'TYPE_ID', 'DURATION', 'SUBJECT'],
]);

TYPE_ID: 1 — meeting, 2 — call, 3 — task, 4 — email.

Quality Control via Required Fields

Are managers skipping important data when creating deals? Configure required fields at specific stages: Pipeline → [stage] → Required Fields. Without filling in the specified fields, moving to the next stage is blocked.

Typical set of required fields by stage:

Head of Sales Dashboard

The standard Bitrix24 dashboard is weak for operational monitoring. Configure a custom widget via Desktop → Add Widget → CRM:

• Deals pipeline grouped by manager
• List of deals with no activity for more than 3 days
• Top 5 overdue tasks in the department
• Plan vs. actual deal value comparison for the current month

For more detailed analytics, use the Bitrix24 BI Connector (Enterprise plans and above) or export data to an external BI system via REST API and build reports there.

Automatic Responsible Reassignment on Inactivity

A critical tool for hot leads: if a manager has not worked a lead within 30 minutes, automatically assign it to someone else. Configuration via a robot on the "New" stage:

• Trigger: 30 minutes have passed since creation
• Condition: no completed activities on the lead
• Action: reassign to the next person in the queue + send a notification to the supervisor

The distribution queue is configured in CRM → Settings → Lead Distribution.

Monitoring without transparency breaks team trust. The rules of the game must be communicated to everyone in advance: what metrics are tracked, what threshold is considered acceptable, and what the consequences are for deviations.