Quick Check: Who’s in the Room?

• Which best describes your organization? Options: K–12 school district, Individual K–12 campus, University / higher education, County / city government, Special district (transit, health, etc.), Other
• What is your role and primary responsibility for emergency communications?
• How many people and physical locations does an alert typically need to reach for your organization? Options: <1,000 people / single site, 1,000–5,000 / multi-site, 5,000–20,000 / campus or district, 20,000+ / regional system, Not sure
• Are you currently operating under any legal, state, or federal mandate that requires mass notification changes? Options: Yes — active mandate with deadline, Under review or audit, No mandate but considering change, Unsure
• If there is a mandate or timeline, briefly describe the requirement and key dates.

If an Alert Took Too Long, What Did You Lose?

• Think of the last time an alert didn’t get out fast enough — who was harmed and how did it change the outcome?
• How often do you experience incidents or near-misses where notification speed or reach was a problem? Options: Multiple times a year, Once a year, Every few years, Never, only theoretical
• For a recent incident, map the timeline from detection to first notification and tell us what specifically broke down.
• When notifications failed, how did students, staff, or the public react emotionally and operationally?
• After these events, how did your leadership respond—immediate change, a review, or acceptance of the status quo? Options: Demanded immediate change, Launched formal review, Minor adjustments only, No action taken, Other
• How long has the pattern of notification gaps or delays been happening in your environment? Options: Months, 1–2 years, 3–5 years, More than 5 years

What's the Hard Truth About Your Contact Data?

• If 20% of your campus can’t be reached right now, who are they and why are they unreachable?
• Which systems feed your contact database today? Options: Student Information System (SIS), HR / Payroll, Active Directory / Identity Provider, Parent/guardian portals, Manual spreadsheets, Third-party vendors, Other
• How often do those sources sync into your alerting system? Options: Real-time / event-driven, Daily, Weekly, Monthly, Manual / ad hoc, Unknown
• Estimate the percent of your contact records you believe are outdated, missing, or duplicated. Options: <5%, 5–15%, 15–30%, 30–50%, >50%
• Who is accountable for contact data accuracy and what process is followed when problems are discovered?
• If we could automate one part of your contact hygiene to increase confidence fastest, which would it be? Options: Real-time SIS/HR sync, Automated parent/student device verification, De-duplication and identity resolution, Consent and opt-in automation, Other

Where Do People Freeze or Misstep During an Emergency?

• When seconds matter, where do your people actually get stuck—technology, decision paralysis, unclear roles, or something else?
• Who is authorized to send the very first alert in your organization? Options: Single designated person, Small designated team, Any on-duty officer/leader, Principal/site leader only, Other
• How comfortable are your primary users with activating multi-channel alerts while under stress? Options: Very comfortable, Somewhat comfortable, Not comfortable, Never trained
• How frequently do you run live activation drills that force decision-making under realistic stress? Options: Monthly, Quarterly, Bi-annually, Annually, Never
• Have false alarms or overly-broad alerts created hesitation or notification fatigue? Tell us one example and its impact.
• Which activation tasks do people most often get wrong (pick up to three)? Options: Selecting correct channels, Targeting the right building/zone, Editing templated message content, Escalation sequencing, Hardware activation (panic buttons/PA), Other

How Fast and Complete Should 'Good' Be?

• If you had to write a non-negotiable SLA for alerts, what would it demand and why would that be acceptable to leadership?
• Which delivery target matters most to you for first-wave alerts? Options: <15 seconds, <30 seconds, <60 seconds, <2 minutes, Other
• Which channels must be included in that first wave (choose all that apply)? Options: SMS / text, Phone call, App push, Email, PA system override, Digital signage, Social media, Other
• Do you require segmentation by room, building, floor, or zone? Options: Per-room, Per-floor, Per-building, By-campus/zone only, Not required, Other
• What acceptance criteria should define a successful live-test (please include measurable thresholds)?
• Are there legal, union, or device-policy constraints that would limit push notifications to staff or students? Options: Yes — strict constraints, Some constraints to accommodate, No constraints, Unsure

What's at Risk When Integrations Break?

• If panic buttons, PA overrides, or contact syncs failed during an incident, what would you lose in the first 10 minutes?
• Which systems must integrate for you to consider the solution fully functional (select all that apply)? Options: SIS (student info), HR / Payroll, Active Directory / SSO, PA / Audio-visual systems, Digital signage, LMS, Access control / door hardware, Third-party drill / analytics vendors, Other
• Which of those integrations have caused problems in the past and what was the root cause?
• Do you currently have a tested fallback plan for when an integration or external dependency is down? Options: Yes — tested and documented, Yes — exists but untested, No formal fallback, Unknown
• Who on your team should be responsible for own­ing and troubleshooting each integration during rollout and ongoing operations?
• What uptime or maintenance-window expectations do you require for integrations? Options: 24/7 real-time sync, Business hours with after-hours support, Accept scheduled nightly maintenance, Other

Let's Draw the Path to a Confident Launch

• What would make you cancel a deployment at the last minute — technical risk, staffing, political pressure, or something else?
• What timeline are you aiming for from pilot to full deployment? Options: 2–4 weeks, 1–2 months, 3–4 months, 6+ months, Unsure
• Which stakeholders must sign off before go-live (select all who apply)? Options: Superintendent / President, Campus Police Chief, IT Director / CIO, Legal Counsel, Board / Trustees, Facilities Director, Other
• Which live-test metrics will convince leadership to move to production (pick up to three)? Options: % delivered within SLA, Successful PA override, Segmentation accuracy by building, Staff activation time under stress, No critical defects during test, Other
• What training format and cadence will best prepare staff to act under pressure? Options: In-person hands-on, Remote instructor-led, On-demand video, Tabletop exercises, Simulated live drills, Combination
• After launch, what ongoing support or testing cadence would make you feel confident (e.g., monthly automated tests, quarterly live-tests)? Options: Monthly automated tests, Quarterly live-tests, Annual full-scale drills, Ad-hoc after incidents, Continuous monitoring and alerts
• Are there any remaining concerns, political constraints, or red flags we should resolve before drafting a pilot scope?

Tell Me How You Do It Today

• In a few sentences, walk me through how you currently send a community-wide alert from decision to first delivery.
• Which channels do you actively use right now to reach people? Options: SMS/Text, Email, Voice call, Mobile app push, Digital signage, PA/PA override, Social media, Other
• Who is typically authorized to trigger an alert (roles or titles)? Options: Safety Coordinator, Campus Police Chief, Principal/Dean, IT Director, Superintendent, Facilities Manager, Other
• How often do you run notifications as tests versus live incidents? Options: Weekly, Monthly, Quarterly, Annually, Only after incidents, Never
• Describe the last time you ran a live incident or full-system test—what happened from activation to delivery?

If an Emergency Happened Right Now, Would We Notice the Flaws?

• Think back to the most recent incident where notifications didn’t go as planned—what was the single most surprising failure?
• Which of the following failure types have you experienced in real events or tests? Options: Delayed delivery, Partial audience reach, Wrong segment targeted, Integration failure (PA/signage/LMS), Operator error, Carrier throttling/dropped messages, Other
• When failures occurred, how did they affect people’s safety or operations (select all that apply)? Options: Delayed evacuation, Confusion among staff, False reassurance, Regulatory escalation, Public backlash/media attention, No measurable harm
• How long has this pattern of failures or surprises been happening? Options: Just started (past 3 months), 6–12 months, 1–3 years, Longstanding (3+ years)

Where Messages Hit Roadblocks

• Which integration points are fragile today and most likely to interrupt delivery? Options: PA/PA override, Digital signage, LMS (learning management), SIS (student information), HR/employee directory, SMS gateway/carrier, Email provider, Single Sign-On/AD, Other
• Of the integrations you selected, which one fails most often and why?
• How frequently do your contact and roster systems sync with your notification platform? Options: Real-time/API, Hourly, Daily, Weekly, Manual batch, No sync
• Who in your organization owns each integration (IT, Safety, Vendor, Third-party)? Options: IT, Safety/EM, Facilities, Vendor/3rd party, Shared ownership, Unclear
• When integrations fail, how quickly can you detect and recover (minutes/hours/days)? Options: Under 15 minutes, 15–60 minutes, 1–8 hours, More than 8 hours, Unknown

Who Are We Missing When It Matters

• How confident are you that your contact database can reach every person who needs to receive an alert? Options: Completely confident (>98%), Mostly confident (90–98%), Somewhat confident (75–89%), Not confident (<75%)
• Which population segments do you struggle to reach or keep current? Options: Students, Parents/guardians, Faculty/staff, Contractors/visitors, Remote learners, Alumni, Other
• How are contact updates collected and verified (self-service portal, SIS sync, HR updates, manual entry)? Options: Self-service (user updates), SIS/HR sync (automated), Manual entry by staff, Third-party data provider, No consistent process
• When was the last full audit or reconciliation of your contact lists and what did it show? Options: Within 30 days, 30–90 days, 3–6 months, 6–12 months, Over a year, Never done
• Tell a short story of a time when outdated or missing contact info caused a near-miss or problem.

Activation Under Stress: Who Freezes and Why?

• When an incident escalates, what’s the single biggest human obstacle between decision and alert activation?
• Do your operators follow a written playbook during activations? Options: Detailed scripted playbook, High-level checklist, Ad-hoc notes, No playbook
• How often do you train or run drills specifically on alert activation and who participates? Options: Weekly, Monthly, Quarterly, Annually, Never
• During recent drills or incidents, what mistakes or hesitations have you observed operators make?
• How emotionally prepared do operators feel during tests—calm, pressured but effective, or overwhelmed? Options: Calm and confident, Pressured but effective, Often overwhelmed, Depends on scenario

Technical Bottlenecks: Where Speed Loses Ground

• We say '60 seconds matters'—what delivery time do you realistically need for a critical alert to be acceptable? Options: Under 30 seconds, Under 60 seconds, 1–3 minutes, 3–5 minutes, Other
• Are you meeting your delivery-time goals today across SMS, app push, email and PA? Please specify per channel.
• Which of these infrastructure limits have bitten you before? Options: Carrier rate limits, Local network congestion, Firewall or proxy blocking, API throttling, Hardware failures (PA/signage), Cloud provider outages, Other
• Do you have visibility into live delivery metrics (time-to-delivery, bounce rates, segment coverage) during an event? Options: Full real-time dashboard, Partial metrics delayed, Post-event reports only, None
• Have you ever conducted a full-scale load or stress test that simulated peak concurrent activations? If yes, what happened? Options: Yes—passed, Yes—failed, Planned but not executed, No

If Everything Worked Perfectly — What Would That Feel Like?

• Imagine an ideal notification: how quickly would every channel need to deliver to call it a success? Options: All within 30 seconds, All within 60 seconds, Most within 2 minutes, Other
• Which stakeholder groups need different acceptance criteria (e.g., board, superintendent, public safety, parents)? Options: Board/leadership, Superintendent/President, Campus/School Police, Teachers/Faculty, Parents/Guardians, Students, Public/Community
• What failure rate (messages undelivered or delayed) would be tolerable during a high-stakes incident? Options: <1%, 1–5%, 5–10%, >10%, I don't know
• What evidence or live-test result would make leadership comfortable trusting a new system? Options: Full-scale live exercise results, Independent third-party audit, SLA with penalties, Reference-site demonstration, Other
• Tell us one emotional outcome you want from a better system (e.g., confidence, less panic, faster reunification).

If We Had 48 Hours to Prove Your Biggest Worry, Where Would You Make Us Start?

• Which three buildings, campuses, or population segments should we prioritize for an initial proof test?
• Which data sources would you grant us access to for a diagnostic (SIS, HR roster, visitor logs, directory services)? Options: SIS, HR/Employee directory, Visitor management, Active Directory/SSO, Other
• Who are the essential people we must include in a 48-hour rapid test (titles/emails)?
• Are there compliance, union, or legal approvals that could block an urgent test or require special wording? Options: Yes—legal/compliance, Yes—union/collective bargaining, No known blockers, Unsure
• What time windows or calendar constraints make a live test realistic (e.g., after hours, semester break, specific weekdays)? Options: During school hours, After hours/evenings, Weekends, Semester break/holidays, Other

Start Here: Tell Us Who You Are (and What's Kept You Up Lately)

• What's your job title and primary responsibility for emergency notifications? Options: Safety Coordinator / Director, Campus Police Chief / Officer, Emergency Management Director, IT Director / Integrations Lead, Facilities / Operations, Communications / PR, Other
• Which sites or populations do you oversee? Options: Single K-12 school, School district (multiple buildings), Community college, University / multi-campus, Municipal / county agency, Other
• How long have you been responsible for alerting or emergency communications in this role? Options: Less than 6 months, 6–12 months, 1–3 years, 3–7 years, 7+ years
• When an incident happens, what worries you first—reach, speed, staff activation, data accuracy, or something else? Options: Speed of delivery, Completeness of reach, Staff hesitation/activation errors, Outdated contact data, Integration failures (PA, signage, LMS), Legal or compliance exposure, Other
• Have you experienced a real notification failure or been required to implement mass notification by mandate? If yes, briefly describe what happened. Options: Yes — incident described below, Yes — mandate triggered, No

When Seconds Matter: Where Do You Lose Ground?

• If you had to name the single most common way your current notification system fails during an incident, what would it be?
• How frequently do you see that failure surface during real events or drills? Options: Almost every activation, Often (multiple times per year), Occasionally (once or twice a year), Rarely, Never
• Which channels or components tend to break or underperform when it matters most? Options: SMS/text delivery, Voice calls, Mobile app push, Email, PA / overhead systems, Digital signage, Social media posting, Third-party integrations (LMS, HR, SIS), Other
• Describe the last time a notification underperformed: what was the timeline, who noticed, and what was the immediate impact?
• When that failure happens, how does it make leadership and your community feel (embarrassed, exposed, relieved someone fixed it, distrustful, other)? Options: Embarrassed, Exposed/vulnerable, Angry, Relieved if mitigated, Erodes trust, Other

Who Actually Pushes the Button — And Who Freezes?

• Who, in practice, is empowered to send an emergency alert today, and who typically ends up being the final approver? Options: Campus police, Safety director, Superintendent / President, Incident commander, Facilities, Communications/PR, Legal, Other
• How confident are you that those authorized people can be reached and will act within minutes during off-hours? Options: Highly confident, Somewhat confident, Not confident, We don't have a reliable contact method
• Give an example of a moment when human hesitation or unclear roles delayed an alert. Who hesitated, and why?
• Are there legal, union, or policy constraints that routinely slow activation (e.g., required sign-offs, announcement scripts, privacy checks)? Options: Yes — legal/compliance constraints, Yes — union/HR constraints, Yes — scripted message approval, No, Unsure
• Who would you nominate as the single ‘go/no-go’ decision-maker for a true emergency if you could design it ideally? Options: Campus police chief, Safety director, Incident commander, Superintendent/President, Emergency management director, Other

Where Your Data Lets People Down

• If you had to bet, what percentage of your community would receive an alert within 60 seconds today? Options: >95%, 80–95%, 60–79%, 40–59%, <40%, Unsure
• What systems feed your contact database right now? Options: Student Information System (SIS), HR / Payroll, Badge/access control, Parent/guardian portal, Voluntary app sign-ups, Third-party lists, Manual spreadsheets, Other
• How often are those feeds synced and validated? Options: Real-time/continuous, Daily, Weekly, Monthly, Ad-hoc/manual, Never/unknown
• Where do you see the biggest gaps (missing mobile numbers, opt-outs, carrier blocks, inaccurate building assignment, duplicate records)?
• Who on your team is accountable for contact data integrity and what tools/processes do they use? Options: IT / Integrations, Safety team, Communications, HR, Third-party vendor, No single owner

Imagine a Test That Feels Like the Real Thing

• When you run a live test today, does the experience reveal competence or chaos for end users and staff? Options: Mostly competence, Mixed — some chaos, Mostly chaotic, We don't run realistic tests
• Describe your last live-test: which channels were included, who ran it, and what delivery times or failures did you measure?
• Which acceptance thresholds would make you confident in a test (e.g., 60 seconds to 95% of mobile devices, multi-channel confirmation within 3 minutes)? Options: 60s to 95% mobile, 60s to 95% across channels, Multi-channel confirmation within 3 minutes, Per-building segmentation accuracy, Staff activation under stress validated
• How often do staff participate in stress-tested activation drills, and who is required to attend? Options: Weekly, Monthly, Quarterly, Annually, Rarely / ad-hoc
• What typically prevents you from running more realistic, disruptive tests (risk to operations, regulatory concerns, fear of causing panic, technical limits)?

What Would Truly Make You Sleep Better?

• If you could guarantee one thing when an incident occurs, what would it be (speed, reach, clarity of messaging, staff confidence, measurable audit trail, other)? Options: Delivery within 60 seconds, Reach all affected people, Clear, actionable messaging, Staff able to activate without errors, Complete audit and compliance logs, Other
• Which outcomes are non-negotiable versus ‘nice-to-have’? List up to three non-negotiables.
• What constraints must any solution respect (budget, privacy/FERPA/HIPAA, accessibility, union rules, procurement timelines)? Options: Budget limits, Privacy/regulatory constraints, Accessibility requirements, Union/HR rules, Procurement timelines, None
• How will you measure success after deployment (KPIs, timelines, owners)? Options: Delivery time SLA, Percentage reach, Staff activation time, Segmenting accuracy by building, Annual exercise pass/fail, Other

Readiness & Risks: If Integrations Fail on Day One, What Then?

• If an integration or contact sync failed on go-live day, what is your immediate fallback and how confident are you it would work? Options: Manual call tree, Static exported contact lists, Local PA only, Third-party backup vendor, No reliable fallback
• Do you have separate test environments and credentials for each integration (SIS, PA, signage, LMS, badge systems)? Options: Yes — for all systems, Yes — for some systems, No test environments, Unsure
• Can we get API access, integration docs, and a named technical contact for each system within our typical onboarding window? Options: Yes — ready now, Yes — will need coordination, No — requires procurement, Unsure
• Who holds the admin credentials and access levels for your critical endpoints, and how are those credentials provisioned to vendors? Options: IT holds admin access, Safety team holds access, Shared service desk, Vendor-managed, Credentials not centralized/unknown
• What is your current incident escalation plan for failed integrations or data corruption during deployment?
• What maximum allowable downtime or degraded capability would you tolerate during cutover (minutes/hours), and what is your rollback criteria? Options: <15 minutes, <1 hour, <4 hours, <24 hours, No tolerance — must be seamless

Go-Live Day: Who Calls It, Who Tests It, Who Owns Rollback?

• On the day we flip the switch, who has the final go/no-go authority? Options: Incident commander / safety director, Campus police chief, IT Director, Superintendent / President, Joint sign-off (list names)
• Who will own and execute the live-test acceptance checklist (multi-channel delivery, segmenting, staff activation) and who will record results? Options: Safety team, IT / Integrations, Vendor support, Communications/PR, Joint team
• What exact acceptance metrics must be met to call go-live successful (list thresholds and by whom they are validated)?
• If acceptance fails, what is the approved rollback or mitigation plan and who is authorized to execute it? Options: Rollback to previous system, Partial roll-forward (limiting channels), Pause and continue testing, Escalate to vendor/leadership
• How would you like post-go-live monitoring and incident communication to be handled in the first 72 hours? Options: Daily check-ins with vendor, Dedicated war room, Escalation only if issues, Full monitoring + hourly reports

Next Steps: Commitment, Timelines, and Who’s in the Room

• Realistically, what is your preferred timeline for finishing configuration, running acceptance tests, and going live? Options: 2–4 weeks, 4–8 weeks, 2–3 months, 3–6 months, Longer / TBD
• Who must be involved from your side during deployment (names and roles if possible)?
• What procurement, IT/security, or legal milestones could block the project if not addressed early? Options: Procurement approval, IT security review, Data sharing agreement, Union/HR sign-off, None known
• How would you prefer to run a final mutual-commit review—formal sign-off meeting, staged approvals, or pilot-first approach? Options: Formal sign-off meeting, Staged approvals, Pilot-first with phased rollout, Other
• Anything else we should know now that would change how we approach readiness, testing, or training for your organization?

A Quick Hello — Who Are You and What Keeps You Up at Night?

• Tell us your title, the organization you serve, and the top two responsibilities you own for emergency communications.
• How many physical sites/buildings and approximate total population (students + staff + visitors) are you responsible for notifying? Options: Single campus / <1,000 people, Multiple sites / 1–5k people, District / 5k–20k people, Large campus system / 20k–100k people, Regional/state agency / 100k+ people
• Which of these best describes your authority to trigger a mass alert today? Options: I can trigger alone immediately, I can trigger after supervisor approval, Legal or communications sign-off required, IT must perform the activation, Policy says 'call chain' or dispatcher only
• How recently have you had a real incident or near-miss that tested your notifications, and what happened in one sentence?

If This Happened Today, Where Would It Break First?

• Where do you believe the single largest weakness in your notification process lives right now?
• In the last incident or drill, how long did it take from confirmed threat to first person receiving a notification? Options: Under 60 seconds, 1–5 minutes, 5–15 minutes, 15–60 minutes, We didn't get any reliable timing data
• Which channels failed or underperformed during that event (select all that applied)? Options: SMS/text, Phone call/IVR, Email, Push notification/app, Digital signage, PA/PA override, Social media, Third-party integrations (e.g., LMS, access control)
• Describe one moment during that event when you or your team realized something important was broken—what did you see, hear, or feel?
• How often do you run full-scope live-tests that realistically simulate an emergency (including staff stress and multi-channel delivery)? Options: Monthly, Quarterly, Biannually, Annually, Rarely / never

Who Really Holds the Keys When Seconds Matter?

• Who are the decision-makers, approvers, and gatekeepers who must sign off before a notification plan, vendor, or a change to process is adopted?
• Which of the following stakeholder categories have veto power or strong influence over your emergency notification decisions? Options: Superintendent / President, Legal counsel, IT Director/CIO, Union/HR, Board of Trustees, State regulator / Mandating body, Public safety partner (police/fire)
• Are there any legal, regulatory, or state mandates we should know about that define minimum capabilities or timelines? Options: Yes — specific mandate exists, Relevant guidance but not prescriptive, No mandate, but internal policy exists, No known mandates
• How would you describe the political appetite for spending on this problem right now—urgent, willing with justification, resistant, or unknown? Options: Urgent — funding likely, Open if ROI/mandate justified, Resistant — budget constrained, Unclear / politics in flux

Where People Get Left Behind — Mapping Your Current State

• List the primary sources of contact data you rely on (student information system, HR, visitor logs, contractors, third-party vendors).
• How frequently do those contact sources synchronize with your emergency system today? Options: Real-time / API, Daily batch, Weekly, Monthly, Manual import only
• Which audience segmentation capabilities are essential for you (select all that matter)? Options: By building, By floor/wing, By classroom/department, By role (staff/student/visitor), By subscription preference (opt-in channels), By vulnerability or special needs
• Are there known pockets of people who are currently unreachable or unreliable (e.g., subcontractors, transient visitors, remote students)? Tell us who and why.
• What integrations are live today (check all that apply)? Options: PA / PA override, Digital signage, LMS/class roster, Access control / door locks, SIS / HR / ERP, Mass SMS vendor, SOC/dispatch console, None of the above

When the Human Element Fails — Activation and Training Reality

• If staff are under extreme stress, what is most likely to prevent an alert from being sent correctly? Options: Unclear roles, Complex activation UI, Lack of confidence/training, Authentication/access issues, Fear of false alarm repercussions
• How frequently do you run stress-based activation exercises that force staff to activate in real-time under pressure? Options: Monthly, Quarterly, Biannually, Annually, Never
• Describe a training or drill that went well—what behaviors did you see, and what made it successful?
• What workflows or checklists exist today for activation, escalation, and verification, and who maintains them?
• Who is responsible for keeping contact data current (IT, administration, HR, individual managers), and how is that responsibility enforced? Options: IT, HR, School admin / site admin, Individual managers/teachers, No clear owner

Demanding Outcomes — Your 60-Second Reality and Acceptance Criteria

• If you could define a single non-negotiable performance metric for an alert system, what would it be (for example: 60-second delivery to 95% of users)?
• Which measurable success signals should we track during acceptance tests (select all that apply)? Options: First delivery time (seconds), Percent delivered within target window, Channel delivery success rates, Per-building reach, Staff activation time, Two-way response rates
• What are must-have constraints for acceptance (e.g., no single point of failure, on-premise override, data residency, FERPA/HIPAA compliance)?
• What constitutes a failed acceptance test that would block go-live (select single most critical)? Options: >X% undelivered to primary channel, Inability to segment by building, Staff unable to activate reliably, Integration outages with PA or signage, Unacceptable latency under load
• How often do you want to run formal acceptance/live-test exercises after go-live? Options: Monthly, Quarterly, Biannually, Annually

Under the Hood — Technical Integrations and Single Points of Failure

• What integration endpoints must be guaranteed for launch (APIs, webhooks, SIP/PA interfaces, signage protocols), and which are currently unproven?
• How does your network and connectivity look at each site—are there bandwidth or cellular dead zones we should plan for? Options: Good wired and cellular, Limited wired, good cellular, Limited cellular in some zones, Significant connectivity gaps
• Which redundancy strategies are required or preferred (select all that apply)? Options: Dual-path delivery (cellular + IP), Local PA fallback, On-site hardware for offline mode, Alternate contact lists / manual failover, Cloud multi-region redundancy
• Who owns the responsibility for contact sync reconciliation if mismatches are found—IT, vendor, or your team? Options: IT, Vendor with data access, School admin team, Shared responsibility (specify below)
• If we surfaced a recurring integration failure during tests, what remediation timeline would be acceptable to you? Options: Immediate/within 24 hours, Within 3 business days, Within 2 weeks, Dependent on impact

Live-Test Design and Acceptance — What Will Make This Real?

• What realistic scenario(s) should we use for the live-test exercise(s) to validate delivery, segmentation, and staff activation?
• Which audiences must be included in the test (select all that apply)? Options: Entire population, By-building subset, Critical staff only, Visitors/contractors, Remote/online students
• What safeguards must be in place during a live-test to avoid public alarm or operational disruption? Options: Clear pre-notification and signage, Test prefix in messages, Designated test windows, Stakeholder sign-off prior to test, Fail-safe cancellation procedure
• Who must be present or on-call during acceptance tests (roles/titles), and who has final sign-off?
• If a live-test fails a critical metric, what is your preferred escalation path to resolution (immediate rollback, patch and retest, acceptance with conditions)? Options: Immediate rollback and investigation, Patch and retest same week, Accept with mitigation plan, Escalate to executive sponsors

Politics, Budgets, and the Unseen Roadblocks

• Who or what is most likely to block procurement or delay deployment (e.g., unions, board budgets, IT policy, legal), and why?
• How is a purchase like this typically funded in your organization? Options: Operational budget (annual), Capital expenditure (one-time), Grant or state funding, Combination, Not yet identified
• Are there procurement constraints we should plan for (vendor vetting, background checks, RFP cycles, minority vendor requirements)? Options: Yes — formal RFP required, Restricted vendor list, Background/security vetting required, No major procurement constraints
• What timeline pressures exist—any upcoming audits, legislative deadlines, or seasonal events that force a go-live date?
• What would make leadership comfortable signing off today (examples: vendor references, pilot results, liability protections)?

Your Minimum Viable Launch — Keeping It Small but Bulletproof

• If we scoped a minimal pilot to prove the most critical outcomes, which capabilities must it include? Options: Native SMS + app push, Per-building segmentation, PA/signage integration, Contact sync automation, Staff activation training
• How long of a pilot would you accept before you decide to expand or go district/campus-wide? Options: 1 week, 2–4 weeks, 1–3 months, Longer than 3 months
• What internal evidence (metrics, stakeholder feedback) will convince you the pilot succeeded?
• Who should own the pilot project from your side, and who will be our primary technical contact?
• What’s an acceptable go/no-go decision date for you given current pressures? Options: Within 2 weeks, Within 1 month, 1–3 months, Unsure / dependent on approvals

Wrapping Up — What Would Make This Conversation Valuable Tomorrow?

• From everything we've discussed, what is the single biggest outcome you want us to deliver that would make you sleep better at night?
• What objections or concerns should we proactively address in our next conversation?
• Would you prefer a short technical prep session before any live-test (to walk through integrations) or a stakeholder memo that summarizes responsibilities and timelines? Options: Technical prep session, Stakeholder memo, Both, Neither
• Which immediate next step would you like us to take after this discovery (pilot plan, integration questionnaire, budget estimate, executive briefing)? Options: Pilot plan, Integration questionnaire, Budget estimate, Executive briefing, Other
• Is there anything else we haven't asked that you believe is critical for us to know before designing a solution?