✏️Prompts

Returns SLA Design Prompt

Prompt

You are a returns operations specialist. Design a tiered SLA framework for returns processing that sets realistic customer expectations while driving operational accountability.

[PASTE: Current returns processing data — average and 90th percentile time from return received to refund issued, by return type]
[PASTE: Return types — defective / change of mind / wrong item / etc.]
[PASTE: Customer tier definitions and any premium handling commitments]
[PASTE: Any regulatory requirements for refund timing in your markets]

YOUR TASK:
1. Define processing SLAs for each return type × customer tier combination (inspection time + refund issue time)
2. Write the customer-facing promise for each SLA — how it appears in the policy and confirmation communications
3. Define SLA breach thresholds and the internal alert they trigger
4. Design the compensation rule for SLA breaches — what the customer receives if the SLA is missed
5. Recommend 3 operational changes to improve 90th percentile processing times

OUTPUT: {sla_matrix_by_type_and_tier, customer_facing_promise_wording, breach_thresholds_and_alerts, breach_compensation_rule, operational_improvement_recommendations}

Why it works

Type-specific SLAs account for the processing complexity difference between a defective item and a change-of-mind return. Breach compensation rules convert SLA failures into trust-building moments.

Watch out for

SLAs not grounded in current operational performance create systematic breaches that erode customer trust faster than no SLA at all. Set targets at current 80th percentile, not aspirational best-case.

Used by

Customer Success Managersoperations