unthinkable
Case study · Ziqitza Healthcare Ltd, India · ambulance and emergency medical services

People who call for an ambulance in India get one assigned at once, and a message saying who is coming.

Ziqitza wanted every caller on its emergency lines to reach an ambulance and crew without delay, with each request tracked from the call to the drop-off instead of on paper and spreadsheets.

IndiaCare coordination & remote monitoring

What changed

67,000emergency calls received per day (as reported)
3500+ambulances integrated (as reported)
2 million+tele-health consultations (as reported)
32 lakh+people served with the EMS system, including 12 lakh+ pregnant women (as reported)
What stood in the way

What stood in the way.

What stood in the way
  • Ziqitza runs a fleet of 3,389 ambulances across 18 states and operates the 108 ambulance and 104 health helplines with state governments.
  • As requests grew, the legacy web app could not manage them: ambulance booking was only partly digital and service requests were processed by hand on paper.
  • Service activity was logged in spreadsheets, so no one could track a request in real time.
  • Every state wanted its own dialer, vehicle tracking and verification rules, and changes to the apps meant downtime.
What changed
  • 67,000emergency calls received per day (as reported)
  • 3500+ambulances integrated (as reported)
  • 2 million+tele-health consultations (as reported)
  • 32 lakh+people served with the EMS system, including 12 lakh+ pregnant women (as reported)
What we built

What we built.

  • A React web app for the call teams: each answered call creates a service request, and the team assigns an ambulance, driver and emergency medical technicians.
  • Role-based access through master data (shift, district, client, hospital and other masters), so each user sees only their part.
  • A React Native app for drivers, technicians, supervisors and auditors: the nearest available ambulance is notified, the driver calls the caller from the app, and the caller gets a push notification and SMS with the ambulance and driver details.
  • An operations support desk for the fleet, covering fuelling and drivers' issue tickets.
  • A decoupled architecture so each state can plug in its own dialer, vehicle tracking system and screens, and choose which emergency numbers (100 for police, 101 for fire and 108 for ambulance) the care team receives.
  • Central logging with a trace ID for every service request across its whole life, and a reporting tool built on Next.js.
  • An extension for private ambulance services: a customer app with scheduled bookings and basic, cardiac and 5G-enabled ambulances, plus ground, air, pet, event and doctor-at-home requests.
  • A vendor and supervisor app that sends requests to registered third-party vendors as well as in-house crews, with a commission to Ziqitza.
  • React
  • React Native
  • Next.js
  • Decoupled architecture
  • Centralized logging
What it shows

What this work shows about us.

We know the emergency dispatch chain

Call, service request, ambulance, driver, technician and hospital each have their own role and screen, with every step traced from the first call.

One system, many states

Dialers, vehicle tracking and verification rules plug in per state government, without rebuilding the apps.

From public helpline to private service

We extended the government portal into private and scheduled ambulance bookings with vendors, instead of starting again.

Want to modernise your emergency dispatch portal like this? Tell us what you want to change. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with the right team.

Start your plan ↗
If we built it today

If we built it today, with AI.

This work came before today's AI. If Ziqitza Healthcare asked us now, this is what we would add, step by step.

Emergency

An agent would fill the service request while the call handler is still on the call, from the caller's answers on location, severity and needs such as oxygen. The call handler still confirms every dispatch.

Arriving

An agent would keep the caller told where the ambulance is and when it will arrive, and answer follow-up calls without tying up a line.

Booking

An agent would take a scheduled or non-emergency ambulance booking by message, check the type needed and confirm the time. Supervisors still assign the crew.

The bill

An agent would explain a private booking's charges and send the receipt, from the booking record and the vendor's price.

Ask Unthinkable

Want this for your business?

Tell us what you run or what you're building. Our AI assistant, Ask Unthinkable, helps you define your requirements, then connects you with a senior AI engineer.

Send us a note instead

Required

Thanks. A senior AI engineer will reply to you.
u
Ask UnthinkableClarity first, then the right team
Your conversation

An AI agent. This prototype uses prepared answers and sends nothing.