msp-client-comms

Drafts operational client communications for MSPs using ten structured message templates.

75|17|Updated Jul 18, 2026
One-click install
npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-client-comms-rtfm-it-services-llc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: msp-client-comms
Source: https://github.com/RTFM-IT-Services-LLC/msp-claude-skills/tree/main/skills/msp-client-comms
Command: npx skills add https://github.com/RTFM-IT-Services-LLC/msp-claude-skills --skill msp-client-comms-rtfm-it-services-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, plain-English client messages during outages, maintenance, security incidents, and price changes is hard under pressure, and inconsistent or speculative wording creates legal and trust risks for an MSP. ## Core Features & Use Cases - Ten ready templates: planned and emergency maintenance, incident initial/update/resolved notices, post-incident summaries, security advisories, price change letters, user onboarding/offboarding confirmations, ticket closing notices, and security incident notices. - Built-in guardrails: plain-English rules, no cause speculation during active incidents, next-update commitments, and mandatory legal review for breach, liability, or contract-related messages. - Use Case: A P1 outage hits a client's email. Use this Skill to draft the initial notice within 30 minutes, hourly progress updates, the resolution message, and the post-incident summary within 3 business days. ## Quick Start Draft an initial incident notice to the client letting them know their email is down and we are working on it.

Frequently Asked Questions about msp-client-comms

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an outage notification email to clients?

Use the incident initial notice template: state the symptom in plain English, list observed facts only, give a workaround if one exists, and commit to a specific next update time. Send it within 30 minutes of confirming a P1 incident.

How do I announce a price increase to MSP clients?

Use the price change letter template: open with specific value delivered, state the new rate plainly with a 30-day notice period, and offer a call to discuss. Deliver it in or after a QBR when possible, and route contract mechanics through legal review.

When should a security incident notice go through legal review?

Any message touching a suspected or confirmed breach, regulated data, or anything that could read as an admission of fault must pass attorney review before sending. The template restricts content to observed facts, containment steps, and client asks.

What should a post-incident summary include?

Include the confirmed cause in plain language, a timeline from detection to resolution, total impact, and one to three concrete changes being made. Send it within 3 business days of every P1 incident.

Can I use this for sales outreach to prospects?

No. This Skill covers messages to clients already under agreement only. Sales outreach, prospecting, and pipeline communication belong to the separate msp-sales skill.