These prompts generate complete escalation responses you can send immediately. Each produces a professional, empathetic response tailored to your specific situation and customer.
These prompts pair well with Jasper AI for Customer Service-specific tone control, or Copy.ai for fast iteration.
De-escalation Phone Call Scripts
You are a customer service representative handling an escalated phone call from an angry customer.
Customer: {customer_name} Issue: {specific_problem_description} Customer’s emotional state: {furious / frustrated / disappointed / betrayed} Previous interactions: {number_of_previous_contacts} What went wrong: {root_cause_of_issue} Resolution you can offer: {specific_solution_available} Timeline for fix: {immediate / 24_hours / 3_business_days / 1_week} Customer’s priority concern: {money / time / principle / future_service}
Write a 300 to 400 word phone script using the HEART method (Halt, Empathize, Apologize, Respond, Thank). Start with immediate acknowledgment of their frustration. Use their name at least twice. Include specific steps and timeline. End with a commitment statement and next contact point.
When to use it: When you have an angry customer on hold and need to structure your response before picking up the call.
Pro tip: Read the script out loud before the call. If you stumble over any phrases, simplify them - you need words that flow naturally under pressure.
You are handling a call from a customer whose issue has been escalated three times without resolution.
Customer: {customer_name} Original issue date: {date_issue_started} Previous agents contacted: {agent_names_or_departments} Promises made but not kept: {specific_commitments_broken} Customer’s relationship with company: {new_customer / long_term_loyal / business_account / individual} What they’re threatening: {cancel_service / legal_action / public_complaints / chargeback} Your authority level: {can_offer_refunds / need_supervisor_approval / limited_options}
Write a 250 to 350 word call script that takes complete ownership without throwing previous agents under the bus. Acknowledge each broken promise specifically. Provide a concrete action plan with accountability measures. Include your direct contact information and escalation path if this solution fails.
When to use it: When you’re the fourth person to touch a case and the customer has lost all faith in your process.
Pro tip: Never say “I’m sorry you feel that way.” Always say “I’m sorry this happened to you.” The difference matters to upset customers.
You are de-escalating a customer who received a defective product and is demanding an immediate supervisor.
Customer: {customer_name} Product: {product_name_and_model} Defect description: {what_is_wrong} Purchase date: {when_they_bought_it} Impact on customer: {ruined_event / business_disruption / safety_concern / financial_loss} Replacement availability: {in_stock / backordered / discontinued} Customer’s demand: {full_refund / free_replacement / compensation / escalation} Supervisor availability: {available_now / available_in_30_min / not_until_tomorrow}
Write a 200 to 300 word script to handle this before transferring to a supervisor. Validate their request for escalation while positioning yourself as someone who can help immediately. Address the defect impact directly. Offer a preliminary solution while confirming supervisor transfer. Set expectations for the supervisor conversation.
When to use it: When a customer demands a supervisor but you want to try resolving it first, or when your supervisor isn’t immediately available.
Pro tip: Always confirm you’re transferring them to a supervisor, not just “someone else.” Customers who ask for supervisors have usually been transferred multiple times already.
You are handling a billing dispute where the customer is correct and your company made an error.
Customer: {customer_name} Billing error: {incorrect_charge_description} Amount in dispute: {dollar_amount} When error occurred: {billing_cycle_or_date} Customer’s discovery method: {how_they_found_the_error} Time spent resolving: {hours_on_phone / emails_sent} Additional fees caused: {overdraft / late_fees / interest} Customer’s tone: {controlled_anger / exhausted / demanding_justice} Refund timeline: {immediate / next_billing_cycle / 5_business_days}
Write a 350 to 450 word script that leads with complete accountability. Explain exactly what happened without technical jargon. Detail every step of the correction process. Address additional fees they incurred. Include a gesture of goodwill beyond just fixing the error. Provide written confirmation details.
When to use it: When your system flagged a billing error or a customer caught a mistake that’s clearly on your end.
Pro tip: Give them the written confirmation details (email address, reference number, timeline) before you hang up. Customers trust the process more when they can track it independently.
You are calming a customer whose service was interrupted during a critical business moment.
Customer: {customer_name} Business type: {restaurant / medical_office / retail_store / home_office} Service interrupted: {internet / phone / payment_processing / security_system} Critical event affected: {customer_meeting / sales_transaction / medical_appointment / family_emergency} Outage duration: {minutes_or_hours} Business impact: {lost_revenue / missed_opportunities / reputation_damage} Cause of outage: {equipment_failure / planned_maintenance / external_issue} Current service status: {restored / partial / still_down} Prevention measures: {backup_systems / monitoring_upgrades / redundancy}
Write a 300 to 400 word script acknowledging the business impact first, then personal frustration. Explain the cause without making excuses. Detail what you’re doing to prevent recurrence. Offer business continuity support for the immediate term. Include escalation to business account management if appropriate.
When to use it: When service interruption has cost a business customer money or damaged their reputation with their own customers.
Pro tip: Ask about their immediate business needs first, then address billing adjustments. A restaurant that lost payment processing during dinner rush cares more about tomorrow night’s backup plan than this month’s credit.
Written Apology Letters
You are writing a formal apology letter for a service failure that affected multiple customers.
Customer: {customer_name} Service failure: {what_went_wrong} Date of incident: {when_it_happened} Duration of impact: {how_long_customers_were_affected} Number of customers impacted: {scope_of_the_problem} Root cause: {technical_failure / human_error / system_update / external_vendor} Customer’s specific impact: {missed_calls / data_loss / service_interruption / billing_issues} Remediation completed: {what_you_have_fixed} Compensation offered: {service_credits / refunds / free_months / upgrades}
Write a 400 to 500 word formal apology letter. Start with a clear apology statement. Explain what happened in plain language. Take full responsibility without deflecting to vendors or technical issues. Detail specific prevention measures. Close with personal contact information and commitment to individual follow-up.
When to use it: When you need to send a written apology that may be forwarded to executives or used in legal discussions.
Pro tip: Include your direct phone number and email, not the general customer service line. Customers receiving formal apologies expect direct access to someone accountable.
You are writing an apology email for a customer who received poor service from a specific team member.
Customer: {customer_name} Team member involved: {agent_name_or_department} Poor service description: {rude_behavior / incorrect_information / long_wait / dismissive_attitude} Date of interaction: {when_it_happened} Customer’s emotional response: {angry / hurt / disappointed / frustrated} What customer was trying to accomplish: {original_request_or_need} Service standard violated: {response_time / courtesy / accuracy / follow_through} Corrective action taken: {additional_training / coaching / process_change} Resolution for original issue: {how_you_fixed_their_actual_problem}
Write a 250 to 350 word apology email that addresses the service failure without discussing personnel details. Focus on the experience they deserved versus what they received. Confirm resolution of their original issue. Include assurance about service standards and monitoring. Provide direct contact for future concerns.
When to use it: When a customer complains about how they were treated by your team, not just the outcome of their request.
Pro tip: Never mention specific disciplinary actions taken with staff. Instead, focus on “service standards” and “additional training to ensure this doesn’t happen again.”
You are writing an apology for a shipping or delivery failure that ruined a special occasion.
Customer: {customer_name} Special occasion: {birthday / wedding / anniversary / holiday / business_event} Item ordered: {gift / decorations / equipment / clothing} Delivery promise date: {when_it_should_have_arrived} Actual delivery status: {delayed / lost / damaged / wrong_address} Shipping method: {standard / expedited / overnight / same_day} Occasion date: {when_they_needed_it} Replacement options: {can_rush_replacement / item_out_of_stock / event_already_passed} Customer’s disappointment level: {mild_inconvenience / major_embarrassment / relationship_impact}
Write a 300 to 400 word apology email that acknowledges the emotional impact, not just the logistical failure. Recognize what the occasion meant to them. Take responsibility for the delivery promise. Explain immediate next steps for resolution. Include meaningful compensation that acknowledges the non-monetary loss.
When to use it: When your delivery failure affected a once-in-a-lifetime event or important personal milestone.
Pro tip: Acknowledge that some things can’t be undone. “We know we can’t give you back your daughter’s graduation day” hits differently than “We apologize for the inconvenience.”
You are writing an apology for a data privacy or security incident that affected customer information.
Customer: {customer_name} Incident type: {data_breach / unauthorized_access / information_leak / system_compromise} Date discovered: {when_you_found_out} Customer data affected: {personal_info / payment_data / account_details / communications} Extent of exposure: {internal_only / external_access / potential_misuse} Immediate actions taken: {system_shutdown / password_resets / security_patches} Law enforcement involvement: {reported / investigating / no_criminal_activity} Monitoring services: {credit_monitoring / identity_protection / account_alerts} Legal requirements: {regulatory_notification / compliance_reporting}
Write a 450 to 550 word formal security incident notification. Lead with clear statement of what happened. Specify exactly what customer data was involved. Explain timeline of discovery and response. Detail protective services being provided. Include specific steps customer should take. Close with ongoing security improvements and direct contact information.
When to use it: When you’re legally required to notify customers about a security incident or when a customer specifically asks about their data exposure.
Pro tip: Be specific about what data was NOT accessed if that’s relevant. “Your payment card numbers and social security numbers were not involved” provides important reassurance.
You are writing an apology for a product recall that affects customer safety.
Customer: {customer_name} Product recalled: {specific_product_and_model} Safety issue: {fire_hazard / injury_risk / toxic_exposure / malfunction} Recall date announced: {official_recall_date} Customer purchase date: {when_they_bought_it} Incidents reported: {number_of_injuries / complaints / failures} Immediate action required: {stop_using / return_product / contact_service / dispose_safely} Return process: {mail_back / drop_off_location / pickup_service} Refund timeline: {immediate / upon_receipt / next_billing_cycle} Replacement availability: {improved_version_available / different_model / full_refund_only}
Write a 350 to 450 word recall notification that prioritizes safety over company liability. Lead with clear safety instruction. Explain the risk in plain language without legal hedging. Provide step-by-step return instructions with prepaid shipping. Include recall hotline and reference numbers. Close with commitment to safety and quality improvements.
When to use it: When sending individual recall notifications or responding to customers who ask about recalled products they own.
Pro tip: Put the safety instruction in the first sentence and repeat it in the closing. Don’t bury “stop using immediately” in the middle of a paragraph.
Complaint Resolution Follow-ups
You are following up one week after resolving a major customer complaint to ensure satisfaction.
Customer: {customer_name} Original complaint: {what_they_complained_about} Resolution provided: {how_you_fixed_it} Timeline promised: {when_you_said_it_would_be_done} Compensation given: {refund / credit / free_service / upgrade} Internal changes made: {process_improvements / training / system_updates} Customer’s satisfaction at resolution: {pleased / cautiously_optimistic / still_frustrated} Follow-up method: {email / phone / text / postal_mail} Relationship status: {long_term_customer / new_customer / considering_leaving}
Write a 200 to 300 word follow-up message that checks on both the resolution outcome and their overall experience. Ask specific questions about whether the fix is working. Acknowledge their patience during the resolution process. Include direct contact information for any remaining concerns. Close with appreciation for their feedback that led to improvements.
When to use it: Seven to ten days after you’ve implemented a solution to a complex customer problem.
Pro tip: Ask about the solution’s effectiveness, not just their satisfaction. “Is the new system working properly?” gets better feedback than “Are you happy with our service?”
You are following up with a customer who threatened to cancel their account after a service failure.
Customer: {customer_name} Threat made: {cancel_service / switch_providers / file_complaint / legal_action} Service failure: {what_went_wrong} Resolution timeline: {how_long_fix_took} Retention offer made: {discount / upgrade / extended_warranty / bonus_features} Customer value: {monthly_revenue / years_as_customer / referral_source} Decision deadline: {when_they_said_they_would_decide} Competitive pressure: {specific_competitor / general_market / price_shopping} Relationship repair needed: {trust_rebuilding / service_proving / value_demonstration}
Write a 250 to 350 word retention follow-up that focuses on relationship repair over sales pressure. Acknowledge their consideration of alternatives as reasonable given what happened. Highlight specific improvements made since their issue. Invite feedback on what would rebuild their confidence. Include metrics or commitments about future service levels.
When to use it: When following up with a valued customer who gave you “one more chance” after a major service failure.
Pro tip: Don’t ask “What can we do to keep your business?” Instead ask “What would need to change for you to feel confident in our service again?” It shifts from transactional to relationship-focused.
You are sending a resolution summary to a customer whose complaint required escalation to multiple departments.
Customer: {customer_name} Departments involved: {technical / billing / management / legal / product_team} Resolution timeline: {total_days_to_resolve} Final outcome: {full_resolution / partial_resolution / ongoing_monitoring} Root cause identified: {system_bug / process_gap / training_issue / policy_conflict} Preventive measures: {what_you_changed_to_prevent_recurrence} Customer effort required: {phone_calls_made / emails_sent / documentation_provided} Compensation rationale: {service_credits / refunds / free_services / priority_support} Ongoing relationship: {account_monitoring / dedicated_contact / service_upgrades}
Write a 400 to 500 word comprehensive resolution summary. Acknowledge the complexity and their persistence. Summarize each department’s role and findings. Detail the permanent fixes implemented. Thank them specifically for their patience and feedback. Include ongoing support structure and escalation paths for any future issues.
When to use it: When closing a complex case that took multiple departments and several weeks to resolve completely.
Pro tip: Include a timeline graphic or bulleted chronology. Complex resolutions feel more complete when customers can see the full scope of work done on their behalf.
You are updating a customer on the status of a complaint that requires vendor coordination to resolve.
Customer: {customer_name} Issue requiring vendor: {third_party_integration / equipment_replacement / service_restoration} Vendor involved: {vendor_name_or_type} Customer’s original deadline: {when_they_needed_resolution} Vendor timeline: {realistic_completion_date} Delays encountered: {vendor_responsiveness / parts_availability / technical_complexity} Workaround offered: {temporary_solution_available} Escalation actions: {vendor_management_involved / contract_enforcement / alternative_vendors} Communication frequency: {daily_updates / weekly_check_ins / milestone_reporting}
Write a 300 to 400 word status update that manages expectations without making excuses. Explain your role versus the vendor’s role clearly. Detail specific pressure being applied to the vendor. Offer interim solutions or alternatives. Provide next update timeline and escalation triggers. Include direct contact for urgent concerns while vendor work continues.
When to use it: When you’re dependent on a third-party vendor to resolve a customer’s issue and the timeline is slipping.
Pro tip: Give them your vendor’s contact information if appropriate. Sometimes customers get better results when they can apply direct pressure themselves.
You are confirming completion of service restoration after an extended outage affected a business customer.
Customer: {customer_name} Service restored: {internet / phone / payment_processing / cloud_access} Outage duration: {total_hours_down} Business impact: {revenue_lost / customers_affected / operations_disrupted} Root cause: {equipment_failure / software_bug / external_provider_issue} Repair actions: {equipment_replacement / software_patches / configuration_changes} Testing completed: {performance_verification / stress_testing / backup_systems} Monitoring enhanced: {additional_alerts / proactive_checks / redundancy_added} Service credits: {automatic_credits / billing_adjustments / free_service_period}
Write a 350 to 450 word service restoration confirmation that includes business continuity assurance. Confirm full functionality and performance levels. Detail the testing performed before declaring restoration complete. Explain new monitoring and redundancy measures. Address billing adjustments automatically applied. Include emergency escalation procedures for any future issues.
When to use it: When confirming that service is fully restored after a significant business disruption, especially for customers who depend on your service for their operations.
Pro tip: Include specific metrics about restored performance (“speeds tested at 99.8% of normal”) rather than just “everything is working fine.” Business customers need data to trust the restoration.
Executive Escalation Responses
You are responding as a department director to a customer complaint that reached executive level.
Customer: {customer_name} How complaint reached executives: {CEO_email / board_member_contact / social_media / news_coverage} Original issue: {service_failure_description} Previous resolution attempts: {number_of_contacts / departments_involved} Resolution failures: {what_your_team_got_wrong} Customer’s executive contact: {CEO / board_member / investor / media_contact} Public exposure risk: {social_media_posts / news_inquiry / industry_reputation} Systemic issue: {affects_other_customers / process_breakdown / training_gap} Authority level: {unlimited_resolution_power / budget_constraints / policy_exceptions}
Write a 450 to 550 word executive-level response that takes complete organizational accountability. Address the systemic issues, not just this customer’s problem. Detail leadership changes or process overhauls being implemented. Include personal commitment to oversight and follow-up. Provide direct executive contact information and regular update schedule.
When to use it: When a customer complaint has reached your CEO, board members, or created public relations exposure.
Pro tip: Write like you’re addressing both the customer and the executive who forwarded it. Your CEO needs to see you taking complete ownership while the customer needs to see meaningful change.
You are responding as a senior manager to a complaint about discriminatory treatment by your staff.
Customer: {customer_name} Discrimination type: {racial / gender / age / disability / religious} Staff member involved: {agent_name_or_department} Specific incident: {what_happened_exactly} Witness information: {other_customers / staff_present} Customer’s documentation: {recordings / screenshots / written_complaints} Legal implications: {potential_lawsuit / regulatory_complaint / civil_rights_violation} Previous similar incidents: {pattern_of_behavior / isolated_incident} Immediate actions taken: {staff_suspension / investigation_started / training_scheduled} Policy review needed: {hiring / training / customer_service_standards}
Write a 500 to 600 word response that demonstrates zero tolerance for discrimination. Acknowledge the seriousness without admitting legal liability. Detail immediate investigation and corrective actions. Explain company values and diversity commitments. Include specific steps to prevent recurrence. Provide direct executive contact and external reporting options if they choose.
When to use it: When responding to any complaint involving discriminatory treatment, bias, or civil rights concerns.
Pro tip: Have this reviewed by legal counsel before sending. Discrimination complaints require careful language that shows seriousness without creating additional legal exposure.
You are responding as a VP to a customer whose safety complaint was initially dismissed by frontline staff.
Customer: {customer_name} Safety concern: {product_defect / facility_hazard / service_risk} Initial staff response: {dismissed_concern / minimized_risk / delayed_action} Actual safety risk: {injury_potential / property_damage / regulatory_violation} Investigation findings: {confirmed_hazard / design_flaw / maintenance_failure} Other customers affected: {number_potentially_at_risk} Regulatory involvement: {OSHA / FDA / state_agency} Corrective actions: {immediate_fixes / product_changes / facility_improvements} Staff training needed: {safety_protocols / escalation_procedures / risk_assessment}
Write a 400 to 500 word executive safety response that prioritizes public safety over company liability. Thank them for reporting the concern despite initial dismissal. Detail immediate safety measures implemented. Explain staff retraining on safety escalation. Include commitment to safety culture and reporting improvements. Provide direct safety hotline and regulatory contact information.
When to use it: When a safety concern was mishandled by frontline staff and reached executive attention.
Pro tip: Copy relevant safety regulators if appropriate. Showing transparency with regulatory bodies demonstrates genuine commitment to safety over damage control.
You are responding as a company officer to a complaint about fraudulent charges handled poorly by multiple departments.
Customer: {customer_name} Fraudulent activity: {unauthorized_charges / account_takeover / identity_theft} Amount involved: {dollar_amount} Detection method: {customer_reported / system_flagged / bank_notification} Resolution delays: {investigation_time / documentation_requirements / interdepartment_coordination} Customer financial impact: {overdraft_fees / credit_damage / frozen_accounts} Departments involved: {fraud_team / billing