When someone stops breathing, the software should already be running.

H18 Platform compresses every second between the emergency call and a volunteer sprinting out the door. Built by Hatzalah, for Hatzalah, in production today, dispatching real emergencies.

Book a walkthrough Follow one call ↓
One emergency · Five moments

This is what ninety seconds look like on H18.

A cardiac arrest at 595 Cedar Lane. Fictional details, real system, real timings, real screens.

00:00min · sec

The phone rings. Watch the AI fill the form live.

The moment the emergency line connects, an AI agent transcribes in real time, and the dispatch form reacts as the words are spoken. Complaint, address, caller: each suggestion pops in the instant the caller says it. This is the actual behavior, looping below.

00:23min · sec00:07 → 00:23

The AI already has everything. Sixteen seconds later, dispatched.

While the caller is still talking, the dispatcher's screen is already complete: complaint, observations, address, apartment, caller. One confirmation on the pre-highlighted address, and the call is out the door: keyboard-first, no mouse, no re-typing.

  • Never overwrites what the operator typed
  • Fuzzy complaint matching with top-3 candidates and confidence scores
  • Address pre-highlighted, but a human must confirm it: safety by design
  • Suggestions survive the hang-up, so nothing is lost between call and dispatch
  • Coverage-area soft gate warns before you dispatch outside your zone
  • Pre-alert: volunteers near the address get a live “AI Calls” notification with a chime, so they start getting ready before the dispatch even exists
  • Supervisors follow live calls in real time: transcript and audio, permission-gated
00:24min · sec

One second later, twelve phones erupt.

A full-screen alert wakes the device, takes over the lockscreen, and fires a 60-second siren with vibration that cuts through anything: sleep, a movie, a pocket. Nearest first. Equipment first.

  • Priority radius rings everyone close by at once, then orders the rest by ETA
  • Volunteers carrying the protocol's equipment, like a defibrillator, get called first
  • Accept or Reject straight from the push, without opening the app
  • Works on rugged Android radio handsets, even without Google services
01:02min · sec

Three volunteers are already running. Nobody gets blamed for being second.

Forty-second response slots. Automatic escalation waves until the quota is filled. A waitlist that re-promotes the instant a slot frees. And a fairness rule baked in: “slot filled” is tracked separately from “expired”, so nobody's record suffers because someone else was faster.

  • Wave-based search: nearest first, then by ETA
  • Reject works fully in the background: one tap, back to sleep
  • Queue positions and distances visible to the dispatcher in real time
04:51min · sec

On scene. And the whole chapter can see it.

The per-incident cockpit shows every responder on a live map with queue-position badges and distance lines, the vehicle timeline, and a dispatch-flow diagram of who was called, when, why, and what happened. On scene, the team charts the patient in the ePCR: vitals, evolutions, and a hospital handoff carrying the receiver's license and a hand-drawn signature captured on the phone.

  • Journey tracking: Accept → On my way → On scene → Finish
  • Live-synced clinical record: the dashboard sees the chart as it's written
  • Printable PDF report and a sanitized public status page carrying no patient data
After the run · The command deck

Ninety seconds of adrenaline. A permanent record of every decision.

Live KPIs, a keyboard-first operations queue, full incident history with filters, a ⌘K command palette, light and dark, realtime with graceful degradation to polling. The dashboard is where the chapter breathes.

In every pocket

The volunteer app is the quiet half of the system.

One-tap availability with a temporary-pause countdown that syncs across phone and radio. A live map of incidents, teammates, ambulances and coverage areas. An AI Calls tab with live transcripts and permission-gated audio. A “Test my siren” self-dispatch. OTA updates. Background location with heartbeat.

  • Fleet crews get a dedicated vehicle app: plate binding and a five-step journey: Accepted → En route → On scene → At hospital → Finished
  • Force-assign mode for crewed ambulances; live vehicle tracking for everyone else
  • Zello radio integration auto-joins incident channels

Everything a chapter runs on. One platform.

The story above is five moments. Here is the long tail: every capability shipping in production today.

Wave-based dispatch

Nearest first, priority radius, 40-second slots, automatic escalation until the quota fills.

AI call intelligence

Real-time transcription and structuring of the emergency line, straight into the dispatch form.

Command dashboard

KPIs, live queue, real-time map, incident history with filters, ⌘K palette, light/dark.

Lockscreen alerts

Full-screen dispatch alert that wakes the device, with a 60-second siren and vibration.

Accept from the push

Accept or Reject without opening the app; Reject works fully in background.

Equipment-aware

Volunteers carrying the protocol's required equipment, like an AED, get called first.

Fair to volunteers

“Slot filled” is tracked separately from “expired”, so nobody is blamed when others were faster.

Waitlist & re-promotion

When a slot frees, the next volunteer is promoted automatically, with no re-dispatch.

Live incident cockpit

Responders map with queue badges & distance lines, vehicle timeline, dispatch-flow diagram.

Address intelligence

Google-powered autocomplete, draggable pin map, coverage-area soft gate at dispatch time.

Vehicle (VTR) app

Plate binding, five-step journey, force-assign mode, live fleet tracking for everyone.

One-tap availability

Available/paused with countdown; state syncs across phone, tablet and radio handset.

Live AI Calls tab

Active calls, live transcript, audio playback (permission-gated), night-mode chime prefs.

ePCR on scene

Multi-patient charting: vitals, medical & nursing evolutions, smart document masks.

Signed hospital handoff

Receiver's name, license (CRM/COREN) and a hand-drawn signature captured on the phone.

Printable reports

Per-incident PDF report, plus a sanitized public status page with zero patient data.

Roles & permissions

Admin, dispatcher, doctor, nurse, first responder: fine-grained access to every screen.

Deny-all data model

Clients never touch the database, and realtime channels carry IDs only, never patient data.

Works without Google

Rugged Android radio handsets still get the full dispatch alert with no Google services installed.

Self-test dispatch

“Test my siren” lets every volunteer verify their alert path actually wakes their phone.

Staged rollouts & OTA

Cloud Run + Terraform infra, per-client isolated stacks, over-the-air mobile updates.

Realtime, gracefully

Live everywhere, with automatic degradation to polling when the network gets ugly.

Zello integration

Radio channels auto-join per incident; APK distribution page for radio handsets.

White-label ready

Your name, logo, colors and map region. One platform, many Hatzalahs.

Auditable by design

Frozen responder snapshot at creation; a full timeline of every decision, forever.

Medical data. Treated like it.

This platform carries patient information through the worst minutes of someone's life. The trust model is not a feature. It is the foundation.

Medical data is locked down by default. No client, app or browser ever touches the database directly.
The H18 data access rule

Deny-all row-level security

Clients never touch the database directly. Every read passes through an authorizing server; private realtime channels carry IDs only.

Server-side redaction

Without explicit permission, every digit is masked and phone numbers, transcripts and audio never leave the server. Engineered, not configured.

Role-based access

Admin, dispatcher, doctor, nurse, first responder: each role sees exactly what its duty requires, down to individual fields and actions.

Auditable dispatch

A frozen snapshot of eligible responders at creation, plus a complete timeline of who was called, when, why, and what they answered.

Built by Hatzalah, for Hatzalah.

We're not a vendor discovering EMS. We're a chapter that built its own platform, runs it in production, and now offers it, white-labeled, to sister organizations worldwide.

Chapter AFounding chapter · its own brand
In production
Chapter BSecond tenant · own name and colors
In production
Your chapterYour city, your colors
Next

One platform. Many Hatzalahs.

  • White-label everything: your chapter's name, logo, colors and map region. The platform is already multi-tenant in production, serving more than one organization.
  • Isolated stacks per client on Google Cloud (Cloud Run), fully described in Terraform.
  • Staged rollouts and OTA updates so your volunteers get improvements without app-store friction.
  • Hatzalah-to-Hatzalah: we dispatch real emergencies on this exact system every day. What we ship to you is what we run ourselves.
Bring H18 to your chapter
04 · Contact

Your chapter's next call could start seven seconds faster.

Tell us about your organization and we'll walk you through the live system, the same one dispatching real emergencies right now. No decks. Real screens, real calls.

Prefer email? Write to team@h18.platform

Thank you. Your email client should have opened with everything pre-filled. If it didn't, write to team@h18.platform directly.