Priority and support agreement matched.
Support escalation and SLAs
Track support events against agreed service rules and surface cases that need an authorized escalation.
A timing alert needs the right service definition.
Ticket creation, staff response and resolution are different events. Escalation workflows need the actual support agreement, business calendar and pause rules before they can interpret a deadline or tell a customer what service is promised.
The workflow makes timing context visible and prepares an owned escalation; it does not turn a dashboard threshold into a new SLA.
Timer uses the agreed business calendar.
Relevant case context travels with the alert.
Make the clock useful to the people who own the case.
Consistent timing context
Use the agreed event definitions and business-hour calculations.
Owned escalations
Send the relevant case context to a responsible support owner.
Reviewable exceptions
Show missing timestamps, paused cases and unresolved alerts.
Measure the moment that the agreement actually defines.
A support clock is only meaningful when the team agrees what starts it, what pauses it and who receives the next action. Keep response, acknowledgement and resolution states distinct so escalation does not hide the real customer experience.
Was the first human response made within the applicable window?
Has an accountable owner accepted the case and its current priority?
Was the customer outcome completed, or is the case still open?
Holiday calendar and waiting-state rules applied from the configured support policy.
From support event to accountable escalation.
Identify the service rule
Match the ticket to the approved priority, agreement and calendar.
Track the relevant events
Read the source timestamps and state transitions used by the agreed calculation.
Notify the responsible owner
Surface approaching or breached thresholds through the supported alert route.
Record the response
Track acknowledgement, reassignment and the actual service outcome.
Illustrative workflow. Actual service terms, calendars, integrations, pause rules and escalation ownership are confirmed during implementation.
Define the clock before connecting the alert.
Bring the approved support terms and source events together first. The implementation can then show what the workflow knows, what it cannot calculate and which owner must act next.
Keep service timing honest.
Do not create an uptime or response guarantee from a dashboard setting.
Keep response, acknowledgement and resolution metrics distinct.
Review clock behavior for holidays, waiting states and reopened tickets.
Practical questions.
Does this page promise a ZARIS support SLA?
No. Service commitments depend on the actual support agreement. The page describes a workflow for tracking agreed rules.
Can AI change ticket priority?
It can prepare a suggestion where scoped. Priority changes and escalation authority should follow the support team’s policy.
Ready to make support timing visible?
Bring your support terms, event definitions, business calendar and escalation owners. We will scope a workflow that surfaces the right action without inventing a service promise.
