Skip to main content
P04 · 24/7 Intake & Dispatch Backup

Try a simulated after-hours call.

Choose Miami / South Florida or Honolulu / Oahu, then step through a local SAMPLE scenario to see the intake pattern: structured fields, escalation decision, CRM event, and follow-up event. The two cohorts remain separate and the displayed disclosure is not legal approval.

SIMULATION — SAMPLE DATA — NOT A PRODUCTION RESULTThis is a deterministic browser simulator, not a live phone call or a live AI system.

Choose a sample launch city

Miami / South Florida SAMPLE configuration

Timezone: America/New_York (ET)

Disclosure: SAMPLE announce-and-confirm workflow — NOT LEGAL APPROVAL. Production language requires licensed review.

Escalation map: SAMPLE client primary on-call → SAMPLE backup → voicemail/notification

Miami and Honolulu sample cohorts are never pooled. No live calls, CRM writes, or legal approval are represented.

Choose a scenario

This simulator passing does not mean the flagship is live-ready. Live telephony readiness (product-factory gate F0) requires every item below — none of which this browser demo tests.
  • Not yet in placeA real, dialable test phone number is provisioned and reachable.
  • Not yet in placeTransfer to a real human and a tested voicemail/SMS fallback exist.
  • Not yet in placeCall logging and monitoring are wired to a real system, not this browser session.
  • Not yet in placeA real CRM/inbox event is written for every call, not simulated in memory.
  • Not yet in placeRetry and outage behavior (carrier down, CRM down) has been tested against real failures.
  • Not yet in placeA usage/cost meter tracks real minutes, model, and transcription spend.
  • Not yet in placeApproved disclosure and recording-consent behavior has been tested end to end.
  • Not yet in placeThe supported telephony/CRM stack combination for this client is named and confirmed compatible.
  • Not yet in placeA real 24/7 on-call human endpoint is identified for emergency escalation.
  • Not yet in placeA primary and backup technical implementer are named with written scope, cost, and SLA.

See /readiness for how demo, validation, and proven status work across the whole product catalog, and PRODUCT_FACTORY.md for the full P04 build sheet and acceptance tests.