Incident, ticket and problem
A ticket is one customer’s request and an incident is a failure of the service, which may generate hundreds of tickets or none.
IT service management also separates out the problem, the underlying cause of one or more incidents. Many teams say “incident” for any request, so it is worth being clear which one is meant.
Why it matters
An outage is forgiven more easily than silence.
A customer who does not know what is going on writes, calls and loses trust, and the team spends the incident answering the same question a hundred times. An up-to-date status page and a fast first notice cut those contacts and leave engineers free to fix the fault.
The phases of an incident
An incident goes through five phases, and each has its own message.
- Detection. Someone or something flags that the service is failing.
- Classification. Severity is set and one person takes the lead.
- Communication. The first notice goes out with the time of the next one.
- Resolution. The service is back and that is confirmed with affected customers.
- Review. The post-mortem is written with the cause and the actions.
What a status page contains
A status page shows, component by component, whether the service is working, and keeps the history of what has failed.
It lives outside the product’s own infrastructure so that it stays up when the product goes down.
- The state of each component, such as the app, the API or payments.
- The current incident, with dated updates.
- Scheduled maintenance, announced in advance.
- The history of past incidents.
- A way to subscribe to notices by email.
What to say in each update
Every update answers four questions, even when the answer to one of them is “not known yet”.
Staying quiet until the cause is found is the most common mistake.
- What is failing, in the customer’s words and without jargon.
- Who is affected and who is not.
- What the customer can do in the meantime.
- When the next update will arrive.
The word in Spanish law
Spain’s Law 10/2025 on customer service uses the word differently.
It calls an “incidencia” any request about how a contract is carried out, such as reporting a fault, asking to cancel or changing tariff. For basic services of general interest, its Article 17 sets a maximum of two hours to answer queries or incidents about service cuts or suspensions, with the known causes and the estimated time to restore.
