Support response targets and business hours
Measure the response policy your team actually intends to deliver.
Set first-response, next-response and resolution targets by priority, calculated in configured business minutes with explicit waiting-state behavior.
A target needs a calendar and a shared meaning.
A label such as urgent means little without a defined response policy. Helpdesk targets connect priority to due times for initial response, later responses and resolution. These are operational measurements chosen by your organization, not a Tsumira guarantee of response time or customer outcome. Define what your team can maintain and who reviews exceptions before using due indicators as a customer-facing commitment.
Review business hours and timezone first.
Targets are calculated in business minutes using the configured hours. The initial policy uses Monday to Friday, 09:00–18:00 Tokyo time; it must be reviewed for your location and staffing. A business-hour target differs from elapsed wall-clock time. Test a request near the end of a working day so the team understands how the due time moves across non-working periods.
- Configured working hours instead of assumed local defaults
Distinguish first answer, follow-up and solution.
The first-response clock begins at ticket creation and is met by the first public agent reply. Internal notes do not count as customer answers. After an agent has replied, a new customer message can start the next-response clock. Resolution measures the path toward solved status. Choose targets independently by priority; a quick acknowledgment does not demonstrate that the underlying issue has been resolved.
- Three distinct target clocks and public-reply semantics
Understand waiting states and breach review.
Pending and on-hold states pause the resolution clock; resuming uses the remaining business minutes. Due and breached indicators help organize queue review under the defined state rules. Changing priority can recalculate running targets from their relevant start. Clear targets to disable the policy rather than assuming an empty configuration implies hidden defaults. Review why a breach occurred instead of changing status merely to improve appearance.
- Defined pauses, recalculation and visible breaches
A concrete workflow
Define policy
Agree realistic priority and response expectations.
Configure time
Review timezone, working periods and targets.
Test transitions
Check first reply, waiting, resume and priority changes.
Review breaches
Inspect the cause and next action rather than just the chip.
An illustrative working example
Illustrative scenario: a question received before closing time
A team receives a high-priority question late in the afternoon. Its business-hour policy determines the first-response due time. A public reply asks for a missing document; an internal note alone would not count. While waiting for the document, the team uses the appropriate state and understands the resolution pause. It tests what happens when work resumes the next day and checks that the configured timezone matches its actual location.
Questions about this topic
Are these guaranteed service levels?
No. They are your configured operational targets, not guaranteed staffing or outcomes.
Does an internal note meet first response?
No. The first public agent reply is what counts as a response to the customer.
Are default hours local to every country?
No. The initial policy uses Tokyo working hours. Review timezone and periods explicitly.
Can targets be disabled?
Yes. Clearing the target configuration switches this policy off; empty targets do not infer a hidden SLA.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Zendesk
Application concept: Compare Zendesk policy definitions with Tsumira's first-response, next-response and resolution clocks rather than copying numbers blindly.
Slack
Application concept: Plan a reviewed Slack escalation notice for a breached target without promising automatic resolution or guaranteed staffing.
Microsoft Teams
Application concept: Use a Teams service review to agree business hours, timezone and responsibility for approaching response targets.