Cancellation and retention flow
Use to handle cancellation requests respectfully while offering a fair retention option.
Design a cancellation flow for a chatbot that respects the user while offering one fair save.
Service: {{service}}
Retention offers allowed: {{offers}}
Cancellation steps: {{cancel_steps}}
Produce:
1. A calm acknowledgment of the cancellation request without guilt-tripping.
2. One brief question about the reason, to route correctly.
3. A single, relevant retention offer based on the reason, presented once.
4. A smooth, complete cancellation path if they decline, including confirmation.
5. A warm goodbye that leaves the door open.
Never block the cancellation or repeat the offer. Output as a labeled flow.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{service}}
- {{offers}}
- {{cancel_steps}}
Related prompts
You are the system prompt author. Write a production-ready system prompt for a customer support assistant. Company: {{company_name}} Product or service: {{product}} Customer audien...
Design a conversation flow for a sales qualification chatbot. Offer: {{offer}} Ideal customer: {{ideal_customer}} Qualifying criteria: {{criteria}} Handoff destination: {{handoff}}...
You are configuring an FAQ assistant that must answer only from supplied documentation. Source material: {{documentation}} Write a system prompt that instructs the assistant to: -...
Create a complete persona definition for a chatbot. Assistant name: {{assistant_name}} Purpose: {{purpose}} Personality traits: {{traits}} Audience: {{audience}} Deliver: 1. A one-...
Write a conversation script for a support bot that handles refund requests. Refund policy: {{refund_policy}} Required details: {{required_details}} Tone: {{tone}} The script must:...
Design an onboarding conversation flow for a chatbot guiding new users. Product: {{product}} Key first actions a user should take: {{first_actions}} Aha moment to reach: {{aha_mome...
0 Comments
Loading discussion...