(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Client told to call, instead emails saying they're available for a call
Ticket is opened right before client's vacation
Any Printer Ticket
Complete ticket to client's written specifications, not mental specifications.
Client calls in with self-diagnosed solution. Solution is incorrect
Client schedules call, but is unavailable at scheduled time
Client escalates ticket internally, blaming IT. Found to be at fault instead.
Attempted to reach client, client claims no attempts made
Ticket labeled ASAP/Urgent, but client unavailable.
User fat fingers password, blames literally anything else
User submits ticket but omits key details expecting IT to read minds
Client complains about lack of service, attempt to resolve but delayed due to client
Client attempts to use a feature outside of intended purpose, blames IT.
Client asks help, then refuses help outside of slow, frustrating methods. IT blamed for issues
User emails non-urgent issue, calls immediately after
Repeatedly reach out to client, no response until ticket closure
Client attempts IT project without IT. Ticket based on mess, not on project.
Client needs to be reminded about AD Sync
Client ignores previous communication, new ticket created
Client mentored in how to resolve reoccurring issue, calls in anyway
Ticket completed with above expected service, client complains
Ticket urgent, but documentation missing
Horizon Oxygen User forget password within one business week of new password
New ticket for new hire starting next day
Client makes request, then immediately makes another request reversing the initial request
