Clients
AuraScore 83/100

Proactive Product Quality Resolution Script

Generate an empathetic, solution-focused email script to notify premium retail clients of an urgent product batch defect or recall.

Use this template when an operational defect or recall affects high-value retail purchases. It produces a clear notification script that de-escalates client frustration, outlines remediation steps, and preserves brand equity.

Template

Role: Senior Director of Customer Experience in luxury retail and consumer goods.

Context

  • Brand identity: {{brand_name}}
  • Recipient name: {{client_name}}
  • Impacted item: {{impacted_product}}
  • Root cause explanation: {{defect_reason}}
  • Compensation or remediation offer: {{remedy_offer}}
  • Direct escalation contact: {{support_channel}}

Task

Draft a high-touch email outreach script to notify {{client_name}} about an issue with {{impacted_product}}, balancing transparency with brand reassurance and a frictionless resolution path.

Method

  1. Review {{impacted_product}} details and synthesize the technical issue described in {{defect_reason}} into transparent, client-friendly language.
  2. Formulate three distinct subject lines varying in tone from direct operational notice to premium client care.
  3. Draft an empathetic opening that directly addresses {{client_name}} and acknowledges their relationship with {{brand_name}}.
  4. Explain the issue concisely without defensive jargon, taking full institutional accountability.
  5. Present the immediate corrective action being taken on their behalf.
  6. Detail the exact steps required to claim {{remedy_offer}} with minimal client effort.
  7. Provide specific guidance on item disposal, return logistics, or courier pick-up.
  8. Include immediate escalation options through {{support_channel}}.

Constraints

  • MUST maintain an apologetic, transparent, and service-oriented tone throughout.
  • MUST NOT shift blame to third-party suppliers or supply chain logistics.
  • Provide clear visual formatting with distinct script placeholders.
  • Word count for the primary email script must be between 180 and 260 words.

Output format

  • Section 1: Subject Line Options (3 distinct options)
  • Section 2: Primary Email Script (greeting to sign-off, ready to send)
  • Section 3: Follow-up Contingency Script (short 75-word bump script if client does not respond in 48 hours)

Self-review

  • Does the script explicitly detail {{remedy_offer}} without requiring excessive effort from {{client_name}}?
  • Is the explanation of {{defect_reason}} clear and non-technical?
  • Are all 6 contextual variables correctly woven into the script?
AuraScore breakdown
83/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency9/10 · Strong

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

emails
emails-clients
retail-consumer-goods
customer-care
retail-support
crisis-response