Escalation summary for support leadership

Create an **Escalation fact record** from the source material below. This is for a customer-support issue that may need leadership attention.

Source material:
- High-risk tickets: [paste ticket IDs, customer messages, agent replies and timestamps]
- Account notes: [paste account notes]
- Internal updates: [paste incident notes, engineering updates, sales or success notes]

Return a Markdown table with these columns: Field | Value | Evidence source | Confidence.

Include exactly these fields:
1. Customer or account name
2. Affected users, sites or accounts
3. Customer-reported problem
4. Business impact stated by the customer
5. Service, product area or workflow affected
6. First known report time
7. Most recent customer contact time
8. Current status
9. Actions already taken
10. Current workaround
11. Unresolved blocker
12. Internal teams involved
13. Promises, commitments or deadlines already given to the customer
14. Financial, contractual, security, privacy or reputational risk mentioned in the material
15. Missing facts needed before escalation

After the table, add these two sections:
- **Conflicts and ambiguity**: list each contradiction, unclear date, unverified claim or missing owner. Quote the conflicting statements briefly and name the source for each.
- **Do not infer**: list material facts that cannot be concluded from the evidence.

Use only the supplied material. Do not invent incident severity, customer impact, ownership, cause or dates. If a field is absent, write `Not provided`. If the source uses relative time such as “yesterday”, retain that wording unless a dated timestamp in the source resolves it.

Prepare an **Escalation evidence timeline** for the customer issue below.

Customer or account: [name]
Escalation fact record: [paste the completed fact record]
Original source material, if needed: [paste tickets, notes and internal updates]

Return two sections in Markdown.

First, provide a table with these columns: Time | Event | Actor or team | Evidence | Customer impact or response consequence | Open question.

Order events from earliest to latest. Include customer reports, agent replies, hand-offs, investigations, workarounds, status updates, missed commitments and internal decisions. Use the actual timestamp where supplied. Where only a date is known, write the date. Where timing is unclear, write `Time not provided` and place the event after dated entries.

Second, provide **Timeline findings** with exactly these headings:
- Response gaps
- Repeated customer effort
- Commitments at risk
- Evidence missing for the next decision

Under each heading, give up to three bullets. Each bullet must point to a timeline event or state `No evidence supplied`.

Do not decide who is at fault. Do not state a root cause unless the supplied material explicitly confirms one. If two sources disagree, retain both accounts and label the conflict rather than choosing one.

Write a **Leadership escalation summary** using the material below. The reader is a support leader who must decide what happens next before the customer issue worsens.

Customer or account: [name]
Escalation fact record: [paste]
Escalation evidence timeline: [paste]
Additional internal context: [paste any relevant updates]

Return Markdown in this exact order:

**Subject**
One line in this format: `Decision needed: [decision] for [customer/account] by [deadline or date not provided]`.

**Customer impact**
Two to four bullets. State who is affected, what they cannot do, how long the issue has been known, and any stated business consequence. Distinguish customer statements from verified internal facts.

**Evidence**
Three to five bullets. Each must include a date or `Date not provided`, followed by the supporting ticket, note or update identifier where available.

**Actions already taken**
Bullets covering investigation, communication, workaround and hand-offs. State the result of each action.

**Current risk**
One short paragraph. Separate confirmed risk from risk that is only reported or suspected.

**Decision needed**
One numbered list of one to three specific decisions. For each item, state the decision-maker, the decision, why it is needed now, and the consequence of no decision.

**Owner and deadline**
A table with columns: Next action | Proposed owner | Deadline | Dependency or blocker.

**Open questions**
Bullets for facts that prevent a firm recommendation.

Keep the full summary under 450 words. Use plain language. Do not invent an owner, deadline, severity, root cause, refund, credit, legal position or customer commitment. Use `Owner to confirm` or `Deadline to confirm` where the material does not identify one. If evidence conflicts, say so in **Open questions**.

Review the **Leadership escalation summary** below and create a **Decision request appendix**. It must make the requested leadership decision explicit without changing or adding facts.

Leadership escalation summary: [paste draft]
Known decision-makers and responsibilities: [paste names, teams or write not provided]
Relevant operating constraints: [paste approved options, service commitments or write not provided]

Return Markdown with this exact structure:

**Decision statement**
One sentence: `Approve / decline / assign [specific action] for [customer/account] by [deadline].` If the action or deadline is not evidenced, write `Decision scope to confirm` or `Deadline to confirm`.

**Options**
A table with columns: Option | What happens | Customer consequence | Operational consequence | Approval or dependency needed.
Include only options supported by the supplied material. If there is only one viable option, include it and state why alternatives are not evidenced.

**Recommended next step**
One paragraph of no more than 80 words. Base it only on stated impact, evidence and deadlines. Mark any assumption as `Assumption to validate:`.

**Questions for leadership**
A numbered list of up to three questions that can be answered in a meeting.

Do not recommend compensation, contractual action, legal action, security classification or a public statement unless the supplied material already presents it as an approved option. Do not turn a suspected cause into a fact.

Audit the **Leadership escalation summary** below against its source material. Produce an **Escalation send-check** for the support manager.

Summary to audit: [paste the escalation summary]
Source material: [paste tickets, account notes, internal updates, fact record and timeline]

Return these sections in Markdown:

**Send status**
Choose exactly one: `Ready to send`, `Ready after named corrections`, or `Do not send yet`. Give one sentence explaining the choice.

**Required fields check**
Use a table with columns: Required field | Present and clear? | Evidence-supported? | Correction needed.
Check: customer impact; evidence; actions already taken; decision needed; owner; deadline; current status; open questions.

**Unsupported or overstated claims**
List each claim in the summary that is not supported by the source, is stronger than the source, or lacks a source. Quote the claim and state the correction. Write `None found` if none.

**Material omissions**
List missing customer commitments, deadlines, affected users, blockers, conflicting accounts or hand-offs that a leader needs to see. Write `None found` if none.

**Final correction list**
Give numbered, paste-ready edits. Each edit must identify the section to change and replacement wording.

Treat absent evidence as absent. Do not fill gaps from typical support practice. If the summary names an owner or date not present in the source, flag it unless it is explicitly labelled `to confirm`.