The problem ResQ solves

How It Makes Ambulance Booking Easier and Safer
This feature transforms your project from a "smartphone app" into a complete, multi-channel "emergency response platform".

Universal Access (Easier) Your app requires a smartphone and internet. Your IVR system only requires the ability to make a phone call. This means anyone with a basic feature phone or even a landline can now access your "life-saving mobile platform", dramatically expanding your user base.

Simplicity During Panic (Easier & Safer) During a "critical medical emergencies", a user may be too panicked, injured, or distressed to unlock their phone, find your app, and navigate its interface. It is far simpler and more instinctual for most people to dial a number. Your AI agent guides them through the booking process with simple voice commands, lowering the barrier to getting help.

Confirmation and Reduced Anxiety (Safer) You mentioned the system "send[s] a SMS" after booking. This is a crucial safety feature. It directly supports your project's goal of "Reduces Panic & Anxiety". After the call ends, the user (or their family member) receives a text confirmation. This provides immediate "peace of mind" that the request was successful and help is on the way, which is a massive improvement over traditional, "fragmented" call systems where you just have to hope.

Bridges the Digital Divide (Easier) This feature makes your platform inclusive for vulnerable populations, such as the elderly or those with disabilities, who are often most in need of emergency services but least likely to be comfortable with new app technology. They can now access the same powerful "AI Smart Dispatch" and "Predictive Routing" as your app users, just by using their voice

Challenges we ran into

Challenge: Finding the fastest ambulance, not just the closest.
Hurdle: The geographically closest ambulance isn't always the fastest due to "unpredictable traffic".

Solution: We use MongoDB geospatial queries to find nearby ambulances, then feed them to the Google Maps API to get the actual traffic-based ETA. Our "AI Smart Dispatch" then assigns the one with the shortest arrival time.

Challenge: Instant, real-time synchronization.
Hurdle: We needed to show "Live GPS Tracking" to patients, drivers, and hospitals simultaneously without lag.

Solution: We built our "Real-time Layer" using WebSockets (Socket.io). This "pushes" location data to everyone instantly, rather than making them constantly refresh and poll the server.

Challenge: Integrating the new IVR (voice) feature.
Hurdle: Our backend was built for apps and needed to understand voice commands from a regular phone call.

Solution: We used the Twilio API to "listen" to the user. It converts their voice requests into a standard API call, which is then sent to our "AI Dispatch Engine" —treating the call just like a booking from the mobile app.