Customers
AuraScore 81/100

Medical Device Critical Downtime Customer Assurance Framework

Construct a high-stakes customer communication framework for hospital leadership during acute medical diagnostic system failures.

Deploy this framework when hospital operations and clinical diagnostics face unplanned hardware or software outages. It helps enterprise healthcare account directors coordinate transparent, reassuring customer communications that preserve institutional partnerships.

Template

Role: Enterprise Customer Success and Clinical Escalations Director for acute-care medical technology systems.

Context

  • Hospital tier and institutional setting: {{hospital_tier}}
  • Affected capital diagnostic modality: {{affected_diagnostic_modality}}
  • Contractual service breach timeframe: {{sla_breach_window}}
  • Patient workflow disruption level: {{clinical_impact_severity}}
  • Engineering containment and repair roadmap: {{technical_mitigation_plan}}
  • Contractual remedies and credits available: {{commercial_remedy_options}}

Task

Architect an incident response customer communication framework that provides hospital C-suite executives, biomedical engineering directors, and clinical department heads with transparent, real-time status updates, mitigates operational disruption, and prevents commercial relationship churn.

Method

  1. Segment recipient stakeholders into executive, clinical, and biomedical engineering tiers based on {{hospital_tier}}.
  2. Translate the engineering specifics in {{technical_mitigation_plan}} into non-defensive, clinically meaningful diagnostic milestones.
  3. Map notification intervals directly against {{sla_breach_window}} to manage executive expectations.
  4. Draft standardized impact acknowledgment statements addressing {{clinical_impact_severity}} without admitting legal liability.
  5. Structure multi-tiered escalation email templates tailored for emergency triage, root-cause transparency, and return-to-service.
  6. Incorporate actionable temporary patient diversion strategies and mobile diagnostic loaner deployment schedules.
  7. Detail the mechanism for invoking {{commercial_remedy_options}} transparently during post-incident debriefing.

Constraints

  • Messaging MUST prioritize patient safety and clinical continuity above commercial protectionism.
  • The framework MUST NOT make definitive restoration guarantees that contradict {{technical_mitigation_plan}}.
  • Technical jargon must be translated into clinical throughput impact for departmental chairs.
  • Every stage must assign a clear single point of contact (SPOC) with direct phone escalation paths.

Output format

Generate an incident communication framework divided into:

  1. Stakeholder Segmentation and Notification Matrix (Role, Channel, Cadence, Primary Information Need)
  2. Incident Escalation Lifecycle (Initial Alert, Containment Update, Resolution Confirmation, Post-Mortem)
  3. Three Complete Template Blueprints (T+0 Immediate Alert, T+4 Progress/Alternative Routing, Post-Resolution Assurance)
  4. Remediation and Commercial Alignment Protocols (Credit processing, preventative maintenance guarantees)
  5. Account Relationship Recovery Checklist (Post-incident governance reviews)

Self-review

  • Are the tone and clinical context appropriately calibrated to the severity in {{clinical_impact_severity}}?
  • Does the framework provide distinct messaging for biomedical engineering versus C-suite hospital stakeholders?
  • Are commercial remedies in {{commercial_remedy_options}} introduced at the appropriate post-resolution phase?
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.

emails
emails-customers
healthcare-life-sciences
medtech
incident-management
customer-success