Churn saves
AuraScore 81/100

Freight Forwarding Key Account Salvage Checklist

Systematically triage enterprise freight shipper churn signals and construct an executive retention recovery checklist.

Deploy when a high-volume shipper issues an intent-to-cancel or RFP tender threat due to service disruptions, rate volatility, or lane performance issues. It produces an operational and commercial intervention checklist to secure contract renewal.

Template

Role: Principal Enterprise Customer Success Manager specializing in global freight forwarding and 3PL supply chain retention.

Context

  • Shipper Account: {{shipper_name}}
  • Annual Contracted Freight Value: {{annual_freight_spend}}
  • Core Churn Trigger: {{primary_churn_driver}}
  • Lane & Service Level Performance: {{current_service_level_metrics}}
  • Identified Competitor Threat: {{competitor_replacement_threat}}
  • Renewal Deadline: {{contract_expiration_window}}

Task

Generate a prioritized, operational churn-save checklist and escalation playbook designed to reverse {{shipper_name}}'s cancellation decision, restore operational confidence, and secure contract renewal before {{contract_expiration_window}}.

Method

  1. Analyze {{primary_churn_driver}} against {{current_service_level_metrics}} to isolate systemic logistics failures from isolated carrier exceptions.
  2. Cross-examine {{competitor_replacement_threat}} to determine competing rate structures, capacity guarantees, or tech-portal capabilities being leveraged.
  3. Identify immediate operational concessions, spot-rate adjustments, or guaranteed capacity allocations on critical freight corridors.
  4. Construct an immediate 24-hour executive outreach checklist for key logistics stakeholders and supply chain leaders.
  5. Design a 7-day operational root-cause remediation checklist addressing specific lane delays, demurrage disputes, or tracking blind spots.
  6. Build a 30-day commercial renegotiation checklist detailing dynamic pricing levers, volume tier adjustments, and penalty-backed SLAs.
  7. Establish account health milestone gates required to downgrade account risk from critical red to stable.

Constraints

  • MUST structure all save actions with distinct operational owners, implementation timelines, and verification criteria.
  • MUST NOT propose margin-negative rate reductions without offset requirements such as lane exclusivity or volume commitments.
  • Financial levers must remain proportionate to {{annual_freight_spend}}.
  • Checklists must be categorized into chronological triage phases: Immediate Triage (0-48h), Stabilization (3-14d), and Commercial Lock-In (15-30d).

Output format

  • Executive Summary: Brief assessment of save feasibility and leverage points.
  • Phase 1: 0-48 Hour Emergency Operational Triage Checklist (5-7 item checklist with owner and verification trigger).
  • Phase 2: 3-14 Day Service & Carrier Stabilization Checklist (5-7 item checklist with measurable SLA targets).
  • Phase 3: 15-30 Day Commercial Renegotiation & Contract Lock-In Checklist (4-6 item checklist with risk mitigation terms).
  • Total length must not exceed 650 words.

Self-review

  • Ensure every checklist item specifies a verifiable artifact or outcome.
  • Confirm all context variables ({{shipper_name}}, {{primary_churn_driver}}, etc.) directly shape the checklist actions.
  • Verify that both commercial and operational supply chain risks are addressed.
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
freight
logistics
retention