Copy-paste prompts for customer service reps who need professional complaint resolution emails written in 30 seconds. Fill in the variables, hit enter, get a polished response you can send immediately.
These prompts pair well with Jasper AI for Customer Service-specific tone control, or Copy.ai for fast iteration.
Product Defect and Quality Issues
You are a customer service representative responding to a product quality complaint.
Customer: {customer_name} Product: {product_name} Purchase date: {purchase_date} Issue described: {defect_description} Customer tone: {angry / disappointed / frustrated / polite} Resolution offered: {replacement / refund / store_credit / repair} Timeline: {immediate / 3_days / 1_week / 2_weeks}
Write a 200 to 280 word email response that acknowledges the specific defect, takes ownership without admitting legal fault, explains the resolution process step-by-step, and includes a gesture of goodwill. Use an empathetic but professional tone.
When to use it: When a customer reports a broken, damaged, or defective product and you need to offer a standard resolution.
Pro tip: If the customer mentions safety concerns, escalate to management instead of using this prompt—safety issues require legal review.
You are handling a complaint about a product that stopped working after the warranty expired.
Customer: {customer_name} Product: {product_name} Warranty expired: {expiration_date} Issue: {malfunction_description} Customer request: {repair / replacement / refund / discount_on_new} Company policy: {strict_warranty / case_by_case / goodwill_available} Customer history: {loyal / new / previous_complaints}
Write a 250 to 320 word email that explains warranty limitations while exploring available options. Reference their customer history positively. Offer at least one concrete next step even if you can’t grant their exact request.
When to use it: When customers want warranty coverage after expiration and you need to balance policy with retention.
Pro tip: Always mention specific dates rather than saying “recently expired”—it shows you’ve reviewed their account carefully.
You’re responding to a customer who received the wrong product variant.
Customer: {customer_name} Ordered: {correct_product_details} Received: {wrong_product_details} Order number: {order_number} Shipping address: {full_address} Customer urgency: {needed_by_specific_date / not_urgent / gift_occasion} Return method: {prepaid_label / store_return / pickup_service}
Write a 180 to 240 word email that apologizes for the fulfillment error, explains the exchange process, provides a prepaid return solution, and gives a realistic timeline for receiving the correct item. Include order tracking information.
When to use it: When warehouse fulfillment errors result in customers receiving incorrect product variations or sizes.
Pro tip: If it’s a gift with a deadline, mention expedited shipping options upfront—don’t make them ask twice.
You’re handling a complaint about poor product quality that doesn’t match advertised standards.
Customer: {customer_name} Product: {product_name} Quality expectation: {what_was_advertised} Actual quality: {customer_description_of_reality} Price paid: {dollar_amount} Evidence provided: {photos / video / none} Preferred outcome: {refund / exchange / store_credit}
Write a 220 to 300 word email that validates their quality concerns, explains how this doesn’t meet company standards, offers their preferred resolution, and mentions steps being taken to prevent similar issues. Avoid defensive language about marketing claims.
When to use it: When products are functional but fall short of quality expectations set by marketing or packaging.
Pro tip: If they provided photos, reference specific details from their images to prove you actually looked at their evidence.
You’re responding to a batch quality complaint where multiple customers reported the same issue.
Product affected: {product_name} Batch identifier: {lot_number_or_date_range} Common issue: {shared_problem_description} Customer: {customer_name} Their specific experience: {their_version_of_issue} Company response: {recall / voluntary_exchange / investigation_ongoing} Timeline: {immediate / days / weeks} Communication plan: {email_updates / phone_call / text_alerts}
Write a 280 to 360 word email that acknowledges the batch issue, explains what caused it, details the company’s proactive response, offers resolution for their specific situation, and outlines how they’ll be kept informed of progress.
When to use it: When you’ve identified a pattern of complaints about products from the same production run or time period.
Pro tip: Lead with the batch information so they know you’re aware this isn’t an isolated incident—it builds confidence in your investigation.
Shipping and Delivery Problems
You’re responding to a complaint about a late delivery that missed an important deadline.
Customer: {customer_name} Order number: {order_number} Original delivery date: {promised_date} Actual delivery date: {actual_or_estimated_date} Missed occasion: {birthday / anniversary / holiday / business_meeting} Shipping carrier: {carrier_name} Cause of delay: {weather / carrier_issue / warehouse_delay / address_problem} Compensation offered: {shipping_refund / discount / store_credit / expedited_future_shipping}
Write a 200 to 270 word email that acknowledges the disappointment of missing their important date, explains what happened without throwing the carrier under the bus, offers meaningful compensation, and provides assurance for future orders.
When to use it: When delivery delays ruin special occasions or time-sensitive needs.
Pro tip: Don’t just refund shipping costs for missed birthdays or holidays—the emotional impact is higher, so offer additional compensation.
You’re handling a complaint about a package marked delivered but never received.
Customer: {customer_name} Order number: {order_number} Delivery confirmation date: {date} Delivery location noted: {doorstep / mailbox / neighbor / office} Customer checked: {neighbors / building_manager / workplace / security_footage} Package value: {dollar_amount} Investigation status: {carrier_investigating / claim_filed / police_report_needed} Next steps: {replacement / refund / wait_for_carrier}
Write a 240 to 320 word email that takes the theft/loss seriously, outlines the investigation process, explains what the customer should do next, provides immediate resolution options, and gives a timeline for final resolution.
When to use it: When tracking shows delivered but the customer never received their package.
Pro tip: If the package value is over $100, mention filing a carrier claim by name—it shows you’re taking financial steps to investigate.
You’re responding to damaged package complaints where shipping caused product damage.
Customer: {customer_name} Order contents: {list_of_items} Packaging damage: {crushed_box / wet_package / torn_open / clearly_dropped} Product damage: {broken / dented / unusable / cosmetic_only} Photos provided: {yes / no / partial} Replacement availability: {in_stock / back_ordered / discontinued} Insurance claim: {required / not_required / pending}
Write a 190 to 260 word email that acknowledges packaging should protect products during shipping, asks for photos if not provided, explains the replacement process, and mentions packaging improvements to prevent future damage.
When to use it: When rough handling during transit results in damaged products inside damaged packaging.
Pro tip: If they mention the box was obviously damaged but they accepted delivery anyway, still honor the claim—customers shouldn’t have to refuse packages to get protection.
You’re handling a complaint about incorrect shipping address delivery due to customer or system error.
Customer: {customer_name} Intended address: {correct_full_address} Delivered to: {wrong_address_if_known} Address error source: {customer_typo / saved_address_outdated / system_glitch / checkout_confusion} Package status: {delivered_elsewhere / returned_to_sender / lost} Replacement cost: {free / discounted / full_price} Shipping cost: {waived / charged / expedited_free}
Write a 210 to 280 word email that handles the address mix-up diplomatically regardless of fault, explains options for locating the package, offers re-shipping terms, and suggests address verification steps for future orders.
When to use it: When packages get delivered to old addresses, typo addresses, or wrong locations due to address confusion.
Pro tip: Even if the customer made the address error, offer to split the re-shipping cost rather than charging full price—it builds goodwill.
You’re responding to complaints about poor packaging that didn’t protect fragile items.
Customer: {customer_name} Items ordered: {fragile_product_list} Packaging used: {bubble_wrap / foam / air_packets / newspaper / box_only} Damage discovered: {completely_broken / chipped / cracked / unusable} Replacement needed: {yes / no / partial} Packaging standards: {met_guidelines / below_standard / new_protocol_needed} Customer expertise: {collector / professional / gift_giver / casual_buyer}
Write a 200 to 290 word email that acknowledges fragile items deserve better protection, explains current packaging standards, offers replacement, and mentions specific packaging improvements for similar future orders.
When to use it: When fragile or valuable items arrive broken due to insufficient protective packaging.
Pro tip: If the customer mentions being a collector or professional, acknowledge their expertise with fragile items—they know good packaging when they see it.
Billing and Payment Disputes
You’re responding to a customer disputing a charge they don’t recognize on their statement.
Customer: {customer_name} Disputed charge: {dollar_amount} Charge date: {transaction_date} Transaction ID: {reference_number} Customer claim: {never_ordered / already_returned / duplicate_charge / wrong_amount} Account history: {shows_order / shows_return / shows_multiple / shows_partial} Resolution: {refund_confirmed / credit_issued / charge_valid / investigating} Timeline: {immediate / 3_business_days / next_billing_cycle}
Write a 220 to 300 word email that explains how to identify the charge, walks through what their account history shows, provides clear resolution steps, and gives timeline expectations for when they’ll see changes on their statement.
When to use it: When customers see charges on their credit card or bank statement they don’t recognize as yours.
Pro tip: Include the exact transaction ID and date in your response—it helps them match your explanation to their statement.
You’re handling a complaint about being charged for a returned item.
Customer: {customer_name} Original order: {order_number} Return date: {when_returned} Return method: {mail / store / pickup} Return reason: {defective / wrong_size / changed_mind / duplicate} Refund status: {processed / pending / missing / partial} Restocking fee: {applied / waived / not_applicable} Current charge showing: {full_amount / partial_amount / fee_only}
Write a 180 to 250 word email that confirms you received their return, explains the refund timeline, addresses any fees that apply, and provides specific next steps if the refund isn’t showing correctly on their account.
When to use it: When customers returned items but still see charges or haven’t received expected refunds.
Pro tip: If the return was processed more than 7 business days ago and they’re not seeing the refund, proactively offer to contact their bank rather than making them wait longer.
You’re responding to a complaint about unauthorized subscription or recurring charges.
Customer: {customer_name} Service: {subscription_name} Billing frequency: {monthly / quarterly / annually} Last intended use: {date_or_never} Cancellation attempt: {tried_online / called / thought_it_was_cancelled / unaware_of_subscription} Charges to dispute: {number_of_billing_cycles} Account status: {active / cancelled / suspended}
Write a 240 to 320 word email that explains how the subscription was set up, acknowledges their cancellation intent, cancels future billing immediately, and offers refund for recent unwanted charges with clear refund timeline.
When to use it: When customers discover they’ve been billed for subscriptions they forgot about, thought they cancelled, or never knowingly signed up for.
Pro tip: Cancel the subscription first, then discuss refunds—they need to know bleeding stops immediately regardless of what you can refund.
You’re handling a complaint about price difference between checkout and final charge.
Customer: {customer_name} Expected total: {checkout_amount} Actual charge: {final_charge_amount} Difference: {dollar_difference} Possible causes: {tax_calculation / shipping_change / promo_code_issue / currency_conversion / authorization_vs_capture} Order details: {what_they_ordered} Shipping method: {standard / expedited / international}
Write a 200 to 280 word email that breaks down each component of their final charge, explains why amounts might differ between checkout and statement, offers to adjust if there was an error, and provides itemized receipt for their records.
When to use it: When the amount on their credit card doesn’t match what they remember seeing at checkout.
Pro tip: Even if the charge is correct, send an itemized breakdown—customers often forget about tax or shipping when comparing amounts.
You’re responding to a complaint about failed payment processing that led to order cancellation.
Customer: {customer_name} Original order: {order_number} Payment method: {credit_card / debit / digital_wallet / bank_transfer} Failure reason: {insufficient_funds / expired_card / bank_decline / processing_error} Customer impact: {missed_sale_price / out_of_stock / needed_by_date} Current availability: {still_available / limited_stock / back_ordered / sale_ended} Reorder process: {simple_retry / new_payment_method / call_required}
Write a 220 to 290 word email that explains why payment failed without embarrassing them, describes current product and pricing status, offers easy reorder options, and provides alternative payment methods if helpful.
When to use it: When payment processing failures result in cancelled orders and disappointed customers.
Pro tip: If they missed a sale price due to payment processing delays on your end, honor the original sale price when they reorder with working payment.
Service Experience and Staff Issues
You’re responding to a complaint about rude or unprofessional treatment from a team member.
Customer: {customer_name} Incident date: {date_of_interaction} Staff member: {name_or_department} Interaction type: {phone / email / chat / in_person} Customer description: {what_happened_in_their_words} Their emotional impact: {frustrated / embarrassed / angry / disappointed} Desired outcome: {apology / staff_training / policy_change / just_want_acknowledgment} Follow_up_needed: {yes / no / management_review}
Write a 250 to 330 word email that acknowledges their experience doesn’t reflect company values, takes responsibility for staff behavior, explains steps being taken to address the situation, and offers to connect them with management if needed.
When to use it: When customers report poor treatment, attitude problems, or unprofessional behavior from your team.
Pro tip: Don’t defend the staff member or ask for “their side”—focus entirely on making the customer feel heard and valued.
You’re handling a complaint about long wait times for customer service response.
Customer: {customer_name} Original contact date: {when_they_first_reached_out} Response time: {actual_days_or_hours} Contact method: {phone / email / chat / social_media} Issue urgency: {time_sensitive / billing_problem / order_deadline / general_question} Staffing situation: {high_volume / system_issues / seasonal_busy / normal_operations} Their frustration level: {annoyed / understanding / very_angry / threatening_to_leave}
Write a 200 to 280 word email that acknowledges wait times are unacceptable, explains what caused the delay without making excuses, prioritizes their current issue, and provides faster contact options for future needs.
When to use it: When customers complain about slow response times from your customer service team.
Pro tip: Give them a direct contact method or reference number for future issues so they don’t get stuck in the same queue again.
You’re responding to a complaint about receiving conflicting information from different team members.
Customer: {customer_name} First interaction: {what_first_rep_said} Second interaction: {what_second_rep_said} Conflicting details: {specific_contradiction} Customer confusion: {what_they_need_clarity_on} Correct information: {actual_policy_or_facts} Previous actions taken: {what_was_already_done_based_on_wrong_info} Resolution needed: {fix_previous_action / clarify_going_forward / both}
Write a 240 to 320 word email that acknowledges how frustrating conflicting information must be, provides the definitive correct answer, explains how the confusion happened, and fixes any problems caused by incorrect previous guidance.
When to use it: When customers get different answers from different reps and don’t know what to believe.
Pro tip: Lead with the correct information before explaining how the confusion happened—they need clarity first, context second.
You’re handling a complaint about a team member who couldn’t resolve their issue and passed them around.
Customer: {customer_name} Original issue: {what_they_needed_help_with} Departments involved: {list_of_teams_they_were_transferred_to} Total time spent: {hours_or_days_trying_to_get_help} Outcome so far: {still_unresolved / partially_resolved / made_worse} Customer effort: {had_to_repeat_story / provided_info_multiple_times / gave_up_and_started_over} Resolution complexity: {simple_fix / requires_coordination / policy_exception_needed}
Write a 260 to 340 word email that apologizes for the runaround, demonstrates you understand their complete situation, provides single-point-of-contact resolution, and ensures they won’t have to repeat their story again.
When to use it: When customers get bounced between departments without getting their issue resolved.
Pro tip: Summarize their complete situation in your response to prove they won’t have to explain everything again to the next person.
You’re responding to a complaint about a team member who made promises that weren’t kept.
Customer: {customer_name} Promise made: {what_rep_committed_to} Promised timeline: {when_it_was_supposed_to_happen} Actual outcome: {what_actually_happened_or_didnt} Customer impact: {how_the_broken_promise_affected_them} Promise feasibility: {was_realistic / impossible / required_approval / policy_violation} Current status: {can_still_be_fulfilled / needs_modification / impossible_to_deliver} Alternative solutions: {what_you_can_actually_do}
Write a 220 to 300 word email that acknowledges promises should be kept, explains why this one wasn’t fulfilled, takes responsibility for the communication breakdown, and offers realistic alternatives that can actually be delivered.
When to use it: When previous reps made commitments that couldn’t be honored and customers are frustrated about unmet expectations.
Pro tip: If the original promise was impossible due to policy, explain the policy clearly so they understand it wasn’t personal—it helps rebuild trust.
Policy and Refund Disputes
You’re responding to a customer who wants a refund outside your normal return window.
Customer: {customer_name} Product: {what_they_want_to_return} Purchase date: {original_order_date} Return policy: {standard_timeframe} Time elapsed: {how_long_theyve_had_it} Reason for delay: {why_they_waited / just_discovered_issue / forgot / been_traveling} Product condition: {unused / lightly_used / heavily_used / defective} Customer history: {loyal / new / previous_returns / high_value}
Write a 200 to 290 word email that explains the return window policy, acknowledges their specific situation, explores available exceptions or alternatives, and provides a clear decision with reasoning they can understand.
When to use it: When customers want to return items after your standard return period has expired.
Pro tip: If they’re a long-term customer, mention their history specifically when explaining why you’re making an exception—it shows the decision is personal, not automatic.
You’re handling a complaint about restocking fees that the customer didn’t expect.
Customer: {customer_name} Items returned: {product_list} Restocking fee: {dollar_amount_or_percentage} Fee policy: {clearly_stated / fine_print / not_mentioned_at_purchase} Return reason: {changed_mind / wrong_size / defective / damaged_in_shipping} Product condition: {unopened / opened_but_unused / used / missing_parts} Customer awareness: {knew_about_fee / surprised_by_fee / disputes_fee_applies}
Write a 180 to 260 word email that explains when restocking fees apply, acknowledges whether this case fits the policy, shows the calculation if the fee is valid, and offers alternatives if the fee seems unfair given their situation.
When to use it: When customers are surprised by or dispute restocking fees on their returns.
Pro tip: If the fee policy wasn’t clearly communicated at purchase, waive it even if you’re technically within policy—customer education failures aren’t the customer’s fault.
You’re responding to a complaint about being denied a price match that the customer expected.
Customer: {customer_name} Product: {item_they_want_price_matched} Competitor price: {lower_price_they_found} Competitor: {where_they_found_lower_price} Price difference: {dollar_amount} Policy restriction: {competitor_not_covered / item_excluded / price_too_old / out_of_stock_elsewhere} Customer expectation: {thought_you_matched_anyone / saw_it_advertised / told_by_previous_rep} Purchase timing: {before_finding_lower_price / after_seeing_competitor}
Write a 220 to 300 word email that explains your price match policy clearly, addresses why their specific request doesn’t qualify, offers alternative solutions like partial credits or future discounts, and maintains goodwill despite the policy limitation.
When to use it: When customers request price matches that don’t meet your policy criteria.
Pro tip: If they’re off by just one day or one policy detail, find a way to meet them halfway—rigid policy enforcement costs more in lost customers than flexibility.
You’re handling a complaint about warranty coverage being denied for damage they claim should be covered.
Customer: {customer_name} Product: {covered_item} Issue: {what_broke_or_failed} Warranty type: {manufacturer / extended / implied} Coverage exclusion: {user_damage