A wearable panic button for employees is a small device a staff member carries, on a badge clip, a lanyard or a wristband, that sends a discreet emergency alert when pressed. The alert travels over a wireless network to a gateway, then to the people set up to respond, so help is called without a phone call or a visible reaction.
If you want the broader picture of what a panic button does, start there. This page is for the person who has to make one work across a real building. It covers what a responder actually sees, how the four wearable form factors compare, why coverage decides everything, what happens in the thirty seconds after a press, and where these devices fall short.
What a Responder Actually Sees When Someone Presses
A press starts a short relay. The button sends a radio signal to the nearest gateway. The gateway passes the alert to the emergency platform over the building's network. The platform then notifies everyone configured to receive that emergency type, on the screens and devices they've been set up to use.
On Coram hardware, the press itself is deliberate. "Two or more presses in quick succession triggers the configured emergency type. A flashing green light confirms the activation." A single accidental bump does nothing, and the person pressing gets a quiet signal that the alert went out.
What the alert carries matters more than how it travels. A Coram activation shows the location set for that button, or the location of the nearest online gateway if none is set, along with the person the button is assigned to. In practice, that means the building and, with good gateway placement, the floor, not the room.
That is an honest answer to the question every buyer asks first: "Will we know where they are?" You will know the location you configured for that button, and careful setup gets you to the floor. You will not see the room number. The response plan should say who checks which areas once the alert arrives.
What the alert also carries is the emergency type. Each button is set to fire a specific type, such as Lockdown or Shelter, so responders know what kind of response is expected before they arrive. A nurse's station and a loading dock can fire different types, which saves the minutes it would otherwise take to work out what kind of emergency this is.
For a facilities or security manager, that shapes the rollout. Decide which emergency type each button sends, decide who receives each type, and write down how responders will narrow the search once they know the site and floor. Those three decisions matter more than the device itself.
The Four Wearable Form Factors, Compared
The table makes two different questions visible. The first is whether the device is on the person at the moment it is needed. A wristband taken off for handwashing, a keyfob left in a coat, or a phone in a locker all fail the same way: the employee has a panic button, just not on them. Badge-clip devices tend to win this one because staff already wear the badge to get through doors.
The second question is whether the press reaches anyone. A phone app depends on that phone's signal and battery at the worst possible moment. A dedicated radio button depends on the gateway network behind it. Neither is automatically better, but they fail in different places, and a buyer should know which failure they are choosing.
Both have to be right. Form factor decides whether the device is on the person when it matters. The network behind it decides whether the press gets through. Most of the evaluation effort belongs on the second, because that's the part a vendor demo can't show you.
Coverage Is the Product: Gateways, Floors, and Dead Zones
A wearable panic button is a radio. It reaches a gateway, or it reaches nothing. Every other feature on the spec sheet depends on that one fact, which is why coverage is the real thing you are buying.
How far one gateway reaches
A gateway is the receiver that listens for button presses and passes them to the emergency platform over your network. On Coram, "A single gateway can support multiple buttons, and has a maximum range of up to 1 kilometer." The installation guide adds the condition that matters: "The gateway has an effective range of approximately 3,300 ft (1 km) under optimal conditions."
Optimal conditions are open air and clear line of sight, which almost no building offers. Walls, floors and equipment all cut into that figure, so treat the published range as a ceiling, not a planning number.
Gateways need power and a network connection, which is where IT comes in. Coram gateways take Power over Ethernet (IEEE 802.3af) or Ethernet plus a power adapter, and the guidance is clear: "It is strongly recommended to use a wired Ethernet connection for the gateway whenever possible. It's the most reliable path for emergency traffic." Bring IT into the conversation early, because cable runs and switch ports are usually what sets the timeline.
Coram's installation guide says to place gateways on every floor, or at least on the floor that needs the most reliable coverage, and to add a gateway when a critical area is more than one or two thick walls away or out of sight. Placement changes the answer as much as count does. Mount the gateway high and central to the area it covers, and "Keep 3–6 ft (1–2 m) of open space around antennas." A gateway tucked in a corner closet above a ceiling tile covers far less than the same gateway mounted openly in the middle of the floor.
The three places coverage breaks
- Construction between the button and the gateway. Radio signals weaken through dense materials, and some materials stop them almost entirely. The installation guide lists the usual suspects: "Avoid thick concrete, brick, metal racks, elevator shafts, and large machinery between the gateway and buttons." Warehouses with steel racking, plants with heavy machinery, and older buildings with thick masonry walls all need more gateways than their floor area suggests. Survey the actual construction, not just the drawings.
- Vertical gaps. Stairwells, elevators, basements and parking structures are where people are often alone, and where signal from the floor above or below doesn't reach. Concrete stair cores and elevator shafts are among the strongest blockers in a building. This is why the guidance is a gateway on every floor: a gateway on the second floor rarely covers the basement reliably, even if the straight-line distance is short.
- A gateway that is offline. Coverage can disappear without anyone moving a wall. "Panic buttons only work where a gateway is present and online." And when none is: "If no gateway is online at a location, button activations from that area won't reach Coram EMS." A switch reboot, an unplugged cable or a network change can quietly take an area out of coverage. A system should tell you before an employee finds out. On Coram, "Coram also sends automatic email notifications when a gateway goes offline or a panic button's battery drops below 5%, so you can address device issues before they affect emergency response."
The practical step is simple and almost always skipped. Before the rollout, walk the routes staff actually take, including the loading dock, the far end of the parking lot, the stairwells and the basement, and test a button at each point. Each test press should show up on the platform. Anywhere it doesn't is a place to add or move a gateway before anyone depends on it.
The Thirty Seconds After the Press
The button is the cheap part. What a buyer is really paying for is what the system does automatically in the half minute after someone presses it: who hears about it, whether doors lock, and whether 911 is called. Those are the steps people are worst at doing by hand under stress.
Who gets notified, and where
When a button fires, the alert goes to the people configured for that emergency type. On Coram, emergencies reach responders through the web dashboard and the mobile app. Emergencies can also be reported from those same places, so a staff member without a button can still raise the alarm.
The button is designed to be discreet. The only confirmation is a small flashing green light. That matters in exactly the situations where a wearable button is useful, a tense conversation at a front desk or a threat in a parking lot, where an obvious alarm could escalate things. For more on discreet alerting at desks and in offices, see silent panic buttons in office environments.
Locking doors without a security admin in the loop
In many emergencies, the most important minute is the one in which doors lock. Doing that by hand means someone with the right permissions has to be at a screen, logged in, and thinking clearly. A linked lockdown removes that step.
On Coram, "When you report an emergency, Coram can automatically activate a linked Access Control lockdown alongside the emergency broadcast; no separate manual step required." The person pressing the button doesn't need special access: "The emergency reporter does not need Access Control access or lockdown-specific permissions. The lockdown activates regardless." A receptionist or a warehouse worker can lock the building without ever having touched the access control settings.
Lockdown is linked per emergency type, so a Lockdown alert can lock doors while a Shelter alert does not. Lockdown activation is best-effort and never blocks the emergency broadcast, so a door problem can't stop the alert from going out.
One behavior surprises people, and it's deliberate: "When the emergency is resolved, the linked lockdown remains active. You must deactivate the lockdown separately in Access Control." Doors don't spring open because someone marked the emergency resolved. A person has to look at the situation and decide the building is safe before unlocking it. Read more about cloud-based access control.
Getting 911 on the line
Calling 911 is the step most likely to be delayed, because everyone assumes someone else has already done it. Automatic Dispatch closes that gap by connecting the emergency to a dispatch partner who contacts local emergency services.
On Coram, Automatic Dispatch is set per emergency type by an admin. "You enable Automatic Dispatch individually for each emergency type, after acknowledging a one-time disclosure." It has a geographic limit: "Automatic Dispatch is available only for locations in the 50 US states and Washington, D.C." Each location also needs a complete US address, a phone number and an emergency contact, and the feature may not be available for every organization, so confirm it for your account.
When it's off, there's a manual path: "When Automatic Dispatch is off, responders can still loop in the dispatch partner manually, using the Notify First Responders button." Either way, the response plan should say who confirms that 911 has been contacted.
Wearable Panic Buttons in Coram EMS
Coram Emergency Management (EMS) uses Coram's own panic buttons and gateways, and they are built to be checked before anyone relies on them.
Activation is two or more quick presses, confirmed by a flashing green light. A single press is the test gesture: a green light confirms the button is powered, charged and communicating, and its Last Seen value updates in the web app. A new button is paired near an online gateway, and pairing is confirmed before the button is mounted or handed to a person.
Each button has a built-in rechargeable battery with an expected working time of about six months under normal use. Charge it with the supplied charger until it's full, then do a single-press test. When a button's battery drops below 5%, Coram emails EMS admins who have device notifications turned on, and repeats the email every 24 hours until the button is charged or replaced.
One boundary is worth knowing up front: buttons are added by serial number and verified during registration, and only Coram-supplied buttons work with Coram gateways. Panic buttons from other manufacturers can't be reused with Coram EMS.
Beyond the button, Coram EMS sits on the same platform as Coram's video and access control, which is what lets a press lock doors and notify responders without anyone switching systems.
Where Wearable Panic Buttons Fall Short
Location stops at the building and the floor. A Coram activation shows the location set for that button, or the location of the nearest online gateway if none is set, along with the person the button is assigned to. In practice, that means the building and, with good gateway placement, the floor, not the room. Responders arrive knowing where to start, not exactly where to go. Plan for that in the response procedure.
Everything depends on gateway coverage. A button outside coverage, or near a gateway that is offline, sends nothing. No feature fixes a dead zone except another gateway in the right place. Coverage has to be designed, tested and monitored, not assumed.
A button program needs discipline. Buttons need charging and periodic test presses, gateways need to stay online, and buttons need to be reassigned when staff change. A program that skips this has buttons that look ready and aren't.
A button reports an emergency. It doesn't resolve one. It gets the right people moving faster and can lock doors and start a 911 call. It doesn't replace training, a response plan or people who know what to do when the alert arrives.
Some environments carry rules this page doesn't cover. Schools in particular face state requirements; see choosing a panic button for a school.
Rolling Out Your First Twenty Buttons
- Survey coverage. Walk every route staff use, including stairwells, basements, loading docks and parking, and note the construction in each area.
- Place and cable gateways with IT. A gateway on every floor as a starting point, high and central, on wired Ethernet, with more where concrete, metal or machinery gets in the way.
- Pair each button and confirm it reported in. Pair near an online gateway and check that each button shows up before it goes to anyone.
- Assign buttons to people and locations. Set the location and assigned user on each button, since that is what the alert shows.
- Set which emergency type each button fires. Match the type to the role and the risk, and link lockdown and dispatch where they belong.
- Run a drill. Test presses along the routes from step 1, and confirm responders receive the alert and know what to do.
- Set up device-health notifications. Make sure an EMS admin receives the offline-gateway and low-battery emails, and decide who acts on them.
Test It Before You Need It
A wearable panic button is only as good as the coverage behind it and the habit of testing it. Walk the building, test the presses, and keep the gateways online. If you want to see how a press turns into an alert, a lockdown and a 911 call, book a demo.
FAQ
Is there a wearable panic button that calls 911?
Yes, when the system behind it supports automatic dispatch. On Coram, Automatic Dispatch connects an emergency to a dispatch partner who contacts 911. An admin enables it for each emergency type, and it covers locations in the 50 US states and Washington, D.C. Each location needs a complete US address, and when the feature is off, responders can bring in the dispatch partner manually.
Is there a wearable panic button that can call my cell phone?
A dedicated wearable button doesn't place a phone call, but the system can alert your phone. On Coram, emergency alerts reach responders through the mobile app and the web dashboard. Choose who receives each emergency type, and their phones get the alert when a button is pressed.
Do wearable panic buttons still work if the Wi-Fi or cell network goes down?
Buttons on a dedicated radio network don't use Wi-Fi or cell service to reach the gateway, but the gateway needs to be online to pass the alert on. On Coram, buttons only work where a gateway is present and online, and Coram emails EMS admins when a gateway goes offline.
Can we use panic buttons we already own with a new system?
It depends on the system. Coram buttons are added by serial number and verified during registration, and only Coram-supplied panic buttons work with Coram gateways, so existing buttons from other manufacturers can't be reused with Coram EMS.






