Skip to content
ZBIX website
ZBIX CRM 1.2.0

SLA Policies

SLA policies measure an initial response commitment on eligible new Leads or Deals. A business calendar determines the deadline; an eligible completed CRM activity satisfies the commitment.

Use a policy to track first-response timeliness and expose overdue work. Recording an activity is not evidence that a real customer interaction occurred.

  • Sales automation is enabled and the user can manage Workflows.

  • A published Business Calendar version exists. Choose the activity types that count as response evidence.

  1. Open Automation > SLA Policies and select Create sla. Enter Name and Module.

  2. Choose Calendar version. Set Owner changes to Pause for review or Use new owner for future actions.

  3. Configure Eligibility conditions, Target business minutes and Priority. Select at least one Qualifying completed activity type: call, meeting, visit or task.

  4. Select Save draft, Validate saved draft, Publish saved draft and Activate published version.

  5. After eligible record creation, inspect the SLA instance under Sales automation activity. Open or create the appropriate related activity and record completion when the work is actually finished.

  6. Review History for met or breached outcomes. Use Sales service commitments reporting to filter the cohort, module, owner and team and compare Active, Due within 24 hours, Breached, Met and Compliance.

The instance retains a deadline, response outcome and execution history. The summary reports measured compliance for its stated denominator.

Field or controlRule
Target business minutes1–525,600
Priority0–10,000; lower first
Qualifying typesOne or more of call, meeting, visit, task
Calendar versionRequired published calendar
Owner changesPause for review or follow the new owner
SLA policies list
SS-036 · SLA policies list. Demonstration capture, 28 October 2026. Select the image to enlarge.
  • Target business minutes is 1–525,600 and priority is 0–10,000. Creating an activity without completing it does not satisfy the SLA.

  • Starts are based on eligible record creation. Arbitrary follow-up event/reset policies are not exposed.

  • Historical late responses remain distinguishable from timely performance. Active, paused and unbreached cancelled instances are excluded from the displayed compliance denominator.

  • Cohort date filters are UTC and the end date is exclusive. An empty measured denominator is shown as No measured results.

  • An activity did not satisfy the SLA: verify the source association, completion state, qualifying type and relevant instance history.

  • Deadline appears wrong: inspect the pinned calendar, timezone and working exceptions.

  • Policy does not attach to existing records: the documented automatic start is record creation; do not assume activation backfills old records.

Download manuals ↓

Open full-resolution image