Match-Target — Reverse-Engineer the Ticket Triage Rule

You're an operations analyst handed 12 tickets and a column showing the expected triage outcome per ticket. The triage logic lives in a runbook nobody can find — derive the rule from the target column itself, then encode it as a single formula.

Columns:

• A — TicketID
• B — Severity (Critical / Major / Minor)
• C — Customer (Enterprise / SMB / Free)
• D — AgeDays (number)
• E — YourFlag (you fill this with a formula)
• F — TargetFlag (the source of truth — what you're trying to match)

Five possible outcomes appear in column F: Auto-Escalate, Manual-Review, Auto-Close-Stale, Pending-Customer, Standard.

Hint — the rule has the structure of a precedence ladder (first match wins). The five branches use Severity, Customer, and AgeDays. Two AgeDays cutoffs separate "fresh," "aging," and "stale." The Minor rows include adjacent values (30 vs. 31 days) that pin the stale boundary precisely — make sure your thresholds match those rows exactly.

Your task:

1. Inspect column F to identify the precedence order, the (Severity, Customer) combinations that escalate or trigger manual review, and the two AgeDays thresholds.
2. Write a single formula in column E that produces the same outcomes as column F for every row. Drag-fill from E2 → E13.

Graded cells: E2 (TKT-001 Critical → Auto-Escalate), E5 (TKT-004 Major/SMB/3d → Manual-Review), E7 (TKT-006 Minor/Enterprise/31d → Auto-Close-Stale — stale boundary), E8 (TKT-007 Minor/SMB/5d → Standard), E9 (TKT-008 Minor/Free/15d → Pending-Customer), E10 (TKT-009 Minor/Enterprise/30d → Pending-Customer — pending boundary).