Setting reply deadlines your support team actually meets

Updated 2026-09-24 · 6 min read · By the Convo360 team

Why a clock-time deadline is unfair and useless

The most common mistake is to set a two-hour first-response target and measure it against the wall clock. A message arriving at 9 pm on Saturday is then already four hours late when the office opens on Monday, and the ticket shows up red before anybody has done anything wrong.

Teams respond to this in one of two ways, and both are bad. Either they start ignoring the red, or they start gaming it by sending an empty holding reply at 9.01 am so the clock stops.

The fix is to count only the minutes your team is actually working. If you are open Monday to Saturday, 10 am to 7 pm, a message at 9 pm Saturday has its clock start at 10 am Monday. A two-hour target then means noon on Monday, which is a promise you can keep and a number that means something.

Convo360 counts deadlines this way by default. You set your hours and timezone once under the Support Desk's routing and SLA panel, and every target is calculated in working minutes from then on.

There is a fairness argument as well as a practical one. Support people are measured on these numbers, sometimes in appraisals. Measuring somebody against hours when the office was shut is the fastest way to teach a team that the metrics are theatre, and a team that believes that will manage the metric rather than the customer.

Choosing numbers you can actually hit

Do not start from what a competitor advertises. Start from what you did last month.

Pull your median first response time and your ninetieth percentile. The median tells you what usually happens; the ninetieth tells you what an unlucky customer experiences. Set the target somewhere between the two, closer to the ninetieth, and you will meet it most days without heroics.

These are reasonable starting points for a small Indian support team. Tighten them once you are hitting them consistently for a month, not before.

Set resolution targets with more slack than feels comfortable. First response is almost entirely within your control, but resolution often depends on a courier, a supplier or a refund cycle you do not run. A target that assumes everything goes smoothly will be missed by exactly the tickets that most needed attention.

It also helps to separate the two in your own head. Fast first response is a service promise. Fast resolution is an operations outcome. Confusing them leads teams to chase acknowledgements when the real problem is upstream.

Setting it up

In Convo360, open Support Desk and find the Routing and SLA panel. Three things to set:

1. Working hours and timezone. Be honest about Saturdays. If half the team works and half does not, count the hours you can reliably answer in.
2. Targets per priority. First response and resolution, in minutes, for each of the four priorities.
3. Escalation. Who gets told when a target is missed, and whether the ticket should be handed to somebody else automatically.

The watcher checks every minute, so a breach is flagged while there is still a chance to act on it. Escalation goes to the workspace owner, to any email addresses you list, and optionally reassigns the ticket.

One detail worth knowing: when a customer reopens a resolved ticket, the clock restarts rather than leaving the old deadline in place. Without that, a reopened ticket would sit permanently overdue and the watcher would never look at it again.

Convo360 recalculates a deadline whenever the priority changes, so a ticket raised as normal and escalated to urgent immediately gets the tighter target rather than keeping the old one. That sounds obvious and is a common gap in simpler tools, where the deadline is fixed at creation and never revisited.

Escalating to somebody, not to everybody

An escalation that emails the whole support group achieves nothing, because everyone assumes someone else is on it. Name one person.

The pattern that works in small teams is simple: the ticket's owner gets the first nudge, and the supervisor gets the second. If nobody has responded by the time the resolution target is at risk, the ticket moves to the supervisor outright so ownership is unambiguous.

Be careful with what goes into the escalation email. The subject line of a ticket is the customer's own words, and a customer can write anything they like. Convo360 escapes that text before it reaches your inbox, because a support team clicking a link inside an escalation they trust is exactly the mistake worth designing out.

Decide what an escalation is allowed to interrupt. A WhatsApp message to a supervisor at 11 pm about a ticket whose clock is paused until morning is noise, and people mute the channel that sends it. Because the deadlines are counted in working hours, the alerts only fire during them, which is what keeps them worth reading.

Write down what the recipient is meant to do. An escalation with no expected action is just an announcement of failure. 'Reassign or call the customer within thirty minutes' is a process; 'FYI, SLA breached' is not.

Reviewing the numbers without fooling yourself

Look at adherence monthly, and look at it by priority rather than in aggregate. A ninety-four per cent overall figure can easily hide the fact that every urgent ticket was late while a large number of low-priority ones were answered instantly.

Two habits keep the numbers honest. First, read the tickets that breached rather than only counting them; the cause is usually one recurring dependency, such as waiting for a courier or for finance. Second, watch reopen rate alongside adherence. If adherence improves while reopens climb, the team has learned to close tickets quickly rather than to resolve them.

When targets are consistently met for a month, tighten one priority by a small step and see whether it holds. Improving a target you are already hitting is far easier to sustain than declaring a target nobody believes and hoping the team rises to it.

Finally, be careful about publishing targets to customers. An SLA on your website is a promise, and customers will quote it back to you on your worst day. Most small teams are better off holding the target internally and simply being consistently quick, rather than committing publicly to a number they will miss during a festive rush.

If you do publish one, publish the working-hours version and say so plainly. 'Within one working hour, Monday to Saturday, 10 am to 7 pm' is a promise you can keep and a customer can understand.

Step by step

1. Measure what you do todayTake last month's median and ninetieth-percentile first response time from the Support Desk dashboard.
2. Set working hours and timezoneSupport Desk → Routing and SLA. Enter the hours you can genuinely answer in, including Saturday if you work it.
3. Enter targets per priorityFirst response and resolution for urgent, high, normal and low. Start near your ninetieth percentile, not your best day.
4. Name one escalation ownerAdd the supervisor's email and, if you want it, switch on automatic reassignment when a target is missed.
5. Review by priority after a monthCheck adherence for each priority separately, read the breached tickets, and only then tighten one target.

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.