FireScriptTurn each call into the next step to verify.
FireScript is a dispatch-support system designed to transcribe an authorized live 119 call audio feed as calls happen and organize critical details. It presents location and incident suggestions for dispatcher review and decision-making.
See the workflow in practiceOperators need to understand the call, verify the location, and follow vehicle and destination updates. Unclear speech and uncertain locations must remain distinguishable from confirmed information.
Speech becomes text and suggested situation and location details. Operators check the conversation, map, and shared coordinates before confirming a location and assigning a vehicle. They verify and enter the hospital reply before sending the destination to the crew.
A live 119 call audio feed becomes text and suggested incident details as the call happens. Dispatchers verify and correct them before deciding the next action. Connection requires the responsible authority's approval.
Audio input
Transcript + Structured data
Suggested type / Suggested priority / Summary
The operator coordinates the vehicle assignment, verifies the hospital reply, and shares the destination with the crew.
FireScript structures speech for review so the operator can confirm the location and decide the next action.
The authorized live audio feed from a 119 call is received.
Speech becomes readable text for review.
Organize suggested situation, location, type, and priority details.
FireScript proposes an incident category based on the communication.
The operator checks the conversation, map, and location suggestions before confirming the location.
The operator coordinates the vehicle assignment, verifies the hospital reply, and shares the destination with the crew.
Transcribes an authorized 119 call audio feed as calls happen and presents it for review.
Radio codes are managed as a catalog, with the Ñuñoa fire department (Chile) code set supported today. Your agency's codes and local terminology can be added.
Structures suggested situation, location, type, and priority details. The operator verifies and confirms the location.
Suggests an incident category from the communication while leaving final judgment to the operator.
Crews acknowledge assignments and report progress. Operators verify and enter hospital replies, then send the destination.
Long-term incident retention, audit records, and connections to existing dispatch and hospital systems are configured to each agency's requirements.
Check a report of someone collapsed near a station against the conversation and map to confirm the location.
An operator assigns a vehicle; the crew acknowledges and reports response and scene arrival.
An operator verifies and enters the hospital reply, then sends the destination to the crew after scene arrival.
Request help from nearby registered responders and review AED information around a confirmed location.
Explore a call from outside a station, from confirming the location to coordinating an ambulance, a hospital, and community responders.
CHOOSE A WORKFLOW
After a caller reports someone collapsed outside a station, the call handler uses the conversation and map to check the scene's location.
Automatic animation is off to match your device preference. Select a step to view it.
Starts the call and listens to the report
Transcribes the speech and organizes the situation and possible locations
If needed, opens a location-sharing link and consents to sending the location
Compares the conversation, map, and possible locations to confirm the location
CONDITIONS TO CHECKLocation sharing requires the caller's consent. The operator checks and confirms any suggested or shared location.
Roll out in stages that follow your procedures. Authorized people and organizations keep the decisions on location, dispatch, vehicle assignment, hospital acceptance, and destination.
Walk through your intake-to-transport procedures in FireScript: the facts to check, who reviews them, and where decisions are made.
After the responsible authority approves access and integration conditions, process the live audio feed from real 119 calls as they happen. First evaluate transcription, critical-detail extraction, and latency in parallel without affecting dispatch; then move to dispatcher-visible review.
Use the findings to define long-term incident retention, audit records, notification settings and consent, and connections to existing dispatch or hospital systems.
A practical starting point for your operations, technology, and data teams.
No. FireScript is advisory: it presents information and preliminary suggestions for review. Authorized people and organizations retain decisions on dispatch, resource allocation, destinations, and hospital acceptance.
The proposed input is the live audio feed from real 119 calls. After the responsible authority approves access, data handling, and integration, we begin with a non-interfering parallel evaluation and move to dispatcher-visible support based on the results. Dispatchers retain final decisions.
Operators verify and enter hospital replies, then send the destination to the crew. FireScript includes an integration layer designed to connect with existing dispatch and hospital systems, configured around interface approval, data freshness, retention, and audit requirements.
Tell us how your intake and dispatch work today. Let's plan a FireScript rollout with the operator at its center.
