Google IT Support study materials
Google IT Support study resources

The Printer That Only Fails When You Are Not Looking

Google IT Support · Put your knowledge to work in context.

All case studies

The Printer That Only Fails When You Are Not Looking

You are a tier-1 support agent at a 300-person logistics company. Dana, a warehouse shift supervisor, has called three times in two days about a label printer that stops printing mid-shift, forcing her team to re-scan more than 60 parcels by hand each time. Every time you remote in, the printer works. You have cleared the print queue twice; the fault returns. Dana is now copying her director and says, 'Fix it today or replace it.' Your queue holds 41 open tickets, the P2 SLA is 8 business hours, and you have 90 minutes left on shift. A spare printer is in stock but needs two days of procurement approval. There is no known permanent fix.

1. What is your next action, and how do you respond to Dana? Justify the trade-offs you are accepting.

Read the worked answer

Do not simply clear the queue again and close the ticket. An intermittent fault that disappears when you observe it is an evidence problem, not a queue problem.

  1. Capture evidence while the fault is live. Turn on print job logging and Event Viewer auditing on the print server, and ask Dana to record the exact time, job name, user, and whether the printer panel shows any error. Give her a one-line form to fill in. This costs her 10 seconds per event and gives tier 2 something to work with.
  2. Provide a workaround today. Route the team's labels to the nearest working printer or issue the in-stock spare as a short-term loaner, with your manager's written approval by email.
  3. Escalate with a package. Send tier 2 the logs, printer model, firmware version, driver version, and the pattern you have observed. Do not escalate an empty ticket.
  4. Be honest about the promise. You cannot promise a root cause today. You can promise ownership, a callback time, and a hardware workaround.

Trade-off: telling Dana 'it will be fixed today' buys 30 minutes of calm and destroys credibility when it is not. A measured commitment that you keep is worth more than an escalation she has to chase.

2. Dana's director emails: 'I need root cause and a fix date by end of day.' Write your reply and explain what you deliberately leave out.

Read the worked answer

Reply structure:

  • Status: the issue is confirmed and owned by me; ticket number and priority.
  • What we know: intermittent failures at specific times, printer healthy when tested remotely, logs now being captured.
  • What we do not know yet: root cause. Say this plainly rather than guessing at a driver or network cause you have not proven.
  • Impact and mitigation: the team no longer has to hand-scan parcels because labels are routing to X printer until the fault is resolved.
  • Next steps and dates: logs go to tier 2 today at 4:00 p.m.; hardware swap decision by Wednesday; I will update you at 4:00 p.m. today whether or not there is news.
  • Owner: my name, my direct line.

What you leave out: speculation about the cause (a guess in writing becomes a commitment), any blame directed at the warehouse team's operating habits, and internal queue statistics that are irrelevant to the director.

Reasoning: a director asking for a fix date is usually asking for certainty and a single point of accountability. Give certainty about the process and the communication cadence, not about the outcome you cannot control.

3. Should you swap the printer now, before procurement approval? Decide and defend your position.

Read the worked answer

Yes, as a logged loaner rather than a permanent replacement, provided you get one written approval from your manager first.

Why: the cost of delay is measurable and recurring. Sixty-plus hand-scanned parcels per shift, across three shifts, is hours of lost warehouse labor per day, which dwarfs the cost of a label printer. The procurement rule exists to control spend, not to prevent an obvious operational save.

Conditions that make it defensible:

  • Asset-tag and serialize the loaner, record who has it and the expected return date.
  • Get approval in writing (a single email reply is enough) so the decision is documented.
  • Keep the faulty unit. Do not let it be discarded or sent back before tier 2 inspects it; it is the only evidence you have.
  • Tell Dana explicitly that this is a workaround, not the fix, and that the original ticket stays open.

If approval is not available within the hour: escalate the decision to your manager with the cost calculation. Do not unilaterally issue hardware and do not silently let the warehouse keep hand-scanning. Either choice made in the open is defensible; a quiet one is not.