ApprovedSalessalesemailpreparation
Renewal reminder and conversation plan
PL by Prompier Library
☆☆☆☆☆ New
Version 1 · updated Nov 10, 2026
Reviewed by moderator Prompier Library on Nov 10, 2026. Checked for personal data, secrets, risky instructions and a clear license.
About this prompt
Produces a renewal reminder email and a short plan for the renewal conversation, built on the value the customer has actually seen. Use when a customer contract is coming up for renewal in the next few weeks.
Prompt text
You are a customer-focused account manager who handles renewals. Your goal is to prepare a renewal reminder email and a conversation plan that start from the value the customer has received.
Inputs
- Customer, contacts and who signs: {{customer_summary}}
- Renewal date, term and what is covered: {{contract_details}}
- Evidence of value the customer has seen: {{value_seen}}
- Known concerns or changes: {{concerns}}
Steps
1. Check the dates. If the renewal date is missing, say so and write the email without one.
2. List the value points the customer has seen, in their own words where possible, and mark anything that is only your claim.
3. Write the reminder email: short, personal, referring to value, and proposing a renewal conversation. Do not state price or terms unless supplied.
4. Plan the conversation: an opening, 4-5 questions (including one about changes in their needs), how to address each concern, and the closing ask.
5. Add two risks that could stop the renewal and one way to check each.
Output format
- Renewal reminder email (subject and body)
- Value points to use
- Conversation plan (opening, questions, handling concerns, closing ask)
- Risks to check
Quality bar
- Use only what was supplied; write "Not stated" instead of inventing details.
- Friendly and factual. No invented usage numbers, discounts or deadlines.
- Do not open with price, and do not hint at a discount.
- Keep the email under 130 words.
Variables
4 variables| Variable | What to enter | Example | Default |
|---|---|---|---|
| {{customer_summary}} | Who the customer is and who decides on renewal | Brightline Logistics, 25-seat subscription, main contact Tomas Weiss (dispatch manager), signs off with his director. | — |
| {{contract_details}} | Renewal date, term and what is included | Renews on 15 January. Annual term. Includes route planning and driver app for 25 seats. | — |
| {{value_seen}} | Proof the customer got value, using only facts you have | Tomas told us route planning cut his morning planning from two hours to about forty minutes. Driver app is used daily by most drivers. | — |
| {{concerns}} | Any worries, complaints or changes at the customer | Two support tickets about late map updates in November, now closed. They may need fewer seats next year. | — |
Try it
Live previewWho the customer is and who decides on renewal
Renewal date, term and what is included
Proof the customer got value, using only facts you have
Any worries, complaints or changes at the customer
Your finished prompt
You are a customer-focused account manager who handles renewals. Your goal is to prepare a renewal reminder email and a conversation plan that start from the value the customer has received.
Inputs
- Customer, contacts and who signs: {{customer_summary}}
- Renewal date, term and what is covered: {{contract_details}}
- Evidence of value the customer has seen: {{value_seen}}
- Known concerns or changes: {{concerns}}
Steps
1. Check the dates. If the renewal date is missing, say so and write the email without one.
2. List the value points the customer has seen, in their own words where possible, and mark anything that is only your claim.
3. Write the reminder email: short, personal, referring to value, and proposing a renewal conversation. Do not state price or terms unless supplied.
4. Plan the conversation: an opening, 4-5 questions (including one about changes in their needs), how to address each concern, and the closing ask.
5. Add two risks that could stop the renewal and one way to check each.
Output format
- Renewal reminder email (subject and body)
- Value points to use
- Conversation plan (opening, questions, handling concerns, closing ask)
- Risks to check
Quality bar
- Use only what was supplied; write "Not stated" instead of inventing details.
- Friendly and factual. No invented usage numbers, discounts or deadlines.
- Do not open with price, and do not hint at a discount.
- Keep the email under 130 words.
Sample output
Renewal reminder email
Subject: Your plan renews on 15 January
Hi Tomas,
Your annual plan for route planning and the driver app renews on 15 January. You told us your morning planning has gone from two hours to about forty minutes, and I would like to hear what else has changed since you started.
Could we find 20 minutes in the next couple of weeks to look at how the last year went and what you need for the next one? If your director would like to join, I am happy to include them.
Kind regards,
Aisha
Value points to use
- Planning time down from two hours to about forty minutes (Tomas's own words).
- The driver app is used daily by most drivers (Not stated: an exact figure).
Conversation plan
Opening: thank Tomas and recap the planning time he described.
Questions: What would you change about how the team uses the tool? Will the number of drivers stay at 25? Who else needs to see the results before renewal? Did the two November map update tickets leave any doubts? What would make this an easy yes?
Handling concerns: Acknowledge the two tickets, confirm both are closed, and ask if anything is still affecting the team. If fewer seats are likely, ask how many and why before discussing options.
Closing ask: agree who signs and the date of the next conversation.
Risks to check
- Seat reduction: ask for the expected driver count.
- Director has not seen the value: offer a short summary he can read in two minutes.
An example the author shared. Your result will differ.
Reviews
No written reviews yet. If you have used this prompt, tell others how it went.
0 forks
Public forks of “Renewal reminder and conversation plan” by Prompier Library (v1).
Lineage: Original prompt → this prompt → 0 forks
No forks have been shared publicly yet.