skills/re-engagement-email-writer/SKILL.md
Writes outreach to customers who have gone dark -- not responded to recent communications, missed meetings, or disengaged from the product. Differs from a check-in email by acknowledging the silence and offering a specific reason to re-engage rather than asking if everything is fine. Use when asked to write a re-engagement email, reach out to a silent customer, draft an outreach to a customer who has gone dark, break through to an unresponsive contact, or when a no-reply streak indicates the customer has disengaged. Also triggers for questions about customer silence, unresponsive accounts, re-engagement strategy, or breaking through communication barriers.
npx skillsauth add stephenrogan/csm-skills re-engagement-email-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Writes outreach to customers who have stopped responding. Different from a check-in email -- this acknowledges the silence (without making it awkward) and offers a specific reason to re-engage.
The fundamental question: why should this customer respond to you today when they did not respond to you last week? If you do not have an answer, the email will not work regardless of how well it is written. This skill helps you find and frame that answer.
Provide:
Before writing the email, diagnose the likely cause. The approach changes based on the root cause:
| Likely Cause | Signals | Email Approach | |-------------|---------|---------------| | Busy / deprioritised | Product usage is stable but contact is not responding to emails. No negative signals | Low-pressure, offer value, make it easy to respond with minimal effort | | Frustrated / dissatisfied | Usage declining, open support tickets, prior negative interactions | Acknowledge the possibility. Do not pretend everything is fine. Offer to address concerns | | Champion departure | Contact may have left. Email bounces, LinkedIn update, sudden silence after regular engagement | Investigate whether they have left. If confirmed, pivot to finding the replacement | | Decision avoidance | Approaching renewal with silence, prior conversation about concerns or alternatives | Direct but empathetic. Name the elephant: "I suspect the renewal is on your mind. I would rather have the conversation than wonder" | | Wrong contact | The person you are emailing is not the right person for this conversation (delegated, moved roles) | Ask: "Are you still the right person for this? If not, could you point me to the right contact?" | | You are not providing value | Your emails are generic check-ins with no specific reason to respond | Bring something genuinely useful. A benchmark, a new feature, a specific observation about their usage |
Best for: Busy/deprioritised contacts. Product usage is healthy.
Structure: Lead with something useful -- a metric, an insight, a new feature, a benchmark -- not a request for time.
Example: "Hi [name], I pulled some numbers on your team's usage and noticed your workflow automation count has grown 30% since last quarter. That puts you in the top quartile for companies your size. I have a few recommendations for features that could accelerate that trend further -- happy to share in a quick call or just send them over by email. Whatever works best for your schedule."
Why it works: You are offering something, not asking for something. The customer's response requires minimal effort (reply "send by email" and they are re-engaged).
Best for: When the silence is conspicuous and pretending it is not happening would be dishonest.
Structure: Acknowledge the silence without making it about you. Express genuine curiosity about what is driving it. Offer to adjust the engagement model.
Example: "Hi [name], I have reached out a few times without hearing back. I want to respect your time and not add to the noise. A couple of possibilities: (a) things are going well and you do not need anything from me right now, (b) something has changed and it would be helpful to talk, or (c) I am not reaching you at the right time or with the right topics. Any of those would be useful to know. A one-line reply is plenty."
Why it works: It is honest without being passive-aggressive. It gives the customer three easy options and asks for minimal effort. Most importantly, it names the silence without blaming them for it.
Best for: When your previous outreach was generic and did not give them a reason to respond.
Structure: Drop the thread entirely. Come in with something completely new -- a different topic, a different value proposition, or a different ask.
Example: "Hi [name], different topic from my recent notes -- I wanted to flag that we just released [specific feature] that directly addresses the [specific use case] your team was exploring last quarter. It is live on your account now. Would a 15-minute walkthrough be useful, or would you prefer I send a quick video?"
Why it works: If your previous emails were "just checking in" and they did not respond, more of the same will not break through. A new topic resets the conversation.
Best for: After 3+ unanswered outreach attempts. This is the closing email in the sequence.
Structure: Be direct that this is your last attempt on this thread. No guilt trip, no corporate language. Just honesty and an open door.
Example: "Hi [name], I know you are busy and I do not want to keep filling your inbox if this is not a priority. I will hold off on further outreach for now. When you are ready to reconnect -- whether that is about [specific topic], something else, or just a catch-up -- I am here. My door is always open."
Why it works: It releases the pressure. Some customers respond to the "last chance" framing because removing the obligation paradoxically creates permission to engage. Others genuinely need the space, and sending this email protects the relationship for the future.
If you are planning a re-engagement sequence (not just a single email):
| Attempt | Timing | Pattern | Escalation | |---------|--------|---------|-----------| | 1 | Day 0 (first re-engagement attempt after silence is identified) | Value-First or New Angle | None -- standard outreach | | 2 | Day 7 | Direct Acknowledgement | Consider changing channel (call instead of email) | | 3 | Day 14 | Honest Last Attempt | Consider reaching out through a different contact at the account | | Post-sequence | Day 30+ | No outreach. Monitor usage and engagement signals. If product usage drops, escalate as a risk signal | CSM manager awareness |
Critical rule: After the Honest Last Attempt, stop emailing this contact. Continued outreach after a clear sign-off degrades the relationship. If you need to re-engage later, wait for a genuine trigger (new feature, renewal approaching, usage change) and come in fresh.
For each email, the skill produces:
development
Structures the CSM's week based on their portfolio status, upcoming events, overdue items, and strategic priorities. Produces a time-blocked plan that balances reactive demands with proactive account management. Use when asked to plan a week, structure daily priorities, build a weekly schedule, allocate time across accounts, manage a busy week, or when a CSM feels overwhelmed and needs to determine where to focus. Also triggers for questions about time management, weekly planning, account prioritisation for the week, daily priority setting, or how to balance competing demands across a portfolio.
development
Constructs a compelling value narrative for a customer account by connecting product usage to business outcomes in the customer's language. Produces different versions for different audiences -- the champion, the CFO, the board. Use when asked to build a value story, articulate ROI, create a business case for the customer, prepare value evidence for a renewal or QBR, or when a CSM needs to translate usage metrics into business impact the customer will recognise. Also triggers for questions about value articulation, ROI storytelling, customer business case, value evidence, or how to prove the product is worth the investment.
data-ai
Takes raw usage data -- even a spreadsheet export or pasted metrics -- and identifies patterns, risks, and opportunities. Translates product analytics into account intelligence a CSM can act on. Use when asked to interpret usage data, analyse product metrics, make sense of a usage report, identify trends in customer behaviour, flag usage-based risks, or when a CSM has data but does not know what it means for the account. Also triggers for questions about usage analysis, product analytics interpretation, behavioural pattern detection, usage-based risk identification, or turning raw metrics into actionable insight.
development
Builds a structured 30-60-90 day plan for a CSM taking over a new book of accounts or joining a new team. Prioritises accounts by risk and value, identifies immediate relationship actions, and structures the ramp to full productivity. Use when asked to plan a book transition, create a new CSM onboarding plan, structure a territory takeover, build a 30-60-90 plan for a new role, or when a CSM is inheriting accounts and needs a systematic approach to getting up to speed. Also triggers for questions about account transitions, new book ramp-up, CSM onboarding to a portfolio, territory planning, or how to take over accounts from another CSM.