Tell my accounts about a product change that affects them
Customer-specific messages about a deprecation, migration, or major product change: what it means for each account and what they must do.
The prompt
A product change is coming that affects my customers. Help me communicate it to my accounts.
The change: [WHAT'S CHANGING - e.g. feature retired, new UI, required migration, API version sunset, plan or packaging change (for a price increase, use a dedicated price-change message)]
Timeline: [ANNOUNCEMENT DATE, KEY DEADLINES, END DATE]
Official company announcement or FAQ: [PASTE]
How it affects customers: [WHAT THEY MUST DO, what happens if they don't, any benefits]
My accounts and how each uses the affected area: [LIST - account, usage level, contract value, sensitivity]
Give me:
1. A segmentation of my accounts: heavily affected, lightly affected, not affected (or unknown - check usage), and who to contact first.
2. A core email for affected accounts: what's changing, why, what it means for them specifically, what they need to do by when (dates in bold), and how I'll help.
3. A variation for heavily affected or high-value accounts that offers a call and a migration plan.
4. Talking points and answers to likely objections ("why are you removing something we rely on?", "we don't have time to migrate").
5. A tracker layout: | Account | Impact | Contacted | Response | Action needed | Deadline | Status |.
6. Reminder messages as deadlines approach.
Stay consistent with the official announcement; don't add commitments, exceptions, or dates that aren't in it. Mark anything unclear [CONFIRM WITH PRODUCT].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- ANNOUNCEMENT DATE, KEY DEADLINES, END DATE
- PASTE
- WHAT THEY MUST DO, what happens if they don't, any benefits
- LIST - account, usage level, contract value, sensitivity
- CONFIRM WITH PRODUCT
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Draft replies to patient messages between appointmentsPersonal, on-brand replies for health and wellness practitioners, with safety checks for symptoms that need urgent care.
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.
- Reply to a constituent inquiry or complaintA respectful, accurate reply to a resident that answers the question, explains next steps, and protects privacy and records obligations.
- Handle a formal patient complaint or grievanceAn investigation plan and a written grievance response that meets common timeline and documentation expectations for healthcare organizations.