About 20 minutes to set up · claude.ai only

Turn a month of tickets into a summary the client reads

Today

The client's monthly summary starts life as a PSA export: sixty rows of subject lines, categories, and tech notes written for other techs. You either send it raw, which tells them nothing, or you rewrite it by hand on the last afternoon of the month for every client you owe one to.

With Claude

You paste the export and get back four sentences at the top, the tickets grouped by theme instead of by date, the recurring root causes called out, and open items with an owner named. You read it once, fix what it got wrong about their environment, and send it the same week the period closes.

The prompt

Paste this into claude.ai and replace anything in brackets.

You are helping a managed service provider turn raw ticket notes into a summary a non-technical client contact will actually read. Use only the ticket data I paste below. Never invent a ticket, a count, a response time, or an uptime figure. If a number would help and I did not give it to you, write NUMBER NEEDED instead of estimating it.

Client and who reads this: [client name or code, plus the role of the person reading it, for example an office manager or a CFO]
Period: [dates]
Ticket export or notes from our PSA: [paste the list with subject, category, status, and whatever tech notes you are willing to share]
What I already know matters this period: [anything you want called out, or write NONE]
Terms this client does not use: [for example GPO, endpoint, DHCP, whatever you end up translating on every call]

Produce this, in order:
1. Four sentences at the top: what we handled, what is still open, and anything they need to decide.
2. The tickets grouped by theme rather than by date. For each theme give a plain language description, the count from my data only, and the current status.
3. Anything that reads as a recurring root cause rather than a one off, with the specific tickets that support that read.
4. Open items, each with an owner named as ours or theirs, and what it is waiting on.
5. Two or three questions I should ask this client based on what these tickets show.

Rules: strip usernames, hostnames, addresses, serial numbers, and anything resembling a credential or license key out of your output, and tell me what you removed. Write it so an office manager understands it without making it sound like we did less work than we did.

What to skip in IT services firms and MSPs

  • Credentials and live infrastructure detail. Passwords, API keys, certificates, connection strings, firewall or VPN configs, network diagrams with real addressing, and security assessment or penetration test findings do not belong in a chat window, yours or your client's. On Free, Pro, and Max accounts whether your chats are used to improve Claude is a setting you control in Privacy Settings, and Anthropic does not use Team or Enterprise account data to train its models by default. Either way, a secret that leaves your password manager is a secret you no longer control. Reference credentials by where they live, never by value.
  • Security configuration and compliance attestations. Claude will hand you a confident conditional access policy, firewall rule set, or control mapping that looks right and is wrong in the details that decide whether it holds. It does not know the client's real environment, the current version of the framework, or what your assessor will accept. Use it to draft the explanation and the client facing summary, have a named engineer verify configuration against vendor documentation, and never sign an attestation or a security questionnaire on the strength of a chat.
  • Incident communication that carries legal weight. Once an event looks like unauthorized access, exfiltration, ransomware, or loss of regulated data, the message stops being a service update. Breach notification requirements vary by state and by contract, the clocks are short, and most cyber policies require you to involve the carrier and counsel before you communicate. Draft internally if it helps you think, then route anything client facing through counsel and your carrier before it is sent.

Want all 4 workflows for IT services firms and MSPs in your inbox?

Every prompt on this page plus the rest, so you still have them on Monday. One email, then four short ones on making it stick. Unsubscribe any time.

Or answer four questions and Claude writes three workflows for your specific business rather than the industry generally.

Before you try it

More for IT services firms and MSPs

Full guide for IT services firms and MSPs