Support Ticket Response Deadline
First-response and resolution deadlines by priority, in business hours.
Written and maintained by Paul Clark, Redmoon Software · Rules last verified
These calculators are for informational purposes only and do not constitute legal, financial, or professional advice.
How the Support Ticket Response Deadline works
The Support Ticket Response Deadline calculator turns a ticket’s priority into two dates rather than one: when the first response is owed, and when the resolution target expires. Enter the moment the ticket was opened, pick the priority, and set the support window your team actually staffs. Both clocks run in business hours and are reported as concrete timestamps.
Two targets rather than one is what separates a real support SLA from a simple deadline. A P1 that gets acknowledged inside the hour and then sits unresolved for two days has met one obligation and breached the other, and reporting a single figure hides that. The tiers used here follow the common commercial pattern — one hour to respond and four to resolve at P1, four and eight at P2, eight and twenty-four at P3, twenty-four and seventy-two at P4 — which is a reasonable default and not a standard. Your own contract governs, and the numbers in it are frequently different, so treat these as a starting shape.
Both clocks count in business hours, which is the part that trips teams up. A P2 ticket raised at 16:00 with a four-hour response target is not due at 20:00; it is due at 11:00 the next working day, because the clock stops when the support window closes and restarts when it reopens. Over a weekend that stretches further still. Set the working window to the hours you genuinely staff rather than to office hours generally — if the desk runs 08:00 to 18:00, entering nine-to-five will make every deadline look tighter than it is and will have you reporting breaches you did not commit. The tool does not model follow-the-sun coverage, paused clocks while awaiting customer response, or severity re-classification mid-ticket, all of which real SLAs address and all of which move the answer.
Worked example
A P1 ticket is opened at 16:00 on Monday, 1 June 2026, with the desk staffed 09:00 to 17:00. The one-hour response target is met by 17:00 the same day — just inside the window. The four-hour resolution target has only one hour of Monday left to consume, so the remaining three run from 09:00 on Tuesday, putting the resolution deadline at 12:00 on Tuesday, 2 June. The same ticket raised an hour later, at 17:00, pushes the response deadline itself into Tuesday morning.
Frequently asked questions
Why is my four-hour target due tomorrow?
Because the clock runs in business hours, not wall-clock hours, and it stops when your support window closes. A four-hour target on a ticket raised at 16:00 with the desk closing at 17:00 consumes one hour on the day and carries three into the next working morning. This is standard for business-hours SLAs and is exactly why the window setting matters: widen it to the hours you actually staff and the deadline moves earlier.
Are these the standard SLA tiers?
There is no standard. The one-and-four, four-and-eight, eight-and-twenty-four, twenty-four-and-seventy-two pattern used here is a common commercial shape and a sensible default, but your contract governs and many differ substantially — particularly for P1, where some agreements demand fifteen-minute acknowledgement and continuous effort until resolution. Read the numbers here as a template and replace them with yours where they differ.
What about clock pauses while waiting on the customer?
Not modelled. Most real SLAs stop the resolution clock while a ticket is awaiting customer input and restart it on reply, which can extend the effective deadline considerably. This calculator computes the unpaused case, which is the stricter one — useful as a worst-case target. If your agreement allows pauses, track the paused intervals separately and add them to the resolution figure.
What this calculator does not do
A limitation you know about costs far less than one you find after the deadline. These are the specific things this tool cannot work out for you.
- Priority tiers and their targets are contractual. The defaults here are a common shape, not an industry standard.
- It does not model clock pauses while a ticket awaits customer response, which most agreements allow and which is where real-world SLA disputes usually start.