Create a Customer-Retention Response

#CONTEXT:
Create a customer-retention response draft for named-human review. Use only the supplied verified facts, policy, approved retention boundaries, ownership, and contact facts. The output is not approval to make an offer or contact the customer.

#INPUTS:
- Verified incident facts and evidence references: [INCIDENT FACTS]
- Customer-reported and independently verified impact: [CUSTOMER IMPACT]
- Current applicable policy with source and effective date: [APPLICABLE POLICY]
- Retention options, eligibility rules, amounts, limits, and prohibited claims explicitly approved for consideration: [APPROVED RETENTION BOUNDARIES]
- Current support, account, financial, and escalation ownership: [CURRENT OWNERSHIP]
- Verified customer name, case reference, channel, consent, and contact history: [CUSTOMER CONTACT FACTS]
- Approved company tone and style constraints: [COMPANY TONE]
- Named human responsible for reviewing the exact draft: [RESPONSE REVIEWER]

#INSTRUCTIONS:
1. Separate verified facts, customer-reported statements, conflicts, and Unknown items. Do not place unsupported details in the response draft.
2. Do not invent, infer, or fabricate policy, eligibility, customer facts, outcomes, contact consent, offers, amounts, dates, fault, or liability.
3. Determine whether the supplied evidence matches an exact approved retention boundary. If any required fact, authority, or eligibility rule is missing or conflicting, mark the option Unknown and draft an internal escalation note instead of an offer.
4. Draft an empathetic acknowledgment of the verified experience without admitting fault or liability and without mirroring hostile language.
5. Include a retention option only when the supplied boundary explicitly supports it. Quote its approved terms exactly and label it pending named-human approval; do not enhance, combine, or imply other value.
6. Do not issue, apply, process, or promise a refund, reimbursement, credit, compensation, retention offer, discount, concession, exception, waiver, guarantee, or outcome.
7. Do not send, publish, email, message, call, contact, notify, schedule, cancel, route, assign, close, resolve, or update any customer, ticket, account, record, or system.
8. Use only authorized customer data and authorized support data in an approved AI workspace or approved AI vendor. Minimize the data and redact or omit unnecessary personal, sensitive, or confidential data. Follow company retention and vendor policy.
9. A named human owner must approve every refund, credit, or compensation decision before action. A named human owner and legal counsel must approve every admission of fault or liability before action. A named human owner must approve every retention offer, discount, or policy exception before action. A named human owner must approve every external communication, sending action, or customer contact before action. A named human owner must approve every ticket, system, account, or record change or mutation before action.

#RESPONSE FORMAT:
## Evidence, conflicts, and Unknowns
| Item | Status | Supplied evidence | Missing or conflicting evidence |
|---|---|---|---|

## Retention-boundary check
- Exact approved rule or Unknown
- Eligibility evidence or Unknown
- Option and terms permitted for consideration
- Named approver and prohibited variations

## DRAFT — HUMAN REVIEW REQUIRED
- Subject
- Customer acknowledgment
- Verified resolution context
- Approved option, only if supported
- Proposed next step without promise

## Human approval checklist
- Facts, policy, eligibility, and consent verified
- Exact option and terms separately approved
- No unsupported admission, promise, exception, or outcome
- External communication and all live changes separately approved