Skip to content
Docs menu

Support SLA policies and reports

Set first-reply and resolution targets per priority, channel, tag or customer company, count them in business hours, pause them while snoozed, get breach alerts, and read response times, breach rate, volume, agent load and ratings on the Reports page or over MCP and REST.

View .md

Every conversation in Venom Support has two timers: the first reply and the resolution. Without any policy they come from the two targets in Support settings (a normal-priority conversation; urgent counts a quarter of them, high half, low double). SLA policies let different customers and kinds of conversation have their own.

Policies

Settings, Support, SLA policies. A policy has:

  • What it matches. Priority, channel (email, form, manual, SMS, WhatsApp, RCS, Telegram), tags (any of) and the customer's company (case-insensitive). A list you leave empty matches anything; all lists you fill must match.
  • Targets. First reply within N minutes, resolved within N minutes. A policy's targets are used as written (they are not scaled by priority: match on priority instead).
  • Business hours (optional). A time zone, the weekdays, and a daily window such as 09:00-17:00. Only working minutes count, so a 4-hour target set at 16:00 on Friday ends Monday at 12:00.

The policies are tried in the order of the list (use Up and Down); the first match wins. When none matches, the organisation's own targets apply. Owners and admins edit; every member can read.

A new conversation takes its policy when it opens. A conversation you retag, reprioritise or give another company is re-counted from its start. A closed one that comes back to life gets a new resolution time under whichever policy matches then. Deleting a policy leaves the due times it already set.

Snoozing pauses the timers

While a conversation is snoozed its running timers stand still. When it wakes (the time passed, you reopen it, or the customer writes again) the due times move later by as long as it slept. The pause is counted in wall-clock time, also for a policy with business hours.

Breach alerts

Support counts breached conversations in the bell as before. In addition, each breach is announced once, by the minute sweep: the support.sla.breached webhook event (the conversation id and number, which SLA, the due time and the priority, never the customer's message) and, when you set a channel under "Announce breaches in Slack", a message through your own Slack app. No third party is called.

Reports

/support/reports shows, for conversations created in the range (7, 30, 90 days or a year; filter by channel, priority, tag, assignee or policy):

  • first-response and resolution time: average, median and 90th percentile;
  • the share of SLAs missed for each timer (answered or closed late, or still waiting past the due time);
  • volume opened and closed per day (UTC), and by channel;
  • per-agent load: open, closed, missed SLAs and median first reply;
  • customer ratings (CSAT): good, not good and the share good.

An agent or script reads the same numbers with the support_report_get MCP tool (GET /support/report on the REST API). A report covers at most a year and the first 20,000 conversations of the range.

Tools

Tool REST Does
support_sla_policy_list GET /support/sla-policies The policies in order
support_sla_policy_save POST /support/sla-policies, PATCH /support/sla-policies/{policy} Create (name, first_response_min, resolve_min) or change one (policy = id or name); hours: null removes the business hours
support_sla_policy_delete DELETE /support/sla-policies/{policy} Delete one
support_report_get GET /support/report The report: from, to, channel, priority, tag, assignee, policy

Changing policies needs the owner or admin role. The Slack channel for alerts is set in Support settings only.