Generate a complete standard operating procedure for any business process

# Standard Operating Procedure: Customer Refund Processing **SOP Number:** OPS-FIN-2024-003 **Effective Date:** July 1, 2024 **Department:** Customer Support / Finance **Process Owner:** Head of Customer Operations **Review Cycle:** Quarterly --- ## 1. Purpose and Scope This SOP defines the end-to-end process for handling customer refund requests. It covers full refunds, partial refunds, and store credit issuance for all payment methods (credit card, PayPal, bank transfer, store credit). **In scope:** Refund requests from direct customers via support tickets, chat, phone, and social media. **Out of scope:** Chargebacks (see SOP-FIN-2024-007), wholesale/B2B refunds (see SOP-FIN-2024-011). --- ## 2. Roles and Responsibilities | Role | Responsibility | |---|---| | L1 Support Agent | Receive request, verify eligibility, process refunds ≤ $50 | | L2 Support Lead | Approve refunds $50–$500, handle escalations | | Finance Manager | Approve refunds > $500, monthly reconciliation | | QA Analyst | Audit 10% of processed refunds weekly | --- ## 3. Prerequisites and Required Tools - Access to Zendesk (support ticket system) - Access to Stripe dashboard (payment processing) - Access to internal admin panel (order lookup) - Refund reason codes reference sheet (pinned in #support-ops Slack) - Calculator for partial refund amounts --- ## 4. Step-by-Step Procedure ### Step 1: Receive and Log Request (Est. 2 min) 1.1. Open the incoming support ticket/chat/call 1.2. Log the request in Zendesk with tag `refund-request` 1.3. Record: order number, customer email, requested amount, stated reason ### Step 2: Verify Eligibility (Est. 3 min) 2.1. Pull up the order in the admin panel 2.2. Check refund eligibility: - Order placed within 30 days? → Eligible for full refund - Order placed 31–90 days? → Eligible for store credit only - Order placed 90+ days? → Not eligible (escalate if customer insists) 2.3. Verify the item/service status: - Digital product: Was it downloaded/accessed more than 3 times? → Partial refund only - Physical product: Has return label been generated? → Require return receipt - Subscription: Pro-rate remaining days in billing cycle 2.4. Check customer history: More than 3 refunds in 12 months? → Flag for L2 review ### Step 3: Determine Refund Type (Est. 1 min) **Decision Tree:** ``` Is the order within 30 days? ├─ YES → Is the product unused/unopened? │ ├─ YES → Full refund to original payment method │ └─ NO → Partial refund (70% of order value) └─ NO → Is it within 90 days? ├─ YES → Store credit for full amount └─ NO → Deny with explanation (offer 15% discount code as goodwill) ``` ### Step 4: Process the Refund (Est. 3 min) 4.1. Open Stripe dashboard → search by order ID 4.2. Click "Issue Refund" → select Full or Partial 4.3. Enter refund amount (double-check against order total) 4.4. Add internal note with reason code from reference sheet 4.5. For store credit: generate credit code in admin panel → email to customer 4.6. Update Zendesk ticket: add refund confirmation ID, amount, method ### Step 5: Communicate with Customer (Est. 2 min) 5.1. Send refund confirmation email using template RC-01 (full) or RC-02 (partial) 5.2. Include: refund amount, method, expected timeline (3–5 business days for card, 1 day for store credit) 5.3. If denied: use template RD-01 with clear explanation and alternative offer ### Step 6: Close and Document (Est. 1 min) 6.1. Set Zendesk ticket status to "Resolved" 6.2. Tag with final refund reason code 6.3. If amount > $200: add entry to the monthly refund tracker spreadsheet --- ## 5. Quality Checkpoints - [ ] Refund amount matches order value (or correct partial calculation) - [ ] Correct payment method selected in Stripe - [ ] Customer notification sent with accurate timeline - [ ] Zendesk ticket tagged with correct reason code - [ ] Approval obtained for refunds above agent threshold --- ## 6. Escalation Paths | Scenario | Escalate To | Response SLA | |---|---|---| | Customer threatens legal action | L2 Lead + Legal | 2 hours | | Refund amount > $500 | Finance Manager | 4 hours | | System error preventing refund | IT Support (#eng-support) | 1 hour | | Customer has 3+ refunds in 12 months | L2 Lead for pattern review | Same day | | Payment method no longer valid | Finance team for manual transfer | 24 hours | --- ## 7. KPIs to Track - **Average refund processing time:** Target < 12 minutes end-to-end - **First-contact resolution rate:** Target > 85% - **Refund accuracy rate:** Target > 99% (no incorrect amounts) - **Customer satisfaction (post-refund CSAT):** Target > 4.2/5 - **Refund rate as % of revenue:** Monitor monthly, flag if > 3% --- ## 8. Revision History | Version | Date | Author | Changes | |---|---|---|---| | 1.0 | July 1, 2024 | Ops Team | Initial release | | | | | |