AI LunchroomPractice AI. Do real work.
AI prompts by job

AI prompts for msp technicians and consultants

You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do. These prompts are written for that work — copy one into ChatGPT, Claude, Copilot, or Gemini, or practice it with step-by-step feedback and keep the ones you reuse.

What AI is actually good for in this job

Not everything — but these four come up every week, and they are all writing tasks, which is where today's tools are strongest.

Before you paste anything

What never goes into a chatbot in this job

Never paste client credentials, network diagrams, RMM or PSA exports, or anything covered by the client's own confidentiality terms. You hold other companies' keys — your standard has to be higher than internal IT's.

Which tool: Your PSA and RMM vendors are shipping AI features fast; those are usually a better bet than a general chatbot because the data stays in the tool. For writing, a general chatbot is fine with client specifics stripped.

Write the client-facing incident summary after an outage

The rough version you start from
Outage notes: Tuesday 2:10pm the client's file server stopped responding. A backup job filled the data volume. Cleared old snapshots, service back 3:25. About 40 users lost access for 75 minutes, no data loss. Root cause: retention policy changed in the last migration and disk alerts were set at 95 percent, not 80. Retention and alert both fixed. Client owner is annoyed, QBR next month.
Copy this prompt
I work in managed service provider support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Write the client-facing incident summary after an outage

Source material:
Outage notes: Tuesday 2:10pm the client's file server stopped responding. A backup job filled the data volume. Cleared old snapshots, service back 3:25. About 40 users lost access for 75 minutes, no data loss. Root cause: retention policy changed in the last migration and disk alerts were set at 95 percent, not 80. Retention and alert both fixed. Client owner is annoyed, QBR next month.

What to give me:
Give me a client-facing incident summary with timeline, impact, cause, what we fixed, and what changes to prevent a repeat, in plain language for a business owner.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Check the timeline, user count, and no-data-loss claim against your logs, and that it owns our part in the cause without overpromising prevention.

Turn an onboarding audit into a recommendations document

The rough version you start from
New client audit: 22 users, mix of Mac and Windows. No MFA on email for 9 of them. Backups cover only the file server, not laptops. Two staff share a login. Firewall firmware 3 years old. Antivirus expired on 6 machines. Guest and staff wifi on one network. Domain registered under a former employee. Nice office manager, tiny budget.
Copy this prompt
I work in managed service provider support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Turn an onboarding audit into a recommendations document

Source material:
New client audit: 22 users, mix of Mac and Windows. No MFA on email for 9 of them. Backups cover only the file server, not laptops. Two staff share a login. Firewall firmware 3 years old. Antivirus expired on 6 machines. Guest and staff wifi on one network. Domain registered under a former employee. Nice office manager, tiny budget.

What to give me:
Give me a recommendations document ranked by risk: top three urgent items first, then next 90 days, each with a plain reason, rough effort, and the decision the client must make.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Make sure the ranking reflects your judgment, every finding came from the audit, and no price or timeline is quoted that you haven't confirmed.

Draft a plain-language explanation of why a client needs a security change

The rough version you start from
Need to explain to a small architecture firm, owner non-technical, why we're turning on MFA for everyone and blocking legacy email sign-ins next month. They hate change. Two people use an old scanner that emails with an SMTP password, which will stop working, but we can switch it to an alternative. They pay for managed security but pushed back last time.
Copy this prompt
I work in managed service provider support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Draft a plain-language explanation of why a client needs a security change

Source material:
Need to explain to a small architecture firm, owner non-technical, why we're turning on MFA for everyone and blocking legacy email sign-ins next month. They hate change. Two people use an old scanner that emails with an SMTP password, which will stop working, but we can switch it to an alternative. They pay for managed security but pushed back last time.

What to give me:
Give me a plain-language email explaining why the change is needed, what staff will notice, the scanner plan, and what we need approved, without scare tactics.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Confirm every technical claim and date matches your plan, and that the risk described is stated accurately, not exaggerated for effect.

Summarize a month of tickets into QBR talking points

The rough version you start from
Month summary: 61 tickets. Top categories: password resets (14), printers (9), new hire setups (8), slow laptops (6). Recurring: Outlook crashes on 4 older laptops. Average response about 40 minutes, 2 tickets over SLA. One minor outage. Patching 96 percent compliant. 5 laptops over 4 years old. Want to push a refresh without sounding like a sales pitch.
Copy this prompt
I work in managed service provider support. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Summarize a month of tickets into QBR talking points

Source material:
Month summary: 61 tickets. Top categories: password resets (14), printers (9), new hire setups (8), slow laptops (6). Recurring: Outlook crashes on 4 older laptops. Average response about 40 minutes, 2 tickets over SLA. One minor outage. Patching 96 percent compliant. 5 laptops over 4 years old. Want to push a refresh without sounding like a sales pitch.

What to give me:
Give me five QBR talking points: the headline, what we fixed, one recurring issue with data, the SLA misses stated honestly, and a refresh recommendation framed as cost avoidance.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Verify every count and percentage against your PSA report, and that the SLA misses are stated plainly rather than smoothed into a positive.

More prompts for this job

Drawn from AI Lunchroom's IT, Systems & Technical Support practice labs and rewritten for this role. See every IT, Systems & Technical Support prompt.

Outage update note

Turn incident facts into a calm, plain-language update for affected users.

Copy this prompt
I work in managed service provider support. Help me create one outage update for the Denver floor that I can review and edit before use.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Write one plain-language outage update that says what's affected, what's being done about it, and what people should do right now instead of re-reporting it one at a time.

Source material:
"Hey — got off a call with facilities. VPN's been dropping every eight or ten minutes for the whole Denver floor since about 7:40 this morning, ticket #4412 already has six people piled onto it. Networking's pretty sure it's the firewall rule that went in overnight, still confirming. Nobody's lost any files, this is just getting kicked off the VPN and having to log back in, but Danielle at the front desk has pinged the IT chat four times already asking if this is showing up somewhere. My manager wants a note out to the floor by 9 so people stop re-reporting it one at a time. Can you get that written up?"

Return only the finished work:
1. outage update for the Denver floor
2. what's causing it
3. what to do right now instead of re-reporting it

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Knowledge base draft

Turn a solved ticket into a reusable support article with symptoms, cause, resolution, and when to escalate.

Copy this prompt
I work in managed service provider support. Help me create one knowledge base draft that I can review and edit before use.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Turn a resolved help-desk ticket into a knowledge-base article another support tech can follow.

Source material:
"Closing out #4544 -- Priya Chandrasekaran (Finance, 3rd floor) couldn't get the video-call app to pick up her headset after Tuesday's Windows update pushed to her laptop. Turns out the update reset the default audio input back to the laptop's built-in mic, and the app's microphone permission under Windows privacy settings had flipped off too. Fixed it by resetting the input device inside the app's audio settings and re-enabling the app permission, then had her fully quit and reopen the app -- closing the window alone didn't make the permission change stick. Took about twenty minutes. This is the third ticket like this since Tuesday's patch went out, so we should probably get a KB article up before it turns into ten more."

Return only the finished work:
1. knowledge base draft
2. applies-to section
3. step-by-step fix

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Ticket summary basics

Summarize a user issue into device, app, error, impact, and the first diagnostic question.

Copy this prompt
I work in managed service provider support. Help me create one ticket summary that I can review and edit before use.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Create a structured ticket summary from a user report so it can be routed without extra back-and-forth.

Source material:
Ticket #4417 came in through the chat widget at 8:52 this morning: "Hey, this is Marcus in Receiving -- I can't log into the purchase-order portal, it just spins on the loading screen and then kicks me back to sign-in. I tried it on my phone too, same thing. I've got a PO for the forklift parts that has to go out before the 11am cutoff or the vendor cancels the order. Can someone look at this before then?" The queue also shows two other open tickets mentioning the purchase-order portal timing out since 8:30 -- one of them from Denise in Shipping.

Return only the finished work:
ticket summary

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Support triage prompt

Create a reusable prompt that turns user-reported issues into structured tickets, troubleshooting paths, and escalation decisions.

Copy this prompt
I work in managed service provider support. Help me create one reusable support-triage prompt that I can review and edit before use.

Relevant context:
- Role: MSP Technicians and Consultant
- Work context: You support many small clients at once, each with a different stack, and you write far more client-facing explanation and documentation than internal IT staff do.

Task:
Build a reusable triage prompt that sorts incoming support tickets like this one into categories, flags anything that needs escalation, and gives safe next steps without exposing sensitive details.

Source material:
"Leah Bennett on the claims team just opened ticket #4577 -- she says she can't get into the shared drive for the Meridian account, keeps throwing 'access denied,' and she's on a deadline to send the reconciliation packet by 3pm. She also pasted her whole error screenshot into the ticket notes, which includes her username, her manager's name, and what looks like a partial account number from a customer record. Two other people on her team, Griffin and Sam, are apparently locked out of the same drive too, but only Leah opened a ticket. I need something I can hand to whoever's on triage today that sorts this the right way without repeating any of that sensitive stuff back verbatim."

Return only the finished work:
reusable support-triage prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

How to use ChatGPT or Copilot for msp technicians work

  1. Start from your own rough version. Type or dictate what you would have written anyway, however messy. A prompt built on your real note beats a blank-page request every time.
  2. Say who it is for and how long it should be. "Two sentences for a supervisor" and "a checklist a new hire can follow" produce completely different output from the same facts.
  3. Strip the identifying details first. Client credentials, network diagrams, RMM or PSA exports, or anything covered by the client's own confidentiality terms. You hold other companies' keys — your standard has to be higher than internal IT's.
  4. Read every specific it produces. AI fills gaps with plausible invention — dates, amounts, names, policy numbers. If you did not supply it, do not trust it.
  5. Keep the ones that work. The value compounds when you stop rewriting the same prompt. Save it with a note about when to use it.
Practice, don't just copy

Get better at these — free

Copying a prompt is a start. AI Lunchroom walks you through the task step by step with your own work, checks what your AI tool gives back, and saves the prompts you will reuse. Free to start, no credit card.

Related jobs in IT, Systems & Technical Support

MSP Technicians AI questions

How do I use AI without leaking client data?

Work in generic terms: “a 40-user client running Microsoft 365 and a NAS” carries no identifying detail but gives the model enough to be useful. Add the client's specifics after, in your own document.

Can AI write my QBR decks?

It can write the narrative around your numbers. Pull the ticket and uptime data yourself — a fabricated metric in front of a client is a trust problem you will not recover from quickly.