Escalation summary for IT & Software

You are an expert in this kind of work, and you know the IT & Software sector from the inside.

## Your task
Summarise this support thread at a software company that ships a SaaS product for escalation to [TEAM]. Give: customer and account, the issue in one sentence, steps already taken, impact on the customer, what we need from the team, and urgency with a reason. Under 150 words.

## About my situation
- Who this is for: engineering leads, developers and IT buyers
- What we must respect: uptime, security and data-protection requirements
- How we measure success: deployment frequency and uptime

## What matters in IT & Software
- How customers decide: technical evaluators and budget owners decide together; they judge security, integrations, total cost and support quality; free trials and proofs of concept are common; contracts are usually annual and renew.
- Common risks to plan for: outages; data breaches and security holes; vendor lock-in; scope creep; knowledge held by one person; churn after a bad release.
- Rules and standards that usually apply: data-protection law (GDPR in the EU, the DPDP Act 2023 in India, CCPA in California); SOC 2 or ISO 27001 security audits; OWASP secure-coding practice; open-source licence terms; the uptime and support promises in customer SLAs.
- Words people in this field use: SaaS; multi-tenant; SLA; incident; sprint; release; tech debt; API; ARR.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
Thread: [PASTE THREAD]

## How to work through it
1. Read the thread.
2. Summarise the issue in one sentence.
3. List steps taken and impact.
4. State what we need and the urgency.

## What to deliver
- Escalation summary under 150 words

## Rules
- Make every point specific to my situation and my industry; replace generic advice with detail that fits.
- Use plain language, short sentences, and tables where they make the answer easier to scan.
- Use only the facts I give you. Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The tone is calm and human, and the customer knows exactly what happens next and when.
- It is written for a software company that ships a SaaS product; nothing in it would read the same for any other business.
- Nothing in it breaks uptime, security and data-protection requirements.
- Every item under "What to deliver" is included.