Radios, Pagers and Landlines: Costing Out the Comms Stack You Already Own

The comms stack most venues and hotels already own is three tools bought in three different decades: two-way radios for staff, pagers for guests or servers, and landlines at the front desk and in the back office. Each has a price on an invoice and a second price that never appears on one, and the second is usually the larger.

This comparison costs out both. The legacy stack is itemized from public records and the FCC fee schedule, never from a vendor price list. The tap-to-request side is priced from Listo's published rate of $29.99 per active user per month, stated on the workforce communication ROI statistics page. Every figure names its source and links to it.

On hardware alone the two stacks land closer than most operators expect. The gap is everything that happens after the button is pressed.

What the legacy stack actually costs

A business radio fleet is a capital purchase, a license, a coverage project and a consumables budget, and most buildings track only the first. The Federal Communications Commission describes private land mobile radio under Part 90 as the systems companies use for coordination of people and materials, safety and security, and quick response in emergencies, which is exactly how a venue uses them. The components below are priced from neutral public sources.

An illustration, built only from the sourced inputs above. Take a venue with 80 radio users. The Millington purchase of $129,811, a school campus with a stadium and the closest public record to a mid-size venue, spread across its five-year warranty is about $26,000 a year for radios, accessories and one repeater. Add 20 front-desk and back-office lines at the UC Berkeley rate of $32.97 a month, about $7,900 a year. The FCC fees of $105 plus a regulatory fee once a decade and a $35 renewal under 47 CFR 1.1102 round to nothing per year. Batteries, chargers and earpieces come on top. The visible total is roughly $34,000 a year before consumables. Your building will differ.

Then there is the second price, the one that never reaches an invoice:

• Relay time. A guest tells a server, the server radios a supervisor, the supervisor finds a runner. Three people touched a request that needed one.
• Missed requests. A radio call goes out to everyone on the channel, so it belongs to no one. The request nobody picked up does not exist anywhere.
• No audit trail. Radios and pagers leave no record of what was asked, who took it or when it was done. You cannot staff to a peak you cannot see.
• Communication quality. Only 10 percent of non-desk employees in the U.S. are very satisfied with internal communication at work, and 40 percent rate it fair or poor, per the 2025 Staffbase and YouGov study of 1,044 employees.

None of these show up in a hardware comparison. All of them show up in response time.

What a tap-to-request platform costs

A tap-to-request platform is a subscription with no hardware line. Listo's core platform starts at $29.99 per active user per month, per Listo's published pricing, and runs on the phones, tablets and Samsung Galaxy smartwatches staff already carry. There is no FCC license, no frequency coordination and no repeater, because the request travels across the Wi-Fi or cellular network the building already has.

On the same 80-user illustration, 80 active users at $29.99 a month is about $28,800 a year, in the same range as the visible radio and landline total above. The difference is not the subscription. It is that the subscription buys routing, a record and escalation, and the radio fleet buys none of those.

The mechanism is the point. A guest scans a QR code or a staffer taps a request, Listo smart-routes it to the right available team member, that person accepts or declines it and marks it complete, and it rolls up into real-time analytics. Unanswered requests escalate to a manager, covered in the explainer on what should happen when nobody answers. Listo reports an average 15 percent reduction in monthly labor hours across its customers. That is a platform-wide average Listo reports, not a guaranteed outcome.

Legacy stack vs tap-to-request: honest comparison table

The table compares the two on what each actually does. "None" means the capability does not exist in that stack, not that a workaround is impossible.

Read down the table and the split is clean. The legacy stack wins the rows about talking and resilience. The platform wins the rows about ownership, record and measurement. Those are different jobs.

When radios and pagers are the right tool

Radios are the right tool when the job is live voice to many people at once, or when the network cannot be trusted. The U.S. Cybersecurity and Infrastructure Security Agency's 2022 SAFECOM guidance on radio and LTE integration states that land mobile radio provides one-to-many voice on a single channel, broadcasts at higher power than phones, and keeps working radio-to-radio even if its infrastructure fails, while LTE is vulnerable when towers are down or the network is overwhelmed. Keep radios if you need to:

• Reach every security, medical and operations lead in one transmission during an evacuation, a lockdown or a medical call.
• Keep talking when a sold-out crowd saturates the cellular network or the Wi-Fi drops.
• Coordinate a crew that works outdoors, in weather, or in a lower level where a phone has no signal.
• Let a waiting guest wander and come back, the one job a guest pager does.

None of that is a tap-to-request platform's job, and we would not suggest otherwise. Public agencies make the same split. The same CISA document records that the Indiana Department of Corrections kept full radios for law enforcement roles, moved 200 other staff to cheaper LTE devices that still reach the radio system, and reported nearly $500,000 in savings. Radios for the critical channel, something lighter for everyone else.

When a tap-to-request platform is the right tool

A tap-to-request platform is the right tool when the problem is a request, not a conversation. A suite wants another round, a cabana wants towels, room 414 reports a leak. Each needs one person, a record and a clock. The how-to on replacing stadium radios with tap-to-request routing walks through the switch. Choose it if you need to:

• Let guests in suites, cabanas or rooms summon service with a QR code and no app, routed to the nearest available staffer.
• Replace the multi-person radio relay with a request that lands with one assigned, available person.
• Prove the work was done, with an accepted, completed and timestamped record for every request.
• Escalate anything unanswered to a manager automatically.
• See response times and high-demand areas by hour, then move floating staff to match.

These outcomes are tied to named customers. At TD Garden (Delaware North), Listo runs across 90 premium suites and handled 1,472 completed guest requests in 6 months at an under 5-minute average response. At American Family Field (Delaware North), Listo reports 0 missed restock orders and a 67 percent reduction in IT downtime. Those are single-venue results, and your building will differ.

Can radios and a tap-to-request platform work together?

Yes, and in most buildings they should. Radios stay the emergency and security channel. Service requests move to the routed system. Listo's own guide on choosing an employee communication app for frontline venue teams says it directly: radios do not have to disappear on day one. Move one area first, premium suites, cabanas or housekeeping requests, keep the radios on the belt, and count how many supervisor calls disappear. The radio is for the moment the building needs one voice. The platform is for the hundreds of moments it needs one person.

See the stack costed in your own building

If your question is how to reach everyone at once when something goes wrong, the answer is still a radio. If your question is why a guest waited eleven minutes for a request three people heard, that is the job a tap-to-request platform was built for.

To cost out your own radios, pagers and landlines against a routed request flow, book a demo or get in touch with the Listo team. We will walk through your request volume, your dead zones and your response times, and show you exactly which requests should leave the radio.