SkipCalls
Communication Checklists

Customer Communication Checklist for IT Companies

IT support and managed service providers win work by responding fast, asking the right triage questions, and setting clear expectations while you troubleshoot live systems. This checklist gives you exact words and steps for every touchpoint—so you stop losing urgent $100–$200/hr break/fix calls and protect your $1,000–$10,000/month managed services relationships.

0 of 43 completed0%

Pre‑Booking (First Call / First Message)

Booking & Confirmation (Scheduling + Prep)

Day‑Of Communication (Arrival, Start, and Live Updates)

During‑Job Communication (Troubleshooting, Scope, and Decisions)

Post‑Job Wrap‑Up (Resolution, Documentation, Billing)

Follow‑Up (Next Day, 7 Days, and Ongoing)

Pro Tips

  • 1.Build a one-page “Emergency Intake” form for your help desk: outage type, users impacted, last known good time, screenshots, recent changes (updates/firewall/ISP), and whether MFA is enabled.
  • 2.Create 4 canned SMS templates: (1) ‘Remote session link,’ (2) ‘On-site ETA,’ (3) ‘15-minute status update,’ (4) ‘Resolved + test steps.’ You’ll type less while troubleshooting.
  • 3.When a client says “the internet is down,” always confirm: Wi‑Fi vs wired, one user vs everyone, and whether phones/VoIP are down—this quickly points to ISP vs LAN vs DNS.
  • 4.For Microsoft 365 issues, always ask: Outlook vs webmail, single mailbox vs all users, and whether there are sign-in alerts. Clients describe symptoms, not systems.
  • 5.After any breach-like call, immediately tell them not to delete emails or wipe machines until you confirm evidence is captured (logs, headers, EDR alerts).

Frequently Asked Questions

What are the most common “emergency” calls IT companies get?

Full office internet down, email not sending/receiving (often Microsoft 365), server crash, ransomware or suspicious pop-ups, users locked out (MFA/password), VPN down, and firewall outages after updates or power events.

What should you ask on the first call when a client says “we got hacked”?

Ask: when it started, what they saw (ransom note, unusual logins, new admin accounts), whether anyone clicked a link, what systems are affected, and whether they have backups. Tell them not to wipe devices yet and that you’ll isolate affected systems and preserve logs.

How do you set expectations for break/fix pricing without scaring people off?

Anchor it to urgency and clarity: “Urgent break/fix is usually $100–$200/hr. I’ll confirm the likely cause and give you an hour estimate once I see logs and the system state.” Then explain what actions might increase time (restores, vendor waits, reimages).

What’s the best way to give updates during an outage?

Pick a cadence and stick to it (every 15 minutes). Use business language: what’s impacted, what you’re doing next, and what you need from them. Avoid long technical explanations unless they ask.

How do you prevent scope creep during on-site troubleshooting?

When you find unrelated issues (old firewall, failing drive, no backups), pause and label it: “This is separate from today’s outage.” Offer options with rough ranges (e.g., network setup $1,000–$10,000; audit $2,000–$20,000) and get approval before proceeding.

How do you stop missing calls while you’re working tickets?

Use a dedicated intake process: voicemail with a strict script, web form, or a 24/7 answering solution that captures triage details and routes true emergencies to you. The goal is to respond fast to real outages without being interrupted by spam or low-priority requests.

Stop losing urgent IT support calls while you’re busy fixing systems

If you run an IT support/MSP team and you can’t answer the phone while you’re in a server room, on a remote session, or handling an outage, set up a 24/7 answering workflow so “server down” and “we got hacked” calls get captured and routed fast. SkipCalls can answer, filter spam, transcribe, and book the right next step—so you win the first-response race and protect your managed services revenue.

More Resources for IT Companies