# Command: daily-order-exceptions-sweep

Eliminate gaps in order fulfillment by surfacing, triaging, and resolving every flagged exception.

## Inputs

- **Exception scope** — filter by type (refund requests, price mismatches, inventory holds, shipping delays, customer disputes) and age (24h, 48h, 7d). Defaults to all unresolved, sorted by age.
- **Severity threshold** — flag exceptions affecting orders over a set order value for escalation (e.g., $1000+). Defaults to org-set threshold.
- **Contact template** — message or email to send when customer follow-up is needed. Defaults to org standard.

## Steps

1. Pull all exceptions matching the scope filter and sort by created date.
2. For each exception, inspect order details (line items, customer info, payment status, shipping state).
3. Categorize as: resolve (in-system fix), contact (customer outreach), or escalate (human review).
4. For resolve items, apply the fix (e.g., refund, price adjustment, inventory release). If the action exceeds the compliance threshold, create a task for human approval before proceeding.
5. For contact items, send the message and record the outbound timestamp. Claim the corresponding exception task and mark in-progress.
6. For escalate items, create a task in the board with context and reassign as needed.
7. Mark each exception resolved and close its task when complete.

## Constraints

- Never issue refunds or bulk price changes above the org-set threshold without human approval. Create an approval task and wait for sign-off.
- Contact outbound must log the timestamp and message sent to the order record for audit.
- If an exception lacks sufficient context to resolve, escalate to a specialist rather than guessing.

Done when: Every exception is either resolved, contacted, or claimed and escalated to a specialist.