In short: a promise like "we reply within 8 business hours" only counts the hours you're open. A request that arrives at 3 pm on a Friday, with an 8-hour promise and 9-to-5 hours, is due at 3 pm on Monday, not 11 pm on Friday. This calculator works out the due time and checks a reply against it.
How the deadline is worked out
- Start the clock when the request comes in. If it arrives outside your hours, the clock starts when you next open.
- Count only open time. Each working day adds the hours between opening and closing. Days off and holidays add nothing.
- Stop when the promised time is used up. That moment is the due time.
"Clock time until due" shows how long that is in real time, which is what the customer experiences.
Setting response promises
- Use two promises, not one. Most support teams set a first reply time (we'll acknowledge you) and a resolution time (we'll fix it). The first is short; the second depends on the problem.
- Vary them by priority. An urgent outage might get a 1-hour first reply; a how-to question might get 8 business hours.
- Business hours or calendar hours? Business hours are fairer to a small team. Calendar hours (24/7) are for promises you can staff around the clock.
- Count waiting time fairly. When you're waiting on the customer for information, many teams pause the resolution clock.
Frequently asked questions
Which time zone does it use?
Your computer's own. If your team and customers are in different zones, enter the times as your team sees them.
Can I enter an overnight shift?
Not yet. The closing time must be after the opening time on the same day.
Does it save anything?
No. It runs in your browser and nothing is sent anywhere.
