Demo clockDark mode

Master data

7 registered listsShared by both companies

Types, priorities and their times, impact and urgency, the matrix.

Ticket types

What a client picks when raising a ticket. The types chosen on each system are what they see on it.

EditableClients see it
  • IncidentSomething that worked stopped, or gives a wrong result.
    Edit “Incident”
  • Service requestAn action we ask of the team: add, export, restore, configure.
    Edit “Service request”
  • QuestionA question on how to use something or what a result means.
    Edit “Question”
  • Change requestA change to how the system behaves, or a new feature.
    Edit “Change request”
  • Access requestCreate a user, change their permissions, or unlock an account.
    Edit “Access request”
  • Performance issueThe system works but is slow or late to respond.
    Edit “Performance issue”

Priorities & their times

Four, fixed in the ticket lifecycle; each one’s response and resolve times are the single reference for every client.

Four fixed — times editableClients see it
Critical
Response time
⁦30⁩m
Resolve target
⁦4⁩h

Open now6

3 tickets past their SLA

30-day compliance: ⁦9⁩ of ⁦11⁩1 cell suggests it
High
Response time
⁦1⁩h
Resolve target
⁦8⁩h

Open now10

2 tickets past their SLA

30-day compliance: ⁦13⁩ of ⁦19⁩2 cells suggest it
Medium
Response time
⁦4⁩h
Resolve target
⁦1⁩d

Open now13

3 tickets past their SLA

30-day compliance: ⁦21⁩ of ⁦26⁩3 cells suggest it
Low
Response time
⁦8⁩h
Resolve target
⁦3⁩d

Open now9

No breaches now

30-day compliance: ⁦30⁩ of ⁦34⁩3 cells suggest it

The four priorities are fixed in the ticket lifecycle, so none is added or removed; their times are what you edit, and they are the single reference for every client.

Impact degrees

How many are affected? The client picks one; its weight places it in the matrix.

EditableClients see it
  • 3WideThe whole organisation or its customers.Edit “Wide”
  • 2ModerateA whole department or a branch.Edit “Moderate”
  • 1LimitedOne user or a few.Edit “Limited”

Urgency degrees

How long can the work wait? The client picks one with the impact.

EditableClients see it
  • 3UrgentWork has stopped.Edit “Urgent”
  • 2HighDisrupts part of the work.Edit “High”
  • 1NormalCan wait; work goes on.Edit “Normal”

Priority suggestion matrix

Impact × urgency gives the suggested priority; the client sees the promised response time before sending. The supervisor confirms or changes it.

Every cell editable
Impact ↓ · Urgency →

2 cells differ from the weight ruleClick a cell to change its priority, or a row or column title to try it.

Matrix tester

Pick what the client would pick, and read what they are shown before sending.

Impact

Urgency

The client sees before sending

Critical

We will reply within ⁦30⁩m and aim to resolve within ⁦4⁩h.

  • This cell follows the weight rule.
  • 20 tickets were raised with this pair; the supervisor changed ⁦2⁩ of them to: High.
  • The supervisor has the final say: confirm or change it, and the change is recorded with the previous priority.

Resolution causes

Staff pick the cause when recording a resolution; cause reports are built from them.

Editable
  • Request fulfilled⁦28⁩ resolutions · ⁦23⁩ in 30 daysEdit “Request fulfilled”
  • Configuration error⁦27⁩ resolutions · ⁦17⁩ in 30 daysEdit “Configuration error”
  • Third-party integration⁦25⁩ resolutions · ⁦19⁩ in 30 daysEdit “Third-party integration”
  • Software bug fixed⁦16⁩ resolutions · ⁦10⁩ in 30 daysEdit “Software bug fixed”
  • Incorrect data⁦9⁩ resolutions · ⁦7⁩ in 30 daysEdit “Incorrect data”
  • User guidance⁦9⁩ resolutions · ⁦4⁩ in 30 daysEdit “User guidance”
  • Permissions⁦8⁩ resolutions · ⁦4⁩ in 30 daysEdit “Permissions”
  • Hosting or network problem⁦6⁩ resolutions · ⁦6⁩ in 30 daysEdit “Hosting or network problem”

The ten ticket statuses

The ticket lifecycle as the team sees it, and what the client reads for each. Read-only.

Read-onlyClients see it
  1. 1In a queue

    • Awaiting assignment5

      In the queue of a supervisor-assign team; waits for the supervisor to choose who works on it.

      SLA runsThe client reads:Under review
    • Available to take9

      In the queue of a self-take team; whoever starts on it takes it.

      SLA runsThe client reads:Under review
  2. 2Being worked

    • Assigned2

      Has an owner; work has not started yet.

      SLA runsThe client reads:Under review
    • In progress15

      Its owner is working on it, and the SLA clock runs.

      SLA runsThe client reads:In progress
    • Reopened1

      Reopened by the client or the team after a resolution; back with its owner.

      SLA runsThe client reads:In progress
  3. 3Waiting

    • Awaiting client5

      Information was requested from the client; the SLA clock is paused until they reply.

      SLA pausedThe client reads:Awaiting your reply
    • Awaiting internal action1

      On hold for an internal action; the deadline is still ours and keeps running.

      SLA runsThe client reads:In progress
  4. 4Finished

    • Resolved6

      The fix is recorded with its cause and action; waits for the client to confirm.

      SLA endedThe client reads:Awaiting your confirmation
    • Closed122

      The client confirmed; the rating is offered once.

      SLA endedThe client reads:Closed
    • Cancelled3

      Cancelled by a supervisor with a reason, e.g. a duplicate.

      SLA endedThe client reads:Closed

The ten statuses are the ticket lifecycle itself, so none is added or edited here; the figures are how many tickets are in each right now.