For IT Support Technician / Help Desk Analysts ·
What you'll accomplish
By the end of this guide, you'll use Claude to draft any IT communication — from routine ticket updates to high-stakes incident notifications — more quickly and with better tone than writing from scratch. You'll cover: maintenance notifications, incident communications, escalation emails, and difficult user interactions.
What you'll need
Claude is particularly well-calibrated for professional communication tone. For IT communications specifically:
Go to claude.ai. Click "Start for free." Create an account with your personal or work email. The free tier handles all communication tasks without hitting limits.
Tell Claude:
For a user waiting on resolution, type in Claude:
Write a professional ticket update message. Situation: still investigating network printer not responding, escalated to Tier 2. Expected: they'll have an update by end of day. Audience: standard business user. Tone: professional and reassuring, not over-apologetic. Under 80 words.
What you should see: A short, clean update that acknowledges the wait, gives a concrete timeline, and tells the user what to do if they need more urgent help.
For a widespread incident:
Write an IT incident notification email. Incident: Microsoft Teams is not working for all users company-wide. Current status: Microsoft reports the issue and is working on a fix (no ETA). Workaround: use Slack or phone for urgent communication. Tone: direct, clear, not alarming. Include a TL;DR at the top. Under 150 words.
What you should see: A clear communication with TL;DR, a brief description of what's happening, the workaround, and what users should expect next. Professional and calm.
For a frustrated or demanding user:
Write a professional response to a user who has emailed for the 3rd time asking why their ticket hasn't been resolved. Situation: it's a complex issue involving a network configuration that requires Tier 2 and a third-party vendor. It's been 4 days. Tone: empathetic, honest about the delay, clear about what's happening, and confident we're working on it. Under 120 words.
What you should see: A response that doesn't over-apologize but acknowledges the frustration, explains the complexity honestly, gives a realistic update, and ends with a commitment. The key is: no defensiveness, no blame-shifting, clear accountability.
For slow vendor support:
Write a follow-up email to a third-party vendor (firewall appliance support). We opened a P2 support ticket 6 days ago. The firewall has intermittent connectivity drops every 24-48 hours affecting 20% of users. No response since initial ticket acknowledgment. Tone: professional but firm. Request immediate escalation to senior support. Reference our ticket number [#] and the business impact.
What you should see: A concise, professional email that states the urgency factually, references the ticket, quantifies the business impact, and specifically requests escalation — without being hostile.
Routine ticket update:
Write a ticket update for a user. Status: [investigating/escalated/waiting on vendor/resolved]. Expected resolution: [timeframe]. Tone: professional, brief. Under 80 words.
Incident notification (all users):
Write an incident notification. System: [what's down]. Scope: [who's affected]. Workaround: [if any]. Status: [being investigated/fix in progress]. Next update: [when]. Under 150 words with TL;DR.
Vendor follow-up:
Write a follow-up email to [vendor]. Ticket #[number], opened [days] ago. Issue: [description]. Business impact: [users affected, operations impact]. Request: [escalation/ETA/specific action]. Professional but firm tone.
Difficult user response:
Write a response to a frustrated user who has followed up multiple times. Situation: [what's happening with the ticket]. Tone: empathetic, accountable, confident. Acknowledge the frustration without over-apologizing. Under 120 words.