Response times and commitments
This page is for designers who write promises into support offers. A missed promise costs more trust than a modest promise kept.
Terms to define
| Term | Define |
|---|---|
| First response | When the customer hears from a person that the request is being handled |
| Resolution | When the problem is fixed, worked around or answered |
| Working hours | Days, hours and time zone, holidays |
| Severity | For example: site down; a feature broken; a cosmetic issue; a question |
| Clock stops | While you wait for the customer's information or access |
Severity levels, as an example structure
| Level | Meaning | First response | Resolution target |
|---|---|---|---|
| 1 | The site is down because of the theme | (your value) | (your value) |
| 2 | A main feature broken | (your value) | (your value) |
| 3 | A minor or visual issue | (your value) | Next release |
| 4 | A question | (your value) | - |
Step by step
- Look at your actual availability over a normal month.
- Set values below that, with room for illness and holidays.
- Arrange a backup person for level 1, or do not promise level 1 outside working hours.
- State what you do when you miss a time (a credit, an apology, an escalation) in the terms.
- Measure: write down when each request arrived, was answered and was resolved.
Related pages
- Designing support tiers
- Warranty and liability
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.