These prompts generate finished customer service responses you can send immediately or edit lightly. Perfect for busy support agents who need professional responses fast without starting from scratch.
These prompts pair well with Jasper AI for Customer Service-specific tone control, or Copy.ai for fast iteration.
Complaint Resolution Responses
You are a customer service representative responding to a product complaint.
Customer name: {customer_name} Product/service: {product_name} Issue: {specific_complaint} Purchase date: {purchase_date} Customer’s emotional state: {frustrated / angry / disappointed / concerned} Resolution offered: {refund / replacement / store_credit / repair} Timeline for resolution: {timeframe}
Write a 150 to 200 word response that acknowledges their frustration, takes ownership without admitting fault, explains the resolution clearly, and includes next steps. Use an empathetic but professional tone. End with a direct action item for the customer.
When to use it: When a customer emails about a defective product or service failure and you need to respond with a solution.
Pro tip: Always include the specific timeline twice - once in the explanation and once in the closing action item to set clear expectations.
You are handling a billing dispute from a long-term customer.
Customer name: {customer_name} Account tenure: {years_as_customer} Disputed charge: {charge_amount_and_description} Billing cycle: {billing_date} Customer’s main concern: {overcharged / unauthorized / service_not_received / pricing_confusion} Account status: {current / past_due / suspended} Resolution: {charge_removal / partial_credit / payment_plan / explanation_only}
Write a 200 to 250 word response using the LAST method (Listen, Apologize, Solve, Thank). Reference their loyalty as a customer. Explain the billing issue clearly with specific numbers. Provide the resolution and confirm what they’ll see on their next statement.
When to use it: When reviewing disputed charges that require both technical explanation and relationship preservation.
Pro tip: Include the exact dollar amounts and dates in your response to eliminate any ambiguity about what’s being adjusted.
You are responding to a customer who received the wrong item in their order.
Customer name: {customer_name} Order number: {order_number} Item ordered: {correct_item} Item received: {wrong_item_received} Order value: {total_order_amount} Shipping address: {shipping_city_state} Customer urgency: {needed_immediately / flexible / gift_deadline} Return method: {prepaid_label / pickup / drop_off}
Write a 180 to 220 word response that apologizes for the mix-up, explains the immediate solution, covers return logistics for the wrong item, and provides tracking information for the correct item shipment. Include an estimated delivery date and a gesture of goodwill.
When to use it: When fulfillment errors require coordinating both returns and new shipments simultaneously.
Pro tip: Send the replacement before requiring the return when the order value is under $50 - it builds trust and reduces friction.
You are addressing a customer complaint about poor service from a specific employee or department.
Customer name: {customer_name} Service location: {store_branch_or_department} Employee involved: {employee_name_or_department} Service issue: {rude_behavior / long_wait / incorrect_information / refused_help} Date of incident: {incident_date} Customer’s desired outcome: {apology / training / disciplinary_action / compensation} Follow-up action: {manager_coaching / process_review / staff_meeting / policy_change}
Write a 200 to 240 word response that validates their experience without criticizing the employee publicly, explains the internal follow-up that will occur, and provides a specific gesture to restore their confidence in your service.
When to use it: When service quality complaints require acknowledgment of internal process failures without throwing staff under the bus.
Pro tip: Never promise specific disciplinary action against employees in writing - focus on process improvements and training instead.
You are responding to a customer whose service appointment was missed or cancelled last minute.
Customer name: {customer_name} Service type: {installation / repair / maintenance / consultation} Original appointment: {date_and_time} Reason for cancellation: {technician_sick / emergency_call / scheduling_error / weather} Customer impact: {took_time_off_work / rearranged_schedule / guests_coming / urgent_repair} Next available slot: {new_appointment_options} Compensation offered: {service_discount / priority_scheduling / rush_fee_waiver}
Write a 160 to 200 word response that acknowledges the inconvenience caused, explains what happened without making excuses, offers priority rescheduling options, and includes compensation for their lost time.
When to use it: When operational failures disrupt customer schedules and require both rescheduling and relationship repair.
Pro tip: Offer multiple reschedule options including early morning or evening slots to show flexibility around their availability.
Refund and Return Responses
You are processing a refund request within the return policy window.
Customer name: {customer_name} Item: {product_name} Purchase date: {purchase_date} Reason for return: {not_as_described / changed_mind / defective / wrong_size} Original payment method: {credit_card / paypal / store_credit} Return condition: {unopened / gently_used / damaged_packaging} Refund amount: {full_amount / partial_amount} Processing time: {3_to_5_days / 7_to_10_days}
Write a 120 to 150 word response confirming the refund approval, explaining the process timeline, and providing any return shipping instructions. Include the exact refund amount and when they’ll see it reflected in their account.
When to use it: When approving straightforward returns that meet all policy requirements.
Pro tip: Include both the business days for processing and the additional bank processing time so customers know exactly when to expect their money.
You are denying a refund request that falls outside your return policy.
Customer name: {customer_name} Item: {product_name} Purchase date: {purchase_date} Policy window: {30_days / 60_days / 90_days} Days since purchase: {actual_days_elapsed} Reason for late return: {forgot / busy / just_decided / found_defect} Alternative offered: {store_credit / exchange / repair / discount_on_future} Policy exception factors: {loyal_customer / expensive_item / special_circumstances}
Write a 180 to 220 word response that explains the policy clearly, shows empathy for their situation, offers the best available alternative, and maintains a helpful tone while upholding company guidelines.
When to use it: When policy prevents a full refund but you want to preserve the customer relationship with alternatives.
Pro tip: Lead with the alternative solution before explaining why the full refund isn’t possible - it softens the “no” and keeps the conversation positive.
You are handling a chargeback dispute where the customer claims non-receipt of goods.
Customer name: {customer_name} Order number: {order_number} Shipping carrier: {ups / fedex / usps / dhl} Tracking number: {tracking_number} Delivery status: {delivered / attempted / in_transit / lost} Delivery address: {confirmed_address} Chargeback amount: {disputed_amount} Evidence available: {signature / photo / gps_coordinates}
Write a 200 to 250 word response that acknowledges their chargeback filing, presents the delivery evidence clearly, explains next steps in the dispute process, and offers resolution options while the dispute is pending.
When to use it: When responding to customers who’ve filed chargebacks for non-receipt while you have delivery confirmation.
Pro tip: Attach delivery photos and GPS coordinates to your response email - visual proof is more convincing than tracking numbers alone.
You are processing a return for a customized or personalized item.
Customer name: {customer_name} Product: {custom_item_description} Customization: {engraving / embroidery / size / color / text} Reason for return: {spelling_error / wrong_size / quality_issue / changed_mind} Error source: {customer_input / production_mistake / measurement_error} Item resalability: {can_resell / cannot_resell / needs_rework} Resolution: {full_refund / partial_refund / remake / exchange}
Write a 170 to 210 word response explaining your custom item policy, determining fault appropriately, and providing a fair resolution based on whether the error was yours or theirs. Include options for fixing vs. refunding.
When to use it: When custom orders don’t meet expectations and you need to determine appropriate remedies based on responsibility.
Pro tip: For customer input errors, offer to remake at 50% cost rather than no refund - it’s fair to both parties and often leads to satisfied customers.
You are explaining a restocking fee on a large or specialized item return.
Customer name: {customer_name} Item: {product_name_and_model} Original price: {purchase_amount} Restocking fee: {fee_percentage_and_amount} Return reason: {changed_mind / ordered_wrong_item / found_cheaper / no_longer_needed} Item condition: {unopened / opened / installed_then_removed} Return processing: {inspection_required / repackaging_needed / testing_required} Final refund: {total_amount_after_fees}
Write a 150 to 190 word response that explains why restocking fees exist for this product category, breaks down the fee calculation clearly, and provides the net refund amount. Maintain a helpful tone while educating about the policy.
When to use it: When processing returns on large appliances, electronics, or B2B items that incur real costs to restock.
Pro tip: Explain the behind-the-scenes work (inspection, repackaging, testing) that justifies the fee rather than just citing policy - it reduces pushback.
Technical Support Responses
You are providing step-by-step troubleshooting for a common technical issue.
Customer name: {customer_name} Product: {software_or_device_name} Issue: {specific_problem_description} Error message: {exact_error_text} Operating system: {windows / mac / ios / android} When issue occurs: {startup / during_use / specific_action / randomly} Attempted solutions: {what_customer_tried_already} Urgency level: {blocking_work / inconvenient / minor_annoyance}
Write a 250 to 300 word response with 5-7 numbered troubleshooting steps in order of likelihood to solve the issue. Include what to expect after each step and when to move to the next. End with escalation instructions if steps don’t work.
When to use it: When customers report technical problems that have standard resolution procedures.
Pro tip: Number your steps and ask customers to reply with how far they got - it makes follow-up much more efficient than starting over.
You are escalating a technical issue to the next support tier.
Customer name: {customer_name} Ticket number: {support_ticket_id} Product: {product_name_version} Issue: {detailed_problem_description} Troubleshooting completed: {steps_already_tried} Customer expertise: {beginner / intermediate / advanced / IT_professional} Business impact: {critical / high / medium / low} Escalation reason: {beyond_tier1 / needs_specialist / requires_dev_team / hardware_replacement}
Write a 180 to 220 word response explaining that you’re escalating their case, what the next tier will do differently, expected response time, and how they’ll be contacted. Set appropriate expectations for resolution timeline.
When to use it: When first-level troubleshooting fails and the customer needs specialized technical expertise.
Pro tip: Explain what information you’re passing to the specialist so customers don’t have to repeat their story from scratch.
You are explaining a known bug or system limitation that affects the customer.
Customer name: {customer_name} Affected feature: {specific_functionality} Bug description: {what_currently_happens} Expected behavior: {what_should_happen} Workaround available: {temporary_solution_or_none} Bug ticket number: {internal_reference} Fix timeline: {next_update / next_quarter / under_investigation} Customer impact: {minor_inconvenience / workflow_disruption / major_blocker}
Write a 200 to 240 word response that acknowledges this is a known issue, explains the current workaround if available, provides realistic timeline expectations for a fix, and offers any compensation appropriate to the impact level.
When to use it: When customers encounter documented bugs that don’t have immediate fixes available.
Pro tip: Always provide the internal bug reference number so customers can reference it in future communications and track progress.
You are helping a customer with account access or password recovery issues.
Customer name: {customer_name} Account email: {registered_email} Issue type: {forgot_password / locked_account / email_changed / two_factor_issues} Security verification: {can_answer_questions / has_backup_codes / alternate_email / phone_verified} Account type: {free / paid / business / enterprise} Urgency: {needs_immediate_access / can_wait / just_convenient} Recovery method: {email_reset / phone_verification / security_questions / admin_unlock}
Write a 160 to 200 word response that guides them through account recovery, explains security verification requirements, provides clear next steps, and includes prevention tips for avoiding future lockouts.
When to use it: When customers can’t access their accounts and need guided recovery assistance.
Pro tip: Send recovery instructions to both their registered email and alternate contact method when possible - accounts get compromised sometimes.
You are explaining why a requested feature isn’t available and suggesting alternatives.
Customer name: {customer_name} Requested feature: {specific_functionality_wanted} Use case: {what_they_want_to_accomplish} Current limitations: {why_feature_doesnt_exist} Alternative solutions: {workarounds_or_different_approaches} Similar features: {related_functionality_that_exists} Feature request status: {logged_for_consideration / planned / not_planned} Timeline: {roadmap_quarter_or_unknown}
Write a 190 to 230 word response that validates their need, explains current limitations honestly, offers the best available alternatives, and indicates whether the feature might be developed in the future.
When to use it: When customers ask for functionality that doesn’t exist but you can suggest viable workarounds.
Pro tip: Focus on what they’re trying to accomplish rather than the specific feature they requested - often there are better alternative approaches.
Order Status and Shipping Updates
You are providing tracking information for a delayed shipment.
Customer name: {customer_name} Order number: {order_number} Original ship date: {promised_date} Actual ship date: {revised_date} Delay reason: {weather / carrier_issues / inventory / processing_backlog} Current location: {tracking_status} New delivery estimate: {updated_delivery_date} Shipping carrier: {ups / fedex / usps} Tracking number: {tracking_number}
Write a 140 to 180 word response explaining the delay cause, providing current tracking status, giving a realistic new delivery estimate, and including any compensation for the inconvenience.
When to use it: When shipments are running behind schedule and customers need proactive updates.
Pro tip: Give a delivery window (Tuesday-Thursday) rather than a specific date when delays are involved - it prevents repeated disappointment.
You are handling a lost package claim with the shipping carrier.
Customer name: {customer_name} Order number: {order_number} Tracking number: {tracking_number} Last tracking update: {final_scan_location} Days since last scan: {number_of_days} Package value: {insured_amount} Contents: {general_description} Carrier investigation: {filed / pending / completed} Resolution: {replacement_sent / refund_issued / still_investigating}
Write a 180 to 220 word response explaining the carrier investigation process, what you’re doing to resolve the issue, timeline for resolution, and immediate action you’re taking (replacement or refund) while the investigation continues.
When to use it: When packages show as delivered but customers didn’t receive them, or tracking stops updating en route.
Pro tip: File carrier claims immediately but send replacements for orders under $100 without waiting - the cost of investigation often exceeds the item value.
You are coordinating a delivery to a business address with specific requirements.
Customer name: {customer_name} Business name: {company_name} Delivery requirements: {dock_access / appointment_needed / signature_required / lift_gate} Package size: {dimensions_and_weight} Preferred delivery window: {time_preference} Contact person: {who_to_call_on_arrival} Special instructions: {building_access / loading_procedures} Carrier: {freight_company} Estimated delivery: {date_range}
Write a 170 to 210 word response confirming the delivery arrangements, explaining the coordination process, providing carrier contact information, and outlining what the customer should expect on delivery day.
When to use it: When large or complex deliveries require coordination between customer, carrier, and receiving location.
Pro tip: Get a direct phone number for the receiving dock or warehouse - business receptionists often don’t know about delivery requirements.
You are explaining international shipping delays due to customs processing.
Customer name: {customer_name} Destination country: {country_name} Order contents: {general_product_description} Customs status: {held_for_inspection / duty_assessment / documentation_required} Required action: {customer_must_provide_info / pay_duties / wait_for_clearance} Typical processing time: {timeframe_range} Tracking updates: {how_to_monitor_progress} Customer responsibility: {duties_taxes_fees}
Write a 200 to 250 word response explaining customs procedures, what’s happening with their package, any required customer actions, and realistic expectations for final delivery timing.
When to use it: When international orders get held up in customs and customers need education about the process.
Pro tip: Include links to the destination country’s customs website so customers can research duties and procedures themselves.
You are arranging a redelivery attempt for a missed delivery.
Customer name: {customer_name} Tracking number: {tracking_number} Carrier: {delivery_company} Missed delivery date: {first_attempt_date} Reason missed: {no_answer / signature_required / access_issues} Package location: {depot / truck / holding_facility} Redelivery options: {next_business_day / scheduled_time / pickup_location} Customer availability: {preferred_times} Special instructions: {where_to_leave / who_can_sign}
Write a 160 to 200 word response explaining redelivery options, how to schedule the next attempt, alternative pickup locations if available, and what to do if they miss the second delivery attempt.
When to use it: When first delivery attempts fail and you need to coordinate successful redelivery.
Pro tip: Suggest pickup locations (UPS Store, FedEx Office) as backup options when customers have unpredictable schedules - it prevents multiple failed attempts.
Frequently Asked Questions
What makes an AI prompt effective for customer service responses?
The best customer service AI prompts include specific scenario details, real customer information variables, clear tone guidelines, and length constraints. This ensures responses sound natural and address the actual situation rather than giving generic answers.
How can I customize these AI prompts for my industry?
Replace the product/service variables with your specific offerings and adjust the tone variables to match your brand voice. Add industry-specific terminology and common issues your customers face to make responses more relevant.
Should I edit AI-generated customer service responses before sending?
Always review AI responses for accuracy, especially regarding policies, pricing, and timelines. The AI provides a strong draft, but you should verify all factual information and add any customer-specific details that weren’t in the original prompt.