Play 8 Complete Implementation Guide

You need an emergency response system that doesn't rely on someone checking their email at 2 AM. Play 8 automates the entire chain: detect VIP involvement, score urgency, acknowledge immediately, escalate via SMS, and notify backups. This guide walks you through building that system from scratch.

Start by defining who gets priority treatment. This isn't about ego. It's about protecting revenue, reputation, and legal exposure.

Define VIP Criteria with Specific Thresholds

Create three tiers:

Tier 1 (Critical)

• C-suite executives and equity partners
• Clients generating $500K+ annual revenue
• Anyone with signing authority over $100K
• Board members and major investors

Tier 2 (High Priority)

• Directors and senior managers
• Clients in the $100K-$500K range
• Department heads with P&L responsibility
• Anyone handling regulated data (HIPAA, SOC 2, attorney-client privilege)

Tier 3 (Standard Priority)

• All other employees and clients

Document these criteria in a shared spreadsheet or wiki. Include the business justification for each tier. When someone questions why Partner X gets faster response than Manager Y, you need a defensible answer.

Automate VIP Identification in Your Systems

Manual VIP lists go stale in weeks. Automate the tagging process:

In Your CRM

(Salesforce, HubSpot, etc.)

1. Create a custom field: "VIP_Tier" (values: 1, 2, 3, or blank)
2. Set up workflow rules: If Annual_Revenue > $500K, set VIP_Tier = 1
3. Add a validation rule: VIP_Tier cannot be changed without VP approval
4. Schedule a monthly report of all Tier 1 and Tier 2 contacts for review

In Your HRIS (BambooHR, Workday, etc.)

1. Tag job titles containing "Partner", "Chief", "VP", or "Director"
2. Flag anyone with "Signature Authority" > $100K in their profile
3. Export this list weekly to your incident management system

In Your Email System (Gmail, Outlook)

1. Create a shared label or category: "VIP_Tier1", "VIP_Tier2"
2. Use email rules to auto-tag messages from known VIP domains
3. Sync these tags to your monitoring tools (see Urgency Analysis section)

Maintain VIP Profiles with Contact Hierarchies

For each Tier 1 VIP, create a contact card with:

• Primary mobile number (verified quarterly)
• Secondary contact (assistant, spouse, or business partner)
• Preferred communication method (call, SMS, or both)
• Escalation contact (who to notify if VIP is unreachable after 15 minutes)
• Special instructions (e.g., "Never call between 6-8 PM - family dinner")

Store these in a secure, shared location. Google Sheets with restricted access works. So does a dedicated field in your CRM

. The key is that your on-call team can access it at 3 AM without hunting through email threads.

You need a scoring system that runs without human judgment. Define the rules once, then let the system apply them consistently.

Build Your Urgency Scoring Matrix

Assign points across five dimensions:

VIP Involvement (0-3 points)

• Tier 1 VIP: 3 points
• Tier 2 VIP: 2 points
• Tier 3 VIP: 1 point
• Non-VIP: 0 points

Keyword Severity (0-3 points)

• Critical keywords ("breach", "lawsuit", "injured", "threat"): 3 points
• High-risk keywords ("urgent", "emergency", "deadline", "complaint"): 2 points
• Moderate keywords ("problem", "issue", "concern"): 1 point
• No keywords: 0 points

Time Sensitivity (0-2 points)

• Explicit deadline within 4 hours: 2 points
• Deadline within 24 hours: 1 point
• No deadline mentioned: 0 points

Financial Impact (0-2 points)

• Mentions dollar amounts over $100K: 2 points
• Mentions dollar amounts $10K-$100K: 1 point
• No financial mention: 0 points

Communication Pattern (0-2 points)

• Multiple messages in 30 minutes: 2 points
• Marked "urgent" or "high priority": 1 point
• Standard communication: 0 points

Total Score: 0-12 points

Configure Monitoring Tools to Calculate Scores

Option A: Use Zapier + Gmail/Outlook

1. Create a Zapier trigger: New email from VIP list
2. Add a filter: Email body contains urgency keywords (use regex: breach|lawsuit|injured|threat|urgent|emergency)
3. Add a Code step (Python or JavaScript) to calculate the urgency score
4. Store the score in a Google Sheet with timestamp, sender, subject, and score

Option B: Use Make.com (formerly Integromat)

1. Set up a Gmail/Outlook watch trigger for new emails
2. Add a router with multiple paths based on sender domain
3. Use text parser to extract keywords and dollar amounts
4. Calculate score using Make's built-in formula tools
5. Send high-scoring incidents to your escalation workflow

Option C: Use a Dedicated Tool (PagerDuty, Opsgenie)

1. Configure email integration to forward all VIP emails
2. Set up event rules to parse email content
3. Define severity levels based on your scoring matrix
4. Route high-severity incidents to on-call schedules

Set Escalation Thresholds

Define three action levels:

Score 0-4 (Monitor)

• Log the incident
• No immediate action required
• Review in next business day standup

Score 5-8 (Respond)

• Send acknowledgment to VIP within 15 minutes
• Assign to on-call team member
• Resolve within 4 hours

Score 9-12 (Escalate)

• Trigger full emergency protocol (see next section)
• Notify backup contacts immediately
• Executive briefing within 1 hour

When a high-urgency incident (score 9+) is detected, the clock starts. Your system must acknowledge receipt before the VIP assumes you're ignoring them.

Configure Automated Acknowledgment Messages

SMS Template (for scores 9-12)

[FIRM_NAME] Emergency Response: We've received your urgent message regarding [SUBJECT_LINE]. Our team is mobilizing now. You will receive an update within 15 minutes. Reply STOP to cancel escalation. - [ON_CALL_NAME]

Email Template (for scores 5-8)

Subject: Acknowledged: [ORIGINAL_SUBJECT]

[VIP_NAME],

We've received your message and flagged it as high priority. [ON_CALL_NAME] from our team is reviewing now and will respond within 4 hours.

If this requires immediate attention, please call [EMERGENCY_NUMBER] or reply "URGENT" to this email.

- [FIRM_NAME] Response Team

Set Up SMS Delivery via Twilio

1. Create a Twilio account and purchase a phone number
2. In Zapier or Make.com, add a Twilio action: "Send SMS"
3. Configure the "To" field to pull from your VIP contact database
4. Set the "From" field to your Twilio number
5. Use the template above, with dynamic fields for [VIP_NAME], [SUBJECT_LINE], etc.
6. Add a 60-second delay, then check for VIP reply

Critical: Test this monthly. Send a test SMS to yourself and verify delivery time. Twilio occasionally has regional delays.

Handle Acknowledgment Failures

If the SMS fails to deliver (bad number, carrier block, etc.):

1. Immediately attempt email acknowledgment
2. Log the failure in your incident tracking system
3. Trigger a Slack alert to your operations channel: "SMS delivery failed for [VIP_NAME] - manual follow-up required"
4. Escalate to backup contact (see next section)

If the VIP doesn't reply within 15 minutes, or if the initial score is 11-12, escalate to your emergency response team.

Build Your On-Call Rotation

Define who's on-call and when:

Primary On-Call (24/7 coverage)

• Week 1: Operations Manager A
• Week 2: Operations Manager B
• Week 3: Senior Associate C
• Week 4: Operations Manager A (repeat)

Secondary On-Call (backup if primary doesn't respond in 5 minutes)

• Always: Director of Operations
• After-hours: Managing Partner (for Tier 1 VIPs only)

Store this schedule in PagerDuty, Opsgenie, or a shared Google Calendar with SMS reminders.

Configure Escalation SMS

Primary Escalation Template

EMERGENCY: Tier [VIP_TIER] incident detected. VIP: [VIP_NAME]. Subject: [SUBJECT_LINE]. Urgency Score: [SCORE]/12. No response to acknowledgment. Review now: [INCIDENT_LINK]. Reply ACK to claim.

Secondary Escalation Template (if primary doesn't ACK in 5 minutes)

ESCALATION: [PRIMARY_NAME] has not acknowledged Tier [VIP_TIER] incident. VIP: [VIP_NAME]. Score: [SCORE]/12. You are now primary responder. Details: [INCIDENT_LINK]. Reply ACK to claim.

Implement the Escalation Workflow

In Zapier:

1. After sending VIP acknowledgment, add a 15-minute delay
2. Check if VIP replied (use Gmail "Search Email" action)
3. If no reply, send Primary Escalation SMS to on-call person
4. Add a 5-minute delay
5. Check if on-call person replied "ACK"
6. If no ACK, send Secondary Escalation SMS to backup

In Make.com:

1. Use a "Sleep" module for 15 minutes after VIP acknowledgment
2. Add a Gmail "Search" module to check for VIP reply
3. Use a router: If no reply found, proceed to escalation path
4. Send SMS via Twilio to primary on-call
5. Add another "Sleep" for 5 minutes
6. Check for "ACK" reply in Twilio message logs
7. If no ACK, trigger secondary escalation

Even the best systems fail. Build redundancy into every step.

Define Backup Contacts for Each VIP

For every Tier 1 VIP, identify:

• Executive Assistant: First backup if VIP is unreachable
• Business Partner: Second backup (co-founder, co-managing partner, etc.)
• Emergency Contact: Personal contact (spouse, family member) for physical safety issues only

Store these in your VIP profile database with clear usage guidelines. Never contact a personal emergency contact for a business issue.

Configure Parallel Notifications for Critical Incidents

For urgency scores of 11-12, send simultaneous notifications:

1. VIP acknowledgment (SMS + email)
2. Primary on-call escalation (SMS)
3. Executive assistant notification (email with "URGENT" flag)
4. Slack alert to #emergency-response channel

This creates multiple paths to resolution. If SMS fails, email might work. If the on-call person is in a dead zone, the Slack alert reaches the broader team.

Set Up Email Backup for SMS Failures

In Zapier:

1. After attempting SMS delivery, add a "Twilio - Get Message" action
2. Check the "Status" field: If "failed" or "undelivered", proceed to backup
3. Send an email to the same recipient with subject line: "URGENT: SMS delivery failed - check immediately"
4. CC your operations team email address

In Make.com:

1. Use error handling on the Twilio SMS module
2. If error occurs, route to an email module
3. Send to the intended SMS recipient's email address
4. Log the failure in your incident tracking system

Create a Manual Escalation Procedure

Document the human fallback for when automation fails:

If you discover an unacknowledged emergency incident:

1. Call the VIP directly (use the number in their profile)
2. If no answer, call their executive assistant
3. If still no answer, call the primary on-call person
4. If on-call doesn't answer, call the secondary on-call
5. If no one answers, call the managing partner directly
6. Document every call attempt in the incident log

Print this procedure and post it in your operations area. When systems are down, people need a paper checklist.

Every emergency response generates data. Capture it systematically.

Set Up Your Incident Tracking System

Option A: Use a Spreadsheet

Create a Google Sheet with these columns:

• Timestamp (auto-populated)
• Incident ID (auto-generated: YYYYMMDD-###)
• VIP Name
• VIP Tier
• Urgency Score
• Initial Detection Method (email, phone, Slack, etc.)
• Acknowledgment Sent (Y/N, timestamp)
• VIP Response Time (minutes)
• Escalation Triggered (Y/N, timestamp)
• On-Call Person
• On-Call Response Time (minutes)
• Resolution Time (minutes)
• Resolution Summary (text field)
• Lessons Learned (text field)

Option B: Use a Dedicated Tool

• PagerDuty: Built-in incident tracking with timeline view
• Opsgenie: Incident logs with custom fields and reporting
• Jira Service Management: Full ticketing system with SLA tracking

Automate Incident Logging

In Zapier:

1. When urgency score is calculated, create a new row in your Google Sheet
2. Populate Timestamp, VIP Name, Tier, and Score automatically
3. When acknowledgment is sent, update the "Acknowledgment Sent" field
4. When VIP replies, calculate response time and update the sheet
5. When incident is resolved, prompt on-call person to fill in Resolution Summary

In Make.com:

1. Use Google Sheets "Add a Row" module when incident is detected
2. Use "Update a Row" module at each stage (acknowledgment, escalation, resolution)
3. Set up a scheduled scenario to run daily: Check for incidents older than 24 hours without resolution, send alert to operations manager

Generate Weekly Incident Reports

Every Monday morning, send a summary to your leadership team:

Report Template:

Emergency Response Summary: [DATE_RANGE]

Total Incidents: [COUNT]
- Tier 1: [COUNT] (avg response time: [MINUTES])
- Tier 2: [COUNT] (avg response time: [MINUTES])
- Tier 3: [COUNT] (avg response time: [MINUTES])

Escalations: [COUNT]
- Primary on-call response rate: [PERCENTAGE]
- Secondary escalations required: [COUNT]

System Performance:
- SMS delivery success rate: [PERCENTAGE]
- Average acknowledgment time: [MINUTES]
- Average resolution time: [HOURS]

Top Issues:
1. [ISSUE_CATEGORY]: [COUNT] incidents
2. [ISSUE_CATEGORY]: [COUNT] incidents
3. [ISSUE_CATEGORY]: [COUNT] incidents

Action Items:
- [SPECIFIC_IMPROVEMENT_NEEDED]
- [SPECIFIC_IMPROVEMENT_NEEDED]

Automate this report using Google Sheets formulas or a Zapier/Make.com scenario that runs every Monday at 8 AM.

Your emergency response system is only as good as your last test.

Run Monthly Fire Drills

First Monday of Every Month:

1. Send a test incident through your system (use a fake VIP email address)
2. Verify acknowledgment is sent within 60 seconds
3. Verify escalation SMS is sent after 15 minutes
4. Verify on-call person receives and acknowledges the alert
5. Document any failures or delays
6. Fix issues before the next real incident

Quarterly System Audits

Every Quarter:

1. Review all VIP profiles - update contact information
2. Test SMS delivery to every on-call person's phone
3. Verify Zapier/Make.com scenarios are still active (they sometimes pause due to errors)
4. Check Twilio account balance and add funds if needed
5. Review incident logs for patterns - are certain VIPs generating repeated incidents?
6. Update urgency scoring rules based on false positives/negatives

Annual Process Review

Once Per Year:

1. Interview your on-call team: What's working? What's frustrating?
2. Survey VI