VIP Escalation White-Glove Service Playbook
Create a premium support escalation playbook for high-value accounts, urgent incidents, and executive-facing customer situations.
Prompt Template
You are a head of support designing a VIP escalation playbook. Business type: [SaaS / ecommerce / agency / service business] VIP customer definition: [ARR tier, enterprise account, influencer, strategic partner, etc.] Common escalation types: [outage, billing dispute, delayed delivery, executive complaint, security concern] Support team structure: [frontline, specialists, CSMs, engineering, leadership] Response expectations: [first response SLA, update cadence, resolution target] Brand tone: [formal, high-touch, empathetic, concise] Create: 1. **Escalation criteria** — what qualifies as VIP or executive priority 2. **Response workflow** — who owns what at each stage 3. **Communication templates** — initial response, progress update, resolution, executive apology if needed 4. **Internal war-room checklist** — facts, stakeholders, and decision points 5. **Recovery actions** — service credits, concierge help, follow-up reviews, etc. 6. **Post-incident review template** — what to document and how to prevent repeats Optimize for calm, speed, accountability, and preserving trust under pressure.
Example Output
Escalation Criteria
A ticket is VIP priority if it affects an account above $50K ARR, involves an executive stakeholder, or blocks a launch, payment, or contractual deliverable.
Workflow
- Frontline marks VIP and pages escalation lead within 10 minutes
- Escalation lead opens internal channel and assigns tech owner, comms owner, and account owner
- Customer receives named-contact reply within 15 minutes
- Updates go out every 30 minutes until stabilized
Initial Response Template
'I’m the escalation lead on your case and I’m staying with this until we have clarity. We’ve pulled in [team/function], we’re investigating [known issue], and your next update will arrive by [time].'
Tips for Best Results
- 💡Define VIP in operational terms, not vibes, revenue, account tier, event criticality, or executive involvement.
- 💡Ask for update cadence rules so customers never wonder whether the team disappeared.
- 💡Include recovery actions in advance, teams under pressure make worse decisions when inventing compensation on the fly.
- 💡Request an internal checklist so engineering, support, and customer success stay aligned.
Related Prompts
Customer Complaint Response Template
Write a professional, empathetic customer complaint response that resolves issues and preserves the relationship.
Help Documentation Writer
Write clear, user-friendly help articles and documentation that reduce support tickets and improve self-service.
Support Ticket Triage and Response
Triage incoming support tickets by priority and generate initial responses for common issue types.