# Who's Responding > Incident response alerting app showing real-time responders list & more Canonical page: [https://chrome-stats.com/d/com.fluentims.WhosResponding](https://chrome-stats.com/d/com.fluentims.WhosResponding) ## Overview - **ID:** `com.fluentims.WhosResponding` - **Platform:** Android - **Type:** Android app - **Status:** Available - **Publisher:** Fluent Information Management Systems, Inc. - **Category:** COMMUNICATION - **Downloads:** 76,334 - **Rating:** 3.68 / 5 (301 ratings) - **Version:** 4.18.0 - **Last updated:** 2026-09-10 - **First published:** 2014-12-16 - **Publisher country:** CA - **Size:** 62 MB - **Data as of:** 2026-09-17 - **Store listing:** [Google Play Store](https://play.google.com/store/apps/details?id=com.fluentims.WhosResponding) - **Website:** [http://www.whosresponding.com/](http://www.whosresponding.com/) - **Privacy policy:** [http://www.fluentims.com/whosresponding/privacy](http://www.fluentims.com/whosresponding/privacy) ## Description Who’s Responding is an incident response alerting and coordination app built for teams that must act fast and stay organized. It shows real‑time responder lists and ETAs, provides turn‑by‑turn navigation, live radio access, hands‑free auto‑speak alerts, mapping tools, and centralized access to SOPs, preplans, and digital resources. The app also tracks attendance, availability, apparatus assignments, and event history to streamline operations across emergency services, public works, hospitals, schools, and industrial teams. Trusted by thousands for over a decade, Who’s Responding is fully customizable to match your team’s workflows and notification needs. Sign up for a 45‑day free trial at www.WhosResponding.com (subscription required). Note: continued GPS use in the background may reduce battery life. ## Rankings - #250,364 — Overall ## Permissions and access ### Permissions - `android.permission.ACCESS_ADSERVICES_AD_ID` - `android.permission.ACCESS_ADSERVICES_ATTRIBUTION` - `android.permission.ACCESS_BACKGROUND_LOCATION` - `android.permission.ACCESS_COARSE_LOCATION` - `android.permission.ACCESS_FINE_LOCATION` - `android.permission.ACCESS_NETWORK_STATE` - `android.permission.ACCESS_WIFI_STATE` - `android.permission.ACTIVITY_RECOGNITION` - `android.permission.CAMERA` - `android.permission.CHANGE_NETWORK_STATE` - `android.permission.FOREGROUND_SERVICE` - `android.permission.FOREGROUND_SERVICE_DATA_SYNC` - `android.permission.FOREGROUND_SERVICE_LOCATION` - `android.permission.FOREGROUND_SERVICE_MEDIA_PLAYBACK` - `android.permission.INTERNET` - `android.permission.MODIFY_AUDIO_SETTINGS` - `android.permission.POST_NOTIFICATIONS` - `android.permission.READ_EXTERNAL_STORAGE` - `android.permission.RECEIVE_BOOT_COMPLETED` - `android.permission.RECORD_AUDIO` - `android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS` - `android.permission.SCHEDULE_EXACT_ALARM` - `android.permission.VIBRATE` - `android.permission.WAKE_LOCK` - `android.permission.WRITE_EXTERNAL_STORAGE` - `com.fluentims.WhosResponding.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION` - `com.google.android.c2dm.permission.RECEIVE` - `com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE` - `com.google.android.gms.permission.ACTIVITY_RECOGNITION` - `com.huawei.hms.permission.ACTIVITY_RECOGNITION` - `com.huawei.permission.external_app_settings.USE_COMPONENT` - `oppo.permission.OPPO_COMPONENT_SAFE` ## Review summary Users appreciate "Who's Responding" for improving call notifications over traditional methods, responsive support, and useful features like tracking responders. However, frequent app glitches, notification problems, lack of smartwatch integration, and issues after updates frustrate many. Some desire additional features like scheduled duty times and better message retention. Despite shortcomings, the app remains a valuable tool for volunteer and professional firefighters. ### Pros - App effectively notifies users about calls, reducing missed alerts compared to traditional pagers and radios. - Customer support is responsive and helpful, resolving issues swiftly when contacted. - The app allows users to see who is responding and their locations, aiding coordination during emergencies. - Many users find the app easy to use and appreciate its utility in a volunteer firefighting context. - Continuous improvements and willingness of developers to accommodate specific organizational needs. ### Cons - Frequent bugs and glitches, including crashing after updates, requiring reinstalls or device restarts to fix. - Notification issues such as audible alerts that can't be fully controlled, missing notifications when using Android Auto, or notifications not working without strong internet connections. - Lack of important features like a smartwatch app, widgets, scheduled on/off duty times, and automatic login retention after updates. - App sometimes logs users out unexpectedly or places users off duty without their control, causing missed messages and calls. - Slow loading times and unreliable performance in rural areas due to dependence on strong internet connections. ## Similar extensions and apps - [Respond-ER](https://chrome-stats.com/d/com.app.adjutant.responder) — 2 users - [Alert2Mate - Team Coordination](https://chrome-stats.com/d/com.redhelmet.a2mate) — 491 users - [EMS - Emergency Responders](https://chrome-stats.com/d/fw.com.bhv) — 12,002 users - [RunReady](https://chrome-stats.com/d/com.runready) — 88 users - [Responder](https://chrome-stats.com/d/ar.com.responder) — 1,377 users - [Callouts](https://chrome-stats.com/d/com.callouts.app) — 8 users - [response](https://chrome-stats.com/d/app.response) — 602 users - [ALERT PINAMALAYAN RESPONDER](https://chrome-stats.com/d/com.arispinamalayan.responder) — 12 users - [iRespond](https://chrome-stats.com/d/com.providedigital.irespond) — 5 users - [KlinicX Responder](https://chrome-stats.com/d/com.klinicx.responder) — 14 users - [Response 24 Plus](https://chrome-stats.com/d/com.response24.mobile) — 1,378 users - [Swift SOS](https://chrome-stats.com/d/com.swift.sos) — 236 users --- Source: [Chrome-Stats](https://chrome-stats.com/d/com.fluentims.WhosResponding)