The trouble with "whatever status you like"
Most ticket tools treat status as a label anyone can edit into anything. Six months in, you have tickets that jumped from new to closed with no work recorded, "resolved" items that quietly reopen as fresh tickets (resetting every clock), and a dozen home-grown statuses that mean different things to different agents.
The damage shows up in two places. Accountability: nobody can say what happened to a request, because the trail is whatever people remembered to type. Reporting: your "average resolution time" is fiction when statuses move arbitrarily.
One workflow, enforced
NSupport Platform ships a single canonical incident workflow:
- New - reported, not yet picked up.
- In progress - an agent owns it and is working it.
- Pending - blocked on something external (a part, a vendor, another team).
- Awaiting customer - blocked on the reporter; the next move is theirs.
- Resolved - the agent believes it is fixed.
- Closed - confirmed and archived.
The platform enforces which transitions are legal. An incident cannot teleport from New to Closed; it has to pass through the work. The two waiting states are deliberately distinct, so "we are waiting on the customer" stops counting against your team and your queue dashboards reflect who actually holds the ball.
Because every workspace shares the same machine, every report means the same thing. Time-in-status, reopen rates, and backlog age become numbers you can defend.
The reopen window: an escape hatch with guardrails
"Resolved" is a claim, and the reporter gets to test it. If the fix did not stick, they can reopen the incident within 14 days - same incident, same history, same context. No fresh ticket that loses the thread, and no resolution stats that look great because failures came back under new numbers.
After the window, reopening becomes an admin decision. Late surprises still have a path, but a deliberate one - the incident record stays trustworthy instead of becoming an eternally reopenable thread.
One audit trail, not three half-stories
Every incident carries a complete change history: every status transition, priority change, reassignment, and edit, recorded structurally - what changed, from what, to what, by whom, when. Attachments and fields are diffed properly, so cosmetic noise does not pollute the record.
That history is merged with the comment timeline into one chronological feed. You read an incident top to bottom and see the whole story: reported, picked up, waited on a vendor, customer confirmed, resolved, closed - with the conversation woven through at the moments it happened.
When an auditor, a customer, or your own manager asks "what happened with this one?", the answer is a scroll, not an archaeology project.
Structure is a kindness
Enforced transitions can sound rigid. In practice the opposite is true: agents stop debating what statuses mean, reporters always know whose move it is, and managers trust the numbers. The workflow does the bookkeeping so people can do the work.