Churn saves
AuraScore 81/100

Enterprise Freight Service Recovery and Contract Retention Appeal

Craft an executive-level retention email to save an enterprise shipper account after severe logistics SLA breaches.

Use this template when an enterprise freight client submits formal notice of intent to cancel or tender off lanes due to recurring operational failures. It generates a high-stakes, accountable executive response that acknowledges root causes, presents financial remedies, and secures a stay of termination.

Template

Role: Senior Director of Global Logistics Account Recovery with 18 years of experience resolving tier-one supply chain escalations.

Context

  • Shipper Organization: {{shipper_name}}
  • Freight Account Executive: {{freight_account_executive}}
  • Breached Performance Metrics: {{breached_sla_metrics}}
  • Root Cause Finding: {{root_cause_investigation}}
  • Proposed Commercial Concession: {{commercial_remedy_package}}
  • Operational Governance Mechanism: {{governance_cadence}}

Task

Draft a high-stakes executive retention email addressed to the chief supply chain officer at {{shipper_name}} that de-escalates pending cancellation, takes transparent accountability for operational failures, and secures an emergency 45-day operational stabilization window.

Method

  1. Analyze {{breached_sla_metrics}} against historical baseline transport KPIs to frame the disruption impact objectively.
  2. Incorporate the operational diagnostics from {{root_cause_investigation}} without deflecting carrier accountability.
  3. Position {{commercial_remedy_package}} as a binding commercial credit and rate concession tied to performance milestones.
  4. Detail the high-priority operational changes enacted across dispatch, yard management, and linehaul operations.
  5. Establish {{governance_cadence}} with named executive stakeholders to ensure daily transparency.
  6. Formulate a low-friction call to action requesting a 20-minute executive alignment call before formal tender offboarding.
  7. Calibrate the tone to balance rigorous professional humility with definitive operational authority.

Constraints

  • MUST maintain an executive tone that eliminates corporate platitudes, defensiveness, and generic apologies.
  • MUST explicitly detail the exact operational mechanics of {{commercial_remedy_package}}.
  • MUST NOT shift blame to external weather, third-party brokerage spot markets, or secondary subcontractors.
  • Word count MUST remain between 350 and 500 words.

Output format

Provide the complete email draft structured into the following distinct sections:

  • Subject Line (3 high-impact options under 60 characters)
  • Executive Salutation
  • Section 1: Direct Accountability & Disruption Acknowledgment
  • Section 2: Root-Cause Remediation & Process Restructure
  • Section 3: Commercial Concession & Performance Guarantee Terms
  • Section 4: Proposed Governance Cadence & Immediate Next Step
  • Professional Sign-off from {{freight_account_executive}}

Self-review

  • Does the email directly address {{breached_sla_metrics}} without obfuscation?
  • Is {{root_cause_investigation}} translated into tangible preventative controls?
  • Is the proposed call-to-action low friction while demanding executive-level commitment?
AuraScore breakdown
81/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 engineering12/12 · Strong

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 efficiency5/10 · Thin

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.

support-success
support-churn
transport-logistics
churn-save
freight
sla-recovery