SLA Breach Apology Writer

Create a working **sla breach apology writer** that solves the intent behind “sla breach apology prompt”. Begin by checking the supplied context for gaps that would materially change the result.

## Context to supply — SLA Breach Apology Writer
- [CUSTOMER_MESSAGE] — for SLA Breach Apology Writer, supply the relevant customer message. If unavailable, label [CUSTOMER_MESSAGE] `unknown`; never infer it.
- [POLICY] — for SLA Breach Apology Writer, supply the relevant policy. If unavailable, label [POLICY] `unknown`; never infer it.
- [URGENCY] — for SLA Breach Apology Writer, supply the relevant urgency. If unavailable, label [URGENCY] `unknown`; never infer it.
- [DESIRED_OUTCOME] — for SLA Breach Apology Writer, supply the relevant desired outcome. If unavailable, label [DESIRED_OUTCOME] `unknown`; never infer it.
- [PRODUCT_FACTS] — for SLA Breach Apology Writer, supply the relevant product facts. If unavailable, label [PRODUCT_FACTS] `unknown`; never infer it.
- [IMPACT] — for SLA Breach Apology Writer, supply the relevant impact. If unavailable, label [IMPACT] `unknown`; never infer it.
- [REQUIRED_POINTS] — for SLA Breach Apology Writer, supply the relevant required points. If unavailable, label [REQUIRED_POINTS] `unknown`; never infer it.
- [APPROVAL_LIMITS] — for SLA Breach Apology Writer, supply the relevant approval limits. If unavailable, label [APPROVAL_LIMITS] `unknown`; never infer it.

## Task procedure — SLA Breach Apology Writer
1. Draft only after locking the audience, purpose, facts, voice, and desired action.
2. Deliver a publishable version plus a compact rationale for important choices.
3. Check policy, account facts, prior troubleshooting, and agent authority before promising an outcome.
4. Separate customer-facing language from internal diagnosis and escalation notes.
5. Identify the actual issue and emotional temperature.
6. Use only verified product and account facts.
7. Apply policy without sounding evasive.
8. Give steps in the safest practical order.
9. Boundary for SLA Breach Apology Writer: Do not invent account actions, refunds, policy exceptions, resolution times, diagnoses, or completed fixes.

## Present the result — SLA Breach Apology Writer
- **Issue summary for SLA Breach Apology Writer** — sla breach apology prompt evidence → SLA Breach Apology Writer; omit preamble.
- **Customer-ready reply for SLA Breach Apology Writer** — material inputs for SLA Breach Apology Writer, each connected to sla breach apology prompt.
- **Troubleshooting step for SLA Breach Apology Writer** — ready-to-use SLA Breach Apology Writer, formatted for sla breach apology prompt.
- **Internal note for SLA Breach Apology Writer** — SLA Breach Apology Writer weak points, unknowns, and sla breach apology prompt limits.
- **Escalation trigger for SLA Breach Apology Writer** — sla breach apology prompt → verify SLA Breach Apology Writer before use.

## Before finishing — SLA Breach Apology Writer
Finish with a compact integrity check for SLA Breach Apology Writer: factual support, task fit, internal consistency, usability, and required human review.