Business - Customer Support System That Turns Angry Customers into Fans

EXECUTION-READY PROMPT TASK You are the customer operations lead. The assignment is: Business - Customer Support System That Turns Angry Customers into Fans. Primary professional job: a measurable support operating system. Primary outcome: Customer Support System That Turns Angry Customers into Fans. Use the stated objective (Customer Support System That Turns Angry Customers into Fans) as the primary success criterion. If the objective contains an implied claim, distinguish the desired outcome from evidence that it has actually occurred. INPUTS AND SOURCE OF TRUTH Use these inputs when supplied: baseline metrics, constraints, existing process, team capacity, financial assumptions, customer evidence. If critical information is missing, state the assumption and proceed; do not fabricate evidence, metrics, customer quotes, sources, code APIs, legal requirements, or product capabilities. Treat supplied files, references, code, data, copy, and exact user facts as authoritative. Preserve them unless the task explicitly asks for transformation. When sources conflict, flag the conflict instead of silently choosing a convenient version. EXECUTION Produce support SOP and KPI dashboard spec. Use this native workflow: ticket taxonomy → routing → SLA → macros → escalation → QA → reporting. The work must explicitly address: priority rules, SLA tiers, routing, macros, escalation, QA sampling, CSAT/FCR metrics. OBJECTIVE-SPECIFIC DECISIONS - Keep the primary outcome visible in every major decision; do not optimize a proxy at the expense of the actual task. - Prefer the smallest set of decisions that can materially change the outcome. Do not add impressive but irrelevant work. DECISION RULES - Optimize for the professional job, not for impressive-sounding output. - Prefer concrete decisions, examples, numbers, schemas, timings, layouts, or steps over adjectives. - Separate facts, assumptions, recommendations, and predictions. - Do not invent citations, performance results, customer evidence, product capabilities, legal requirements, technical APIs, or required text. - If a critical input is missing, make the smallest defensible assumption, label it, and continue. - Turn the goal into a decision-ready operating artifact with assumptions, owners, metrics, and next actions. - Treat numeric goals as targets to test against evidence, not as promises. REQUIRED OUTPUT 1. Executive answer 2. Baseline and assumptions 3. Analysis/options 4. Recommendation 5. 30/60/90-day actions 6. KPI scorecard Where alternatives are useful, provide no more than three materially different options and explain the trade-off of each; do not create cosmetic variants that do not change the decision. FAILURE PREVENTION Quality-check the result against: agents can execute without ambiguity; escalation and ownership are clear. Also verify that facts are separated from assumptions, the requested outcome is measurable where applicable, and every recommendation/action has an owner, next step, or validation method when the task requires one. If a check fails, identify the smallest responsible variable, revise only that variable, and rerun the relevant acceptance check. Do not rewrite the entire solution just to make it look different. FINAL STANDARD The result must be usable by a professional in the stated Customer Support context on the first serious execution. It should be specific enough to act on, test, hand off, or publish without requiring the model to invent missing fundamentals.