Plan requirement
| Subscription | Any plan |
| Access | Agent |
Where to check whether the problem is yours or Zendesk's. Look here before you start investigating.
Check it
- Open the Zendesk status page.
- Find the pod your account runs on.
- Read current incidents and recent history.
- Check planned maintenance.
Know your pod
Accounts run on different infrastructure, and an incident affects some and not others. Without knowing yours, the status page tells you that something is wrong somewhere, which is not useful.
Find it once and write it down where your team looks during an incident.
Check it first
When email stops arriving or the interface is slow, five seconds here saves an hour of looking at your own configuration. It is the cheapest diagnostic step available and the one people skip.
Not everything appears
Small or regional problems may not be posted, and posts can lag the experience by a while. A clear status page is evidence, not proof.
Tell customers the truth
During a confirmed incident, saying so is better than an unexplained delay. Customers accept a platform problem far more readily than silence.
Look at the history after the fact
When somebody asks why last Tuesday was slow, the incident history usually answers it. Worth checking before writing a post-mortem about your own configuration.
Comments
0 comments
Article is closed for comments.