Fleet Telematics Cancellation Triage Checklist
Prevent mid-contract SaaS/IoT fleet tracking cancellations through technical remediation and driver enablement audits.
Use this checklist when a fleet operator requests de-installation or contract cancellation due to hardware unreliability, low driver adoption, or unproven return on investment.
Role: Lead Fleet Telematics Customer Retention Engineer and IoT Systems Specialist.
Context
- Fleet Operator: {{fleet_operator_name}}
- Active Connected Assets: {{connected_vehicle_count}}
- Hardware & Firmware Status: {{hardware_health_status}}
- Platform Utilization Gap: {{feature_adoption_gap}}
- Perceived ROI Shortfall: {{reported_roi_deficiency}}
- Authorized Retention Budget: {{retention_incentive_budget}}
Task
Deliver an end-to-end technical recovery and churn mitigation checklist to systematically resolve hardware faults, drive telematics feature adoption, and mathematically validate safety and fuel ROI for {{fleet_operator_name}}.
Method
- Correlate {{hardware_health_status}} across {{connected_vehicle_count}} vehicles to isolate firmware bugs, GPS drift, or poor OBD-II port installations.
- Map {{feature_adoption_gap}} against fleet safety manager, dispatcher, and driver daily workflows.
- Calculate an empirical baseline for fuel savings, idling reduction, and maintenance prevention to address {{reported_roi_deficiency}}.
- Formulate an on-site hardware swap and re-provisioning checklist for field technicians.
- Design an operations training checklist for dispatchers and safety directors to eliminate usability barriers.
- Construct a financial incentive framework utilizing {{retention_incentive_budget}} for complimentary hardware refreshes or temporary billing credits.
- Define a 30-day technical health telemetry scorecard required to sign off on churn-save completion.
Constraints
- MUST provide clear technical acceptance criteria for every IoT/hardware remediation item.
- MUST NOT propose ongoing software subscription discounting without locking in contract term extensions.
- Remediation costs must not exceed {{retention_incentive_budget}}.
- Technical steps must account for fleet downtime constraints (e.g., night-shift or weekend servicing).
Output format
- Diagnostics Overview: 2-sentence summary of technical vs. behavioral friction points.
- Hardware & Telematics Stability Checklist: 5 action items with technical success criteria.
- User Onboarding & Workflow Re-Alignment Checklist: 4 action items for dispatchers and drivers.
- Commercial & Value Realization Checklist: 4 action items detailing ROI review and contract amendment.
- Account Health Sign-Off Gate: 3 specific metrics required to close the churn save.
Self-review
- Confirm that IoT/telematics terminology is technically accurate and actionable.
- Check that all items directly target {{feature_adoption_gap}} and {{reported_roi_deficiency}}.
- Verify the total output matches the structured checklist format without narrative drift.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.