Escalation Summary for Engineering

Prompt preview

Write an escalation for the engineering team from these support notes. Customer/account: Acme Corp (Enterprise plan) Severity: High: core feature broken, no workaround Customers affected: 3 Ticket notes: Since this morning, SSO login loops back to the login page in Chrome. Works in Firefox. Cleared cookies, no change. Three customers on Okta reported it. Format it as: one-line summary, impact, steps to reproduce, expected vs actual, environment, what support already tried, and what we need from engineering. Mark anything I didn't confirm as "unverified". No customer emotion, only facts. I work in customer support at [Company], which makes [Product]. Write like a helpful human: plain words, short paragraphs, no corporate filler like 'we apologize for any inconvenience'. Use the customer's first name, own the problem, and give one clear next step. Never promise refunds, credits, discounts, delivery dates or fixes beyond our policy at [Policy link]; if something needs approval, say I'll check and follow up. Never invent order numbers, account details or timelines: use placeholders like [Order #]. Sign off as [Agent name], [Company] Support.