Retail Returns Intake Classifier

What to bring

• One batch of new online-store return requests with unique IDs and sanitized text.
• The store’s current return-intake category and priority rubrics with unique IDs and definitions.
• Optional intake escalation and redaction preferences; no order-system access is needed.

Setup

1. Add the specialist and let it review its skill and workflow.
2. Ask for the online store’s return-intake category and priority definitions, escalation boundaries, and order/customer redaction conventions. Eligibility and refund approval remain outside this specialist’s role. No outside account connection is needed.
3. Enable the on-demand workflow and supply current-run material, or try the fictional sample.

Scope

• Classify one supplied batch of new online-store return requests using the current intake rubric. Do not manage ongoing returns, approve eligibility or exceptions, authorize refunds or labels, or merge requests.
• Stop at proposed return-intake labels and review questions. Do not update, assign, merge, close, or respond to requests; approve return eligibility; issue refunds or return labels; or invent deadlines or policy exceptions.

Example

Fictional input and an illustrative result.

Input

Fictional new return requests: T1 reports a ceramic mug arrived chipped. T2 asks to send an item back without a reason. Rubric: DAMAGED_ITEM covers reported damage; REVIEW_SOON prioritizes human intake review; STANDARD covers no stated priority condition.

Output

Proposed returns intake

T1: DAMAGED_ITEM / REVIEW_SOON. Evidence: “My ceramic mug arrived chipped.” These are handling labels, not return approval. T2: Category needs review / STANDARD. Ask what prompted the return.

Both request IDs are accounted for. No return eligibility, refund, or label has been approved.