CURVE
Five stages, and the fourth exists because you already told them it was fixed once.
What is CURVE?
CURVE is five stages: Challenge, Understand, Resolve, Verify, Engage. It is built for the reply that goes to a customer something has actually gone wrong for — and its distinguishing stage is the fourth one, which exists because in support you often have to fix a problem and repair the fact that you claimed to have fixed it before.
Most support replies fail identically: they open with an apology for the inconvenience, describe what will happen, and end with an offer of further assistance. That works on a first contact and fails completely on a fourth, because every phrase in it is one the customer has already been sent. By the time someone is writing for the fourth time, your previous language is evidence against you. CURVE handles this by opening with the specific failure rather than a general apology, and by requiring a Verify stage — something the customer can check themselves — because a further assurance from the party who already gave a false one is worth nothing.
Where CURVE Came From
A modern support convention with no author of record
CURVE has no documented inventor. It belongs to the customer-service and service-recovery tradition, where the underlying research is genuinely old — the observation that a well-handled complaint can leave a customer more loyal than one who never had a problem has been discussed in service literature for decades. The acronym is a modern compression of that practice, not a source of it.
Why Challenge comes before Understand
A deliberate inversion of the empathy-first script most support teams are trained on. Leading with feeling — "I completely understand how frustrating this must be" — before naming what went wrong reads as delay to somebody who has already explained it three times. Naming the failure first is itself the empathy; the Understand stage then has something to be sincere about.
And why Verify is a stage rather than a sentence
The structural insight that makes CURVE worth choosing. Ordinary reply frameworks end at Resolve — here is what we are doing. That is sufficient exactly once. On any repeat contact, the customer has already been told something was resolved and it was not, so the valuable thing is not another promise but a way for them to confirm it without asking you. Verify is that, and no other support framework has it.
The 5 Slots, One at a Time
Each slot is a decision. Leave it out and the model still makes it — just without you.
Specific, first, and without the softening opener. If a previous reply claimed the problem was fixed and it was not, that belongs in the first two sentences: it is the thing the customer is angriest about and the thing they expect you to avoid mentioning. Naming it unprompted is the single strongest move available.
Not a statement of feeling — an accounting. Four messages, three months, and the experience of being told it was resolved. Listing what they have actually spent on this demonstrates attention in a way that "we understand your frustration" cannot, because the second is a phrase and the first is a fact only someone paying attention would know.
Numbers and a date, in the first half of the reply. Vagueness here — "we are processing a refund" — is what turns a resolved complaint into a fifth message. £141, today, arriving in three to five working days is checkable; "as soon as possible" is another thing to chase.
The stage that makes CURVE different, and it matters most exactly when it is hardest to write. After a false all-clear, another assurance is worthless. Give them a thing to look at — the cancelled subscription visible in their account, the date the next charge would have fallen and will not, the reference number on the refund. Verification they can perform without you is the only kind that rebuilds anything.
Two things: whether anything else is required of them, and a route to a human rather than a queue. On a fourth contact, "reply to this email if you need anything else" sends them back into the system that failed three times. A named person or a direct route is a small cost and is the difference between a closing line and a repair.
One Task, Before and After
The task: A reply to a customer double-billed for three months who was already told it was fixed. Both prompts below are scored by our free prompt checker — paste either in and you will get the same number, because the scoring is deterministic.
Write a reply to a customer complaining about billing.
Nine words. You get an apology for the inconvenience, an assurance it is now resolved, and an offer of further assistance - all three of which this customer has already received.
Write a support reply using Challenge, Understand, Resolve, Verify, Engage. The situation, and the only facts available: the customer has been double-billed for three consecutive months. They noticed in month one, contacted support, were told it was fixed, and it was not. This is their fourth message. The overcharge is 47 pounds a month. The cause was a duplicate subscription created during a plan change in March. We can refund 141 pounds today and it reaches them in 3 to 5 working days. The duplicate has now actually been cancelled. Challenge - name what has gone wrong, including the part where we said it was fixed and it was not. Leading with an apology for the inconvenience will make this worse; leading with the specific failure will not. Understand - show that we know what this has cost them beyond the money: four messages, three months, and being told it was resolved. Resolve - what we are doing, with amounts and dates. Verify - how they can check it is actually fixed this time, which matters more than usual because we have already claimed it once. Engage - what happens next and how to reach a person rather than a queue. Write the reply as an email of 200 to 250 words in three short paragraphs, plain and direct, no headings, first person plural. They are angry and correct to be. Think through the fourth-message problem before you write: every phrase this customer has already been sent is now evidence of not being heard, and repeating any of it is worse than saying nothing. For example, open like this: ``` You have been charged twice a month since March, and we told you in April that it was fixed. It was not. ``` Every claim we make must be checkable by the customer without contacting us again, and the refund amount and date must appear in the first half. Ensure the Verify section gives them something they can check themselves rather than another assurance. Do not use the phrase we apologise for any inconvenience, do not describe this as an isolated incident, do not offer a discount code in place of the refund, and do not promise it cannot happen again.
Ninety-two. The move that does the most work is naming the false all-clear in the first two sentences, which is the thing the customer is angriest about and expects you to skip.
Ninety-two, and no scorer can hear how this reads to someone on their fourth message
One check is unreachable, and the two things that decide whether a recovery reply works are unmeasured:
No persona slot, and correctly so — this reply is from your company to a customer who is already unhappy with it. A "senior customer experience specialist" persona produces exactly the register that has failed three times.
The specific failure on a repeat contact, and completely invisible. "We apologise for any inconvenience" scores as politeness. To someone who has received it three times it is proof of not being read, and no rubric knows what this customer has already been sent.
"We can assure you this is now resolved" and "the duplicate subscription no longer appears under Billing" score identically. Only the second is something the customer can do without you.
The rule worth carrying into any service-recovery reply: on a repeat contact, every phrase they have already received is evidence against you. The practical version is uncomfortable and simple — read your previous replies before writing this one, and remove anything that appears in them.
Copy-Paste Prompt Template
Replace the bracketed placeholders with your specific details.
[The situation, and the ONLY facts available — including what previous replies already claimed] Challenge: [name what went wrong, INCLUDING the part where you said it was fixed and it was not. First two sentences. No apology opener] Understand: [what it has cost them beyond money — messages sent, months elapsed, promises made. An accounting, not a feeling] Resolve: [what you are doing, with amounts and dates, in the first half] Verify: [something THEY can check without asking you. After a false all-clear, another assurance is worth nothing] Engage: [what happens next, and a route to a person rather than a queue] [Read your previous replies first and remove anything that appears in them] [No "we apologise for any inconvenience", no isolated incident, no discount in place of the refund, no promise it cannot recur]
When CURVE Fits — and When It Does Not
- Repeat contacts, escalations, and complaints where a previous fix did not hold.
- Billing errors, where the money is checkable and vagueness is fatal.
- Retention replies to a customer who has said they are leaving.
- Incident notifications to individual affected customers.
- Any reply where the customer is right and knows it.
- Routine first-contact support, where five stages is more ceremony than the question needs.
- Public statements to many customers at once. Use TAG, which is built for that.
- Sales and marketing copy of any kind.
- Situations where you cannot actually resolve anything — Resolve becomes an empty stage.
- Replies where no previous claim was made, in which case Verify has little to do.
10 Ready-Made CURVE Prompts
Every prompt below was produced by the Frompting generator with CURVE selected — not written by hand for this page. Each is scored by our prompt checker; the median is 86/100. Click one to open it, then copy.
An order that arrived damaged 74
You are a customer support specialist drafting a written response to a buyer whose recent order arrived damaged. The response should: 1. Acknowledge the issue promptly and express sincere regret, showing empathy for the inconvenience caused. 2. Summarize the key details the buyer has provided (e.g., order number, product name) and ask for any missing information needed to process a solution. 3. Offer a clear resolution option-such as a replacement shipment, a refund, or a discount on a future purchase-based on the company’s standard policy. 4. Explain the next steps the buyer should expect, including any required actions (e.g., returning the damaged item, providing photos) and the timeline for completion. 5. Invite the buyer to confirm the proposed solution or suggest an alternative, and thank them for their patience while reinforcing the company’s commitment to quality service. Write the reply in a friendly, professional tone suitable for email, keeping the total length between 730-960 words. **Quality criteria:** - Demonstrates genuine empathy and takes ownership of the problem. - Provides a concise, actionable resolution with clear next steps. - Ends with a courteous invitation for further input and a reaffirmation of customer value. **Boundary:** Do not mention internal policies, shipping costs, or legal language; focus solely on the customer-facing communication. [CUSTOMER_NAME: insert the buyer’s first name] [ORDER_NUMBER: insert the relevant order identifier] [PRODUCT_DESCRIPTION: insert the name or brief description of the damaged item] [COMPANY_NAME: insert the business name] If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue - do not ask for it and stop.
A recurring billing error 95
You are a customer-support specialist drafting a concise, empathetic reply to a user who reports a recurring billing error. Your response must: 1. Acknowledge the problem and express sincere concern. 2. Summarize the key details you understand about the issue. 3. Offer a clear, step-by-step resolution plan, including any immediate actions you will take and what the customer should expect. 4. Explain how the solution will be verified and how the customer can confirm the issue is resolved. 5. Invite further contact, reassure the customer of continued support, and suggest next steps to prevent future occurrences. Write the reply in plain, friendly language suitable for an email or ticket response. Keep the total length between **695-915 words**. Quality criteria: - Tone is apologetic yet confident, showing ownership of the problem. - Information is specific, avoids vague promises, and includes concrete next steps. - The message is easy to scan: short paragraphs, no more than two sentences per paragraph. Boundary: Do not include any internal policy details, pricing information, or legal disclaimer text. If any essential details are missing, state your assumptions and ask up to three clarifying questions before finalizing the reply. [CUSTOMER_NAME: provide the customer's first name] [ACCOUNT_ID: provide the relevant account or subscription identifier] [ERROR_DATE: specify the date(s) the billing error occurred] [BILLING_AMOUNT: indicate the incorrect amount charged] [CONTACT_METHOD: indicate preferred channel for follow-up, e.g., email or phone]
A complaint about a long support wait 86
You are a customer support specialist drafting a concise response to a client who has complained about an excessively long wait for assistance. Your reply should: 1. Acknowledge the difficulty the client experienced and express sincere empathy. 2. Summarize the situation based on the information provided, confirming the key details (e.g., date of contact, channel used, product/service involved). 3. Offer a clear, actionable solution or next steps to resolve the issue promptly, including any compensation or priority handling if appropriate. 4. Explain how you will follow up to ensure the solution works and the client is satisfied. 5. Invite the client to continue the conversation, ask any further questions, or provide additional feedback. Write the response in a friendly, professional tone suitable for a [CHANNEL: specify whether email, chat, or letter]. Keep the total length between 695-915 words. Quality criteria: - Shows genuine empathy and takes ownership of the problem. - Provides a specific, realistic resolution plan. - Ends with a clear call to action encouraging further dialogue. Exclude any internal process details or unrelated company policies. If any essential details (e.g., client name, product, date of incident) are missing, state your assumption and ask up to three brief clarifying questions before finalizing the response.
A customer threatening to cancel 75
You are a customer‑success specialist drafting a response to a client who has threatened to cancel their service. Your reply should: 1. Begin by acknowledging the client’s concern and expressing genuine empathy for the situation. 2. Summarize the key issue the client raised, confirming you understand the specific problem and its impact on them. 3. Offer a clear, concrete solution or set of actions you will take to address the problem, including any immediate steps and a timeline for resolution. 4. Request confirmation that the proposed solution meets the client’s needs and ask if there is anything else you can do to ensure satisfaction. 5. End with a warm invitation for further dialogue, reinforcing your commitment to their success and offering a direct contact method for any follow‑up. Write the response in a professional yet personable tone, suitable for email. Keep the total length between 180 and 250 words. Ensure the message is concise, avoids jargon, and uses plain language. [CLIENT_NAME: insert the customer’s name] [PRODUCT_OR_SERVICE: specify the product or service involved] [ISSUE_DESCRIPTION: brief description of the problem the client is facing] [PROPOSED_ACTIONS: list the concrete steps you will take, with any relevant dates] If any of the placeholders above are unknown, state your assumption and proceed, or ask up to two clarifying questions before finalizing the response. Quality criteria: - Demonstrates empathy and understanding. - Provides a specific, actionable resolution plan. - Encourages continued engagement and confirms the client’s satisfaction.
A complaint about a removed feature 78
You are a customer-support specialist drafting a response to a user upset about a removed feature. Your task is to write a concise, empathetic reply that: 1. Acknowledge the user’s frustration and the specific issue they raised. 2. Show that you understand why the feature mattered to them and gather any missing details needed to address it fully. 3. Offer a clear resolution-whether it’s a timeline for a possible return, an alternative solution, or a compensation option. 4. Explain how you will verify that the solution works for the user and what follow-up steps will be taken. 5. Invite the user to stay engaged, provide feedback, and let them know you value their continued use. Write the reply in **695-915 words**, using a friendly yet professional tone. **Quality criteria**: - Demonstrates genuine empathy and acknowledges the specific feature. - Provides a concrete next step or alternative that the user can act on. - Ends with a clear invitation for further dialogue. **Boundary**: Do not mention internal policies, development roadmaps, or speculative future features beyond what you state as a possible resolution. If any essential detail is unknown, insert a placeholder in the form **[PLACEHOLDER: brief hint]** (e.g., [FEATURE_NAME: name of the removed feature]). State any assumptions you make and ask up to three clarifying questions before finalizing the response.
A customer given wrong information 88
You are a customer-support specialist drafting a concise, empathetic response to a client who received incorrect information. The response must: - Acknowledge the issue and express sincere regret. - Summarize the mistaken information and clarify the correct details. - Offer a clear solution or next step to resolve any impact. - Confirm that the correction is accurate and invite the client to verify it. - Encourage continued engagement by offering additional help or a goodwill gesture. Write the reply for **[CUSTOMER NAME]**, who contacted support about **[PRODUCT/SERVICE]** and was told **[INCORRECT INFORMATION]**. The correct information is **[CORRECT INFORMATION]**. The desired outcome is **[DESIRED RESOLUTION]** (e.g., refund, replacement, updated instructions). The response should be 375-495 words, use a warm, professional tone, and be formatted as a single email body without headings. Ensure the language is clear, avoids jargon, and includes a brief call-to-action inviting the customer to reply if anything remains unclear. Quality criteria: 1. Shows genuine empathy and takes responsibility. 2. Provides accurate, concise correction and actionable next steps. 3. Ends with a friendly invitation for further assistance. If any of the placeholders above are unknown, state your assumption and ask up to three clarifying questions before finalizing the reply. Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader.
A reply after a data incident 76
You are a customer-support specialist drafting a concise, empathetic response to a user whose data was impacted by an incident. Your reply should: 1. Acknowledge the situation clearly and express sincere regret for any inconvenience caused. 2. Show that you understand the user’s concerns by briefly summarizing the incident’s effect on their data and confirming you have reviewed the details. 3. Outline the specific actions you are taking to resolve the issue, including any immediate safeguards and the timeline for full restoration. 4. Explain how you will verify that the problem is fully resolved and how the user will be informed of the outcome. 5. Invite the user to stay engaged by offering a direct contact for further questions, a reference number, and any additional resources or compensation you are providing. Write the response in a friendly, professional tone, keeping it under 915 words. Ensure the message is clear, avoids technical jargon, and ends with a courteous call-to-action. [RECIPIENT_NAME]: the name of the person you are addressing [INCIDENT_DESCRIPTION]: brief description of the data incident [RESOLUTION_STEPS]: specific actions you will take to fix the issue [VERIFICATION_METHOD]: how you will confirm the issue is resolved [CONTACT_INFO]: email or phone number for follow-up, plus reference number Write this for [AUDIENCE: who will read the output, and how much they already know]. Match the depth, vocabulary and examples to that reader. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue - do not ask for it and stop.
A complaint about a price increase 87
You are a customer-success specialist drafting a concise response to a client who is upset about a recent price increase. Your task is to write a single reply that: 1. Acknowledges the client’s concern and shows empathy. 2. Summarizes the reason for the price change in clear, factual terms. 3. Offers a practical solution or compensation (e.g., a discount, extended trial, or alternative plan). 4. Confirms that the client’s issue will be tracked and followed up. 5. Invites the client to continue the conversation or ask further questions. The reply should be addressed to **[CUSTOMER NAME]**, reference **[PRODUCT/SERVICE]**, and be suitable for **[COMMUNICATION CHANNEL]** (e.g., email, chat). Keep the total length between 555-735 words. Quality criteria: - Empathetic tone that validates the customer’s feelings. - Clear, jargon-free explanation of the price adjustment. - Specific, actionable next step that encourages retention. Boundary: Do not include any promotional language unrelated to the price issue or make promises about features not yet released. If any of the placeholders above are unknown, state your assumption and proceed, or ask up to three brief clarifying questions before finalizing the response.
Three failed deliveries 81
You are a customer‑support specialist drafting a response to a client who has experienced three consecutive delivery failures. The response should: - Begin with a sincere apology that acknowledges the inconvenience and frustration caused by the missed deliveries. - Show that you have reviewed the situation by referencing the relevant order details and any prior communications. [ORDER_NUMBER: the specific order identifier] [PRODUCT_DESCRIPTION: brief description of the item(s) ordered] [PREVIOUS_CONTACTS: dates or summaries of earlier interactions, if any] - Offer a clear, concrete solution to resolve the issue, such as a guaranteed delivery date, an expedited shipping option, or a full refund/credit. [PROPOSED_RESOLUTION: the exact remedy you intend to provide] [EXPECTED_DELIVERY_DATE: the new delivery deadline, if applicable] - Include a verification step that lets the customer confirm the proposed plan or suggest an alternative, and provide a direct contact method for immediate assistance. [CONTACT_METHOD: phone number, email, or chat link for the support team] - End with an invitation to stay engaged, expressing appreciation for the customer’s patience and encouraging future interaction. Write the reply in a friendly, professional tone, keeping the total length between 150 and 250 words. Ensure the message is clear, concise, and free of jargon, and that it directly addresses the customer’s experience while outlining the next steps. Do not mention any frameworks or internal processes. If any bracketed detail above is left unfilled, choose a sensible value from the context, state that assumption in one line before you begin, and continue — do not ask for it and stop.
A retention reply to a cancelling subscriber 87
You are a customer-success specialist crafting a persuasive retention email for a subscriber who has decided to cancel. The email should: - Acknowledge the subscriber’s current situation and any expressed concerns. - Show that you understand their specific reasons for leaving and the impact on their experience. - Offer a clear, tailored solution or incentive that addresses those concerns and adds value. - Confirm that the proposed solution meets their needs and invite them to confirm acceptance. - Encourage continued engagement by highlighting next steps, support resources, or a personal follow-up. Write the email in a warm, professional tone, using the subscriber’s name and referencing the service they are canceling. Keep the total length between 340-450 words. **Quality criteria**: 1. Empathy-driven opening that reflects the subscriber’s stated issue. 2. Concrete, relevant offer or action that directly resolves the issue. 3. Clear call-to-action inviting a response and outlining next steps. **Boundary**: Do not mention pricing details beyond the offered incentive, and avoid any language that could be interpreted as a guarantee of future performance. If any key details are missing, state your assumptions and ask up to three clarifying questions (e.g., subscriber’s name, product name, reason for cancellation, preferred incentive).
Scores range from 74 to 95. They are shown as generated rather than cherry-picked — a library where every entry scores in the nineties tells you it was curated, not measured.
CURVE vs the Alternatives
For the public version of the same event. TAG writes the outage notice everyone sees; CURVE writes the reply to the individual whose invoices were wrong.
The internal write-up of the same incident. PAR explains to colleagues how it was fixed; CURVE explains to the customer that it was.
For a customer story afterwards — and only with permission. CURVE handles the moment; BAB tells it later, if it becomes a story worth telling.
What to reach for when the reply has compliance implications — a data incident, a regulated product. PACT has an explicit slot for the things you may not say.
For the phone version. If you are calling rather than writing, PREP handles ninety seconds better than five written stages.
Five Ways People Get CURVE Wrong
The defining CURVE failure. It is the phrase the customer has already received, it delays the thing they want to see, and on a repeat contact it reads as a form letter. Open with the specific failure instead.
If a previous reply said it was fixed and it was not, that is the thing they are angriest about and the thing they expect you to skip. Naming it unprompted is the strongest single move in the reply.
After a broken promise, another promise is worth nothing. Give them something to look at — the cancelled subscription in their account, the reference number, the date the charge will not fall.
"We are processing a refund" produces a fifth message. An amount, a date and an expected arrival window does not.
Offering credit in place of the refund reads as buying the complaint off, and to a customer who is owed money it is worse than nothing.
You do not know that, and a customer who has heard a confident claim from you before will notice. Describe what changed, not what is now impossible.
CURVE Questions
What does CURVE stand for?
Challenge, Understand, Resolve, Verify, Engage — five stages for a support or complaint reply where something has genuinely gone wrong.
Why does Challenge come before Understand?
Because leading with empathy delays the thing the customer wants, and to someone who has explained the problem three times it reads as another script. Naming the specific failure first is what makes the empathy that follows credible.
What is the Verify stage for?
Giving the customer a way to confirm the fix themselves. It matters most after a previous reply claimed the problem was resolved and it was not — at that point another assurance from you is worth nothing.
Should I mention that we told them it was fixed before?
Yes, in the first two sentences. It is what they are most angry about and what they expect you to avoid. Raising it unprompted does more to repair the relationship than the refund.
Can I offer a discount instead of a refund?
Not in place of one. Credit offered instead of money owed reads as buying off the complaint, and to a customer who is right it makes things worse.
How long should a CURVE reply be?
Short — around 200 to 250 words for most cases. An angry customer on their fourth message wants the facts, the amount and the date, not five paragraphs of care.
Generate a CURVE Prompt Instantly
Skip the manual template — Frompting applies CURVE to your topic in one click.
Try it FreeFramework Details
| Name | CURVE |
| Stands for | Challenge-Understand-Resolve-Verify-Engage |
| Domain | Communication & Storytelling |
| Steps | 5 |
| Access | Pro |