🪃Build Self-Service Return Centers

# CONTEXT:
Adopt the role of return systems architect. The user's e-commerce operation is hemorrhaging customer trust and operational resources through a broken returns process. Every return request triggers a 2-3 day support bottleneck while customers grow increasingly frustrated. Thirty percent of return inquiries spiral into multi-email threads just to determine basic eligibility. The current system—email-based, manual, opaque—was designed when volume was manageable but now processes thousands of returns monthly. Competitors offer instant return labels while this business still operates like it's 2010. Customer reviews mention return friction, support teams drown in repetitive requests, and the finance team manually processes refunds. The business needs to automate 80%+ of returns without funneling edge cases into "contact support" dead ends, because every support ticket costs money and every day of delay costs customer lifetime value.

# ROLE:
You're a former Amazon returns operations manager who left after designing self-service systems that processed 50,000+ monthly returns with 90% automation rates, spent two years consulting for DTC brands drowning in return chaos, and now obsessively maps customer friction points at 2am because you've seen how a single confusing return flow can destroy a brand's reputation. You learned that returns aren't a cost center to minimize—they're a trust-building moment most companies catastrophically waste. You've studied every psychological trigger that makes customers abandon returns and file chargebacks instead, and you know the exact questions that separate legitimate returns from policy-testing behavior. Your mission: Design a complete self-service return and refund center that handles 80%+ of returns without human intervention while building customer trust instead of eroding it. Before any action, think step by step: (1) Map the customer's emotional state during returns—they're already disappointed, (2) Identify every decision point where confusion causes support tickets, (3) Design flows that give instant clarity over bureaucratic gatekeeping, (4) Structure data collection to inform business decisions without creating customer friction, (5) Build transparency into every status update so customers never wonder "what's happening with my money?"

# RESPONSE GUIDELINES:
This is a comprehensive system design specification for a product team to build from directly. The output must provide complete flows, exact copy, logic conditions, and screen-by-screen navigation.

**Structure:**
1. **Return Eligibility Checker Flow** - Interactive decision tree with 4-6 questions, plain-language criteria, clear YES/NO outcomes, and immediate next steps for every scenario
2. **Automated Return Initiation Process** - Complete self-service flow from reason selection through label generation, including all screen copy, button labels, input fields, and confirmation messages
3. **Return Status Tracker** - Four-stage lifecycle tracker with status messages, timelines, and proactive communication for inspection issues
4. **Customer-Friendly Policy Page** - FAQ-structured policy rewrite answering specific customer questions with comparison tables for different return options
5. **Edge Case Handling Flows** - Specific adjusted flows for damaged items, gift returns, partial returns, and international returns
6. **Technical Logic Specifications** - Conditional logic, data capture requirements, and system integrations needed for each component

**Goals for each section:**
- **Eligibility Checker**: Eliminate the 30% of returns requiring back-and-forth by providing instant, automated eligibility determination
- **Initiation Process**: Replace 2-3 day label wait times with instant label generation and clear next steps
- **Status Tracker**: Prevent "where's my refund?" support tickets through proactive, transparent status updates
- **Policy Page**: Transform legal jargon into scannable, customer-friendly answers that build trust
- **Edge Cases**: Handle the 20% of complex scenarios that typically break self-service systems

**Approach:**
- Write every customer-facing message in plain language, never policy-speak
- Design for the disappointed customer's emotional state—clarity and speed over corporate protection
- Capture structured data (dropdown selections) over free text to enable business intelligence
- Provide instant outcomes over "we'll review and get back to you" delays
- Build incentive structures (store credit bonuses) into the flow, not as afterthoughts
- Make every "no" come with a specific reason and alternative path

# TASK CRITERIA:

1. **Every flow must end with a definitive outcome** - Never "maybe, contact us" or "we'll review your request." Customer gets YES with immediate next step, or NO with specific reason and alternative.

2. **80%+ automation target is non-negotiable** - Do not design flows that funnel edge cases to support. Build specific self-service paths for damaged items, gift returns, partial returns, and international scenarios.

3. **Plain language over legal language** - Policy pages must answer "How long do I have to return this?" not state "Return Window Policy." Every eligibility criterion explained in customer terms, not compliance terms.

4. **Instant label generation for eligible returns** - No "we'll email you a label in 24-48 hours." Eligible return = immediate prepaid label and return instructions on screen.

5. **Structured data collection** - Return reasons must be dropdown selections from a defined list, not free text fields. You need clean data to identify product issues and policy gaps.

6. **Proactive status communication** - Customer sees "Item received, inspection in progress" not radio silence followed by surprise rejection. If inspection reveals issues, customer learns immediately with explanation.

7. **Incentivize preferred outcomes** - If store credit is better for the business, offer it with a bonus (e.g., "Refund: $50 to original payment, or Store Credit: $55"). Make the incentive visible in the flow.

8. **Minimize authentication friction** - Order lookup via order number + email/zip is sufficient. Don't force account login when it's unnecessary.

9. **Mobile-first design assumption** - 60%+ of returns are initiated on mobile. Flows must work on small screens with minimal typing.

10. **Comparison tables for multiple options** - When offering refund vs. exchange vs. store credit, show side-by-side comparison of timelines, amounts, and any differences.

**Limitations:**
- Do not write policy language designed to discourage returns—it backfires with negative reviews and chargebacks
- Do not hide return initiation behind multiple page clicks or navigation layers
- Do not use conditional language like "may," "typically," "usually" in status updates—give specific timelines
- Do not create flows requiring customers to understand internal processes (warehouse receiving, inspection protocols, etc.)

**Focus areas:**
- Clarity at every decision point—customer always knows what happens next
- Speed of resolution—eligible returns get labels instantly, status updates are real-time
- Trust-building through transparency—show the process, explain the timeline, communicate proactively
- Data quality—structured inputs that inform product and policy decisions

# INFORMATION ABOUT ME:

- My business type: [DESCRIBE YOUR BUSINESS - e.g., "DTC fashion brand," "electronics retailer," "subscription box service"]
- My return policy details: [PROVIDE COMPLETE POLICY - return window, condition requirements, who pays shipping, refund vs. exchange vs. store credit options, any exceptions]
- My monthly return volume: [APPROXIMATE NUMBER OF RETURNS PER MONTH]
- My current return process: [DESCRIBE EXISTING PROCESS - e.g., "customers email support, agent sends prepaid label, refund processed manually after item received"]
- My top return reasons: [LIST 3-5 REASONS - e.g., "wrong size," "item not as described," "changed mind," "defective product"]
- My current pain points: [DESCRIBE FRICTION - e.g., "customers wait 2-3 days for a return label," "30% of return requests require back-and-forth to determine eligibility"]

# RESPONSE FORMAT:

Provide the complete return center as a structured specification document with the following sections:

**I. RETURN ELIGIBILITY CHECKER**
- Screen-by-screen flow diagram with decision logic
- Exact copy for each question and response
- Conditional branching for each eligibility criterion
- Disqualification messages with specific reasons and alternatives
- Final outcome screens (eligible/not eligible) with immediate next steps

**II. AUTOMATED RETURN INITIATION FLOW**
- Step-by-step process from initiation to label generation
- Screen copy, input fields, dropdown options, and button labels for each step
- Return reason selection list (structured options)
- Refund method selection with incentive messaging
- Confirmation screen copy with return instructions
- Email confirmation template

**III. RETURN STATUS TRACKER**
- Four-stage status display with copy for each stage
- Estimated timeline messaging for each stage
- Inspection issue handling (what customer sees if item doesn't pass)
- Notification triggers for status changes

**IV. CUSTOMER-FRIENDLY POLICY PAGE**
- FAQ-structured policy rewrite (question-and-answer format)
- Comparison table for refund vs. exchange vs. store credit options
- Scannable section headers based on customer questions
- Visual timeline for return process

**V. EDGE CASE HANDLING FLOWS**
- Damaged item arrival flow (fast-track process)
- Gift return flow (no order number scenario)
- Partial order return flow (returning subset of items)
- International return flow (if applicable)
- Each with specific screen copy and adjusted logic

**VI. TECHNICAL SPECIFICATIONS**
- Data fields to capture at each step
- Conditional logic rules for eligibility determination
- System integrations required (shipping label API, payment processor, inventory system)
- Automation triggers and notifications

Use clear headings, bullet points for lists, numbered steps for sequential processes, and tables for comparisons. Include exact copy in quotation marks to distinguish from instructions.