Policy selection
Zendesk evaluates ticket triggers before its SLA policy system. The first matching ticket SLA policy applies. Group SLAs are separate. A custom field named Priority cannot replace the system Priority required for policy application.
In an original case, a broad Billing policy offers a 240-minute first-reply target, while a specific organization policy offers 45 minutes. Both match. Put the source-supported specific policy first; do not add the two targets together. Read back system priority and the selected policy.
Public reply evidence
In the taught human-agent subset, a private diagnostic is not the public agent reply used by the ordinary first-reply route. Inspect actor, audience and timestamp. The real product also has configurable automatic public-reply behavior beyond this local subset. Do not claim one rule covers every account.
A priority change can alter a target without resetting every elapsed clock. Solved-state SLA fulfillment is also distinct from a reporting measure that requires an actual public reply.
Business calendar
Calendar hours and business hours answer different timing questions. The local Zendesk course discloses a fixed teaching calendar. It does not model every holiday, time zone or group SLA. Preserve the source timestamps and calendar in your handoff; a colored breach label alone cannot explain the calculation.