Prompt Details
Model
Chat - (gpt-5.6)
Token size
1,971
Example input
[BUSINESS_INFORMATION]: Online fashion store selling clothing and accessories. The company prioritizes consistent customer service and accurate policy application. Customer support representatives can handle standard requests but must escalate policy exceptions.
[SUPPORT_PROCESS_OR_SCENARIO]: Create an SOP for handling customer requests to return products and receive refunds.
[CURRENT_WORKFLOW_AND_POLICIES]: Customers can request a return within 14 days of delivery. Products must be unused, unworn, and in their original condition with tags attached. Once the returned product is inspected and approved, the customer receives a refund to the original payment method. Items showing signs of use are not eligible for a standard return. Policy exceptions require manager approval.
[TEAM_ROLES_AND_TOOLS]: Customer Support Representatives receive requests and verify order information. Warehouse staff inspect returned products. Managers approve exceptions. The team uses an e-commerce order-management system and email for customer communication.
[SOP_REQUIREMENTS_AND_PREFERENCES]: Create a clear step-by-step SOP that a newly hired support representative can follow. Include eligibility checks, roles, decision points, customer communication, escalation rules, documentation, and a quality-control checklist. Keep the language professional and practical.
Example output
E-COMMERCE CUSTOMER SUPPORT SOP
SOP Title: Customer Product Return & Refund Processing SOP
Purpose: To ensure customer return and refund requests are handled consistently, accurately, and according to the company's stated return policy.
Scope: Covers customer requests to return clothing or accessories and receive a refund after the returned product is inspected and approved.
Trigger: A customer contacts Customer Support requesting to return a product and receive a refund.
Intended Outcome: Eligible returns are processed correctly, customers receive appropriate communication, approved refunds are issued to the original payment method, and all cases are properly documented and closed.
Responsible Teams/Roles:
Customer Support Representative (CSR)
Warehouse Staff
Manager
1. PROCESS OVERVIEW
When This SOP Applies:
A customer requests to return a purchased product.
The customer is seeking a refund for the returned product.
The request can be assessed against the company's 14-day return policy.
When It Does Not Apply:
Requests unrelated to product returns/refunds.
Situations requiring a policy exception that have not yet received manager approval.
Products that fail the standard return conditions.
Any issue outside the authority defined in this SOP unless management provides further instructions.
Required Information:
Customer/order information available in the order-management system.
Date of delivery.
Product being returned.
Product condition.
Relevant return-policy requirements.
Any information provided by the customer regarding the return.
Required Tools:
E-commerce order-management system
Email
Internal communication/management process for escalation
2. ROLES & RESPONSIBILITIES
Role Responsibility Authority
Customer Support Representative Receive the request, verify order information, check return eligibility, communicate with the customer, document the case, and coordinate the process. Can handle standard requests that meet the stated policy. Must escalate policy exceptions.
Warehouse Staff Receive/inspect the returned product and determine whether it meets the stated physical-condition requirements. Responsible for product inspection. Further authority regarding exceptions is not specified.
Manager Review and approve policy exceptions and cases requiring management intervention. Authority to approve policy exceptions.
Important: No employee should approve an exception without the required manager approval.
3. STEP-BY-STEP PROCEDURE
Step Action Responsible Role Verification/Decision Expected Outcome
1 Receive the customer's return/refund request. CSR Confirm that the customer is requesting a product return and refund. Request is identified as a return/refund case.
2 Locate and verify the order in the e-commerce order-management system. CSR Verify the relevant customer/order information and delivery date. Correct order is identified.
3 Check the return timeframe. CSR IF the request is within 14 days of delivery → continue. OTHERWISE treat it as outside the standard return policy and escalate if an exception is requested. Time eligibility is established.
4 Explain/check the required product condition. CSR Product must be unused, unworn, in original condition, and have tags attached. Customer understands the standard eligibility requirements.
5 Determine whether the request meets the standard policy based on available information. CSR IF all known requirements are satisfied → proceed through the standard return process. IF a requirement is not satisfied → do not approve a standard return; escalate if the customer is requesting an exception. Standard eligibility or exception status is established.
6 Communicate the applicable next step to the customer. CSR Ensure communication reflects the actual policy status. Customer receives clear instructions/status.
7 Returned product is inspected. Warehouse Staff Check whether the returned product is unused, unworn, in original condition, and has tags attached. Product is approved or found ineligible based on inspection.
8 Record the inspection outcome and communicate the result through the support process. CSR / Warehouse Staff IF inspection confirms the stated requirements → proceed to refund. IF product shows signs of use or otherwise fails the requirements → standard return is not eligible. Final return eligibility is established.
9 Process/confirm the refund after the returned product has been inspected and approved. Responsible authority to be confirmed Refund must only proceed after inspection and approval. Refund is issued to the original payment method.
10 Communicate the resolution to the customer. CSR Confirm whether the return/refund was approved or not approved. Customer receives the final outcome.
11 Document the complete case. CSR Record the relevant order, eligibility decision, inspection outcome, communication, and any required approval. Case history is complete.
12 Close the case once the applicable process is complete. CSR Confirm that no required action remains outstanding. Case is properly closed.
4. DECISION RULES
Rule 1 — Return timeframe
IF: The customer requests a return within 14 days of delivery.
THEN: Continue with the standard eligibility assessment.
OTHERWISE: The request falls outside the standard return policy. Do not promise approval. If the customer requests an exception, escalate to a manager.
Rule 2 — Product condition
IF: The product is unused, unworn, in its original condition, and has tags attached.
THEN: It meets the stated product-condition requirements for a standard return, subject to inspection.
OTHERWISE: It is not eligible for a standard return. If an exception is requested, escalate to a manager.
Rule 3 — Inspection approval
IF: Warehouse inspection confirms that the returned product meets the required condition.
THEN: The return is approved and the refund proceeds to the original payment method.
OTHERWISE: The standard return is not eligible.
Rule 4 — Policy exception
IF: A request requires an exception to the stated return policy.
THEN: Escalate to a manager for approval before promising or applying the exception.
OTHERWISE: Process the request according to the standard policy.
Rule 5 — Employee authority
IF: The requested action is within the CSR's standard authority and complies with the stated policy.
THEN: The CSR may handle the request through the standard process.
OTHERWISE: Escalate the case rather than making an unauthorized commitment.
Rule 6 — Refund timing
IF: The returned product has been inspected and approved.
THEN: The customer receives a refund to the original payment method.
OTHERWISE: Do not represent the refund as approved.
Note: The business has not supplied a specific refund-processing timeframe, so employees must not promise a specific number of days.
5. CUSTOMER COMMUNICATION
Initial Response
Hello [Customer Name],
Thank you for contacting us regarding your return request. We’ll review your order and check it against our return policy, including the delivery date and product-condition requirements.
We’ll guide you through the next step once the eligibility check is complete.
Best regards,
Customer Support Team
Information Request
Hello [Customer Name],
To review your return request, we need to verify the relevant order information. Please provide the information needed to identify your order.
Once verified, we’ll assess the request according to our return policy.
Best regards,
Customer Support Team
Resolution Response — Approved
Hello [Customer Name],
Your returned product has been inspected and approved under our return policy. Your refund will be issued to the original payment method.
Thank you for your cooperation.
Best regards,
Customer Support Team
Resolution Response — Standard Return Not Eligible
Hello [Customer Name],
We have reviewed your return request. Under our standard return policy, returned products must be unused, unworn, in their original condition, and have tags attached.
As the returned product does not meet the standard return requirements, we are unable to approve it as a standard return.
Best regards,
Customer Support Team
Escalation/Delay Response
Hello [Customer Name],
Your request requires additional review because it falls outside our standard return process. We have escalated the matter for management review and will communicate the outcome once the review is complete.
Thank you for your patience.
Best regards,
Customer Support Team
Final Follow-Up
Hello [Customer Name],
We’re following up to confirm that your return/refund case has been completed according to the applicable return process.
Thank you for contacting us.
Best regards,
Customer Support Team
Communication rule: Employees must not promise an exception, refund, compensation, or specific processing timeframe unless it is supported by the company's policy or an approved management decision.
6. EXCEPTION & ESCALATION HANDLING
Scenario Required Action Escalation Reason
Return requested after 14 days Do not treat it as a standard eligible return. If an exception is requested, refer for management review. Manager Outside stated timeframe
Product shows signs of use Do not approve as a standard return. Communicate the policy outcome. Manager only if an exception is requested. Product-condition requirement not met
Product is worn/used Treat as ineligible for standard return. Manager only if an exception is requested. Standard policy requirement not met
Tags are missing Do not approve as a standard return unless an approved exception applies. Manager if exception requested. Tags are a stated eligibility condition
Product is not in original condition Do not approve as a standard return. Manager if exception requested. Original-condition requirement not met
Customer requests a policy exception Do not promise approval. Send for management review. Manager Exceptions require manager approval
Customer repeatedly contacts support about the same case Review the existing case documentation before responding. Escalate if the matter requires authority beyond the CSR's role. Manager when outside CSR authority Prevents inconsistent or unauthorized decisions
Serious complaint Document the issue and escalate if it requires authority beyond the CSR's role. Management review where required Serious complaints may require additional handling
Legal threat Do not make legal commitments or policy exceptions. Escalate to management. Manager Outside normal CSR authority
Suspected fraud Do not make unsupported accusations or provide unauthorized exceptions. Document the concern and escalate. Manager No fraud-handling procedure was supplied
Safety concern Document the concern and escalate rather than attempting to resolve it through the normal return process. Manager Safety procedure was not supplied
System error prevents order verification or processing Document the error and escalate according to available management direction. Management / designated system authority to be confirmed Standard system-error procedure was not supplied
Note: The business has not specified special procedures for high-value orders, fraud, legal threats, safety concerns, reputation-risk cases, or system failures. The table therefore does not create new approval thresholds or outcomes for these situations.
7. QUALITY CONTROL CHECKLIST
Before closing a return/refund case, the responsible employee should verify:
Customer information verified
Correct order identified in the order-management system
Delivery date verified
14-day return timeframe checked
Product-condition requirements checked
Product inspection completed where applicable
Return decision matches the stated policy
Any policy exception received manager approval
Refund is only treated as approved after the returned product is inspected and approved
Refund is directed to the original payment method
Customer response sent
Customer communication accurately reflects the decision
Case documentation completed
Any escalation recorded
Required follow-up completed
Case properly closed
8. PERFORMANCE METRICS
Recommended KPIs:
First Response Time
Measures how quickly customers initially receive a response.
Resolution Time
Measures the time from receiving a return request to completing the case.
First-Contact Resolution Rate
Measures how many return inquiries are resolved without unnecessary additional contacts.
Escalation Rate
Measures the proportion of cases requiring management intervention.
Return Resolution Accuracy
Measures whether return decisions correctly follow the stated policy.
Case Reopen Rate
Measures how frequently supposedly completed cases require additional action.
Customer Satisfaction
Can be used to assess the customer experience following return/refund handling.
Refund/Exception Rate
Can help management monitor how often standard policy exceptions are being approved.
How to Measure: Use case records, order-management data, communication records, and management-approved reporting methods.
Suggested Review Frequency: Management should establish an appropriate review frequency. A specific frequency was not supplied and therefore is not prescribed by this SOP.
Important: No numerical performance targets are established because the business has not supplied any.
9. TRAINING & IMPLEMENTATION
Employee Training Points
New CSRs should understand:
The 14-day return window begins from delivery.
Standard returns require the product to be unused.
Products must also be unworn, in original condition, and have tags attached.
Product inspection is required before an approved refund.
Approved refunds go to the original payment method.
Products showing signs of use are not eligible for a standard return.
Policy exceptions require manager approval.
CSRs must not promise unauthorized exceptions or refunds.
Order information must be verified before making a decision.
Case information and customer communication must be documented.
Employees should distinguish between a standard-policy case and an exception case.
Common Mistakes
Avoid:
Approving a return without checking the delivery date.
Treating a request made after 14 days as automatically eligible.
Ignoring product-condition requirements.
Approving a product that shows signs of use as a standard return.
Promising an exception before manager approval.
Treating a refund as approved before product inspection.
Failing to document the case.
Giving customers an invented refund-processing timeframe.
Providing inconsistent answers because previous case information was not reviewed.
Closing a case while required actions are still outstanding.
Implementation Checklist
Provide new employees with access to the order-management system.
Train employees on the stated return-policy requirements.
Train employees on this SOP's decision rules.
Explain the manager-escalation requirement.
Provide access to the approved customer communication templates.
Ensure warehouse staff understand the product-condition requirements they must inspect.
Establish/document the person responsible for processing or confirming refunds if this is not already defined.
Establish/document procedures for system errors and other specialized escalations not covered by the supplied policy.
Test the SOP using standard eligible and ineligible return scenarios before full implementation.
SOP Review Triggers
Review this SOP when:
The return timeframe changes.
Product-condition requirements change.
Refund procedures change.
The refund payment method/process changes.
Employee authority changes.
Manager approval requirements change.
The order-management system changes materially.
A recurring process error indicates that the SOP is unclear.
Management introduces additional escalation rules or exception policies.
10. MISSING INFORMATION / MANAGEMENT CONFIRMATION
The following information is genuinely required to make the SOP fully operational:
1. Who actually processes the refund?
The supplied roles identify CSRs, warehouse staff, and managers, but do not explicitly state which role has authority to execute the refund in the order-management/payment system.
2. What happens logistically after a return is approved?
The supplied policy states that a customer can request a return and that the product is inspected, but does not specify how the customer sends/returns the product or who provides return instructions.
3. What happens when a return is rejected after inspection?
The policy states that products showing signs of use are not eligible for a standard return, but does not specify whether the product is sent back to the customer, held, or handled in another way.
4. Refund-processing timeframe
No timeframe is supplied. Employees should therefore avoid promising a specific number of days until management defines one.
5. Shipping/return-cost policy
The supplied information does not state who bears return shipping costs or whether any shipping charges are refunded.
6. Required documentation fields
The business has not specified the exact fields that must be recorded in the order-management system. Management should define the minimum case-record requirements.
7. Special escalation rules
No specific rules are supplied for high-value orders, fraud concerns, legal threats, safety concerns, reputation-risk cases, or system failures. Management should define the responsible escalation path if these cases occur.
8. Customer response/service-level targets
No first-response or resolution-time targets were supplied. These should be defined separately if the business wants them measured or enforced.
FINAL SOP SUMMARY
When a customer requests a return and refund:
1. Receive the request → 2. Verify the order → 3. Check whether the request is within 14 days of delivery → 4. Check the product-condition requirements → 5. Determine whether it qualifies for the standard process → 6. Escalate any policy exception to a manager → 7. Have the returned product inspected → 8. If approved, process the refund to the original payment method → 9. Communicate the outcome → 10. Document the case → 11. Complete follow-up → 12. Close the case.
The core rule is:
Standard policy compliance = CSR can handle the case.
Policy exception = Manager approval required.
Returned product not meeting the stated condition = Not eligible for a standard return.
Inspection approved = Refund to original payment method.
Employees should never invent policy terms, promise unauthorized exceptions, or commit to refund timelines that management has not established.
Get this prompt + 9 more with SelectFrom $14/mo · Cancel anytimeFrom $14/mo · Cancel anytime
View SelectBy purchasing this prompt, you agree to our terms of service
GPT-5.6
Build clear, practical customer support SOPs with AI. This E-commerce Customer Support SOP Builder transforms your business information, policies, workflows, team roles, tools, and requirements into implementation-ready SOPs with step-by-step procedures, decision rules, escalation paths, customer response templates, quality checks, KPIs, and training guidance—without inventing policies or unsupported rules.
...more
Added 3 weeks ago
