Quick answer: A paging group is a named list of devices and people that one tap addresses all at once. In Devotel Orbit, an operator opens Voice → Paging groups (/voice/paging-groups), hits Page on a group, and the announcement goes out to the zone: SIP deskphones are paged and play it out loud (auto-answer-capable phones straight on speaker), while softphone teammates get an "Incoming page" notification they can open in one tap. Type the announcement and paged deskphones read it out on speaker while teammates see it in the notification; send it blank and the group sounds the incoming-page notice instead. Nobody dials a list, and nobody has to be at their phone to be reached. It is the overhead speaker system, rebuilt on the cloud phone system the team already runs.
What 1-tap paging is, and what it is not
Three distribution shapes get confused because they all "reach a team":
- Hunt (ring group). An inbound call rings member devices in an order or all at once until one person picks up. One caller ends up in a two-way conversation with one answerer.
- Ring-all. Every device rings at once, but the call still needs a human to pick up. It is a hunt with no order, not a broadcast.
- Paging. Nobody has to wait for one person to pick up. Deskphone endpoints on the group's roster are paged and play the message out loud, and the teammates on that roster get it pushed to their softphone, and one voice goes to many listeners at the same time.
Paging is one voice to many ears. Hunt is many devices racing to one conversation. If the message matters to whoever happens to be in the zone, page the zone. If it matters to one named person who must answer back, dial their extension or let a hunt group find them.
Orbit ships the whole surface end to end at /voice/paging-groups: create the group, edit its members, pick a mode, and trigger the broadcast from the same screen. It is the last UCaaS sub-surface that used to live only in hardware, now next to ring groups, queues, and park in the dashboard.
Anatomy of a page
A page moves through four parts:
- The pager group. A named set of members: teammates reached through their softphone, and SIP deskphones registered to the organization. A group also carries a mode (simplex or duplex; today both deliver the same one-way announcement) and, for the live open-mic broadcast, a 5-to-300-second timebox that hangs the speaker line up when the speaker runs long.
- The broadcast trigger. From the group list, Page opens the page dialog. Type an announcement (up to 500 characters) and paged deskphones speak it aloud over text-to-speech, with the exact wording in the teammate notification. Leave it blank and deskphones play the generic incoming-page notice ("Incoming page from
<group>") instead, so the existing page still announces itself. The mode can be overridden per page, for a one-off announcement on an intercom group or vice versa. - Two delivery paths. A page reaches members two ways at once. SIP deskphones on the roster (the ceiling or bay endpoints) are paged directly over an internal call to each phone's registered SIP contact, and phones honor auto-answer so the announcement plays out loud in the zone within milliseconds. Right now every teammate in the organization sees the "Incoming page" notice with the announcement text wherever they are logged in; per-roster notice delivery is on the roadmap, and the deskphone side is already roster-scoped.
- Paging-only membership. Groups work best as zone rosters: the ceiling endpoints over the warehouse floor, the desk sets along the retail wall, the people at the nurses' station. A page rings the deskphones on the roster; today every teammate in the organization also sees the incoming-page notice, so keeping a group scoped to the endpoints the zone actually needs is what keeps the overhead audio where it belongs.
After the page, Orbit reports how many member devices were notified and how many resolved, so the sender knows whether the zone actually heard it.
Operator playbook: when paging beats a ring group
The rule of thumb is audience shape. A ring group or hunt group solves "one caller needs any one of us." Paging solves "everyone in earshot needs the same sentence at the same time." Per vertical, that looks like:
- Warehouse. A forklift certification is needed at receiving, or a spill closes an aisle. The floor supervisor pages the Floor group from the tablet at the dock; the announcement plays over the zone endpoints and nobody stops scanning to answer a ringing handset.
- Retail floor. "Manager to register 3." The classic page exists because a checkout lane cannot be left unattended while someone hunts for a manager by radio. One tap, and every manager's device on the floor hears it.
- Medical ward. Porters, equipment runs, and bed-turnover coordination all want a short broadcast to a zone, not a phone tree. Teams typically set their own announcement discipline for overhead audio (for example, no patient identifiers in a typed or spoken page); Orbit leaves that policy where it belongs, with the tenant, and gives the typed-message path so announcements can be deliberate rather than shouted.
- Dealership service bay. A vehicle is ready to move, or an advisor is needed at a bay. Paging the service group reaches every technician at once instead of walking the bay or burning a radio channel.
In every case the failure mode paging fixes is the same: the message was for a place, and the phone system only knew how to call people.
How paging composes with the rest of the phone system
Paging is a broadcast layer on top of the same primitives the rest of the UCaaS surface uses:
- Ring groups and hunt groups handle the one-caller-one-answerer traffic; paging handles the announcements. The two divide inbound work from outbound-to-internal broadcasts. The operations guide to shared lines, call park, hunt groups, and hot-desking covers the automated distribution side.
- Queues hold external callers waiting for a free agent. Paging reaches the agents themselves: a supervisor who sees queue depth spike can page the floor instead of tapping shoulders.
- Call park holds a live caller in a shared slot. A page is the natural retrieval channel: "call parked in slot 2" goes to every device that might free up, and the first person who can takes it.
- Extensions are the dialable identity behind every member device. A paging group does not replace extensions; it addresses a set of them in one motion.
- Presence tells you who is free before you pick one person. Paging is for the moments when picking one person is the wrong question and the whole zone is the audience.
- Hot-desking decides which physical device a person owns today; paging decides which set of people hears the announcement. They compose: sign in at the bay desk and you are paged at the bay desk.
The attendant console sits on the same map as the staffed opposite: a person directing calls one at a time, beside a person addressing everyone at once. And AI-powered UCaaS in 2026 places both inside the wider pillar of extensions, voicemail, and the agent layer.
Configuration playbook, with numbers
The levers the group editor exposes, and how operators tend to set them:
- Members. At least one, and in practice one per endpoint or person that should hear the group. Zone-wide rosters are normal: dozens of deskphones over a floor plus the teammates who should hear the broadcast on their softphones. Cap the group at the endpoints and people the zone actually needs, up to 200 members.
- Mode. A group carries simplex or duplex. Simplex is listen-only and the right default for overhead announcements. On shipment today, pages from both modes deliver the one-way announcement: deskphones are paged, teammates are notified. Marking a group duplex now records the intercom intent against the group and keeps it ready for the two-way talk-back floor as live duplex intercom rolls out, without a roster rebuild.
- Max announcement. 5 to 300 seconds, 30 by default, recorded on the group as the broadcast timebox: the open-mic live broadcast hangs itself up at that mark so a forgotten mic never holds a speaker line open. Keep it at 30 or lower for simplex zones; long pages get ignored, and the cap is the discipline. A typed, text-to-speech message is pre-recorded by nature, so it plays through and the leg hangs up right after; the timebox is the live-mic guardrail, not a limit on the typed text.
- Typed message. Up to 500 characters, spoken aloud on paged deskphones via text-to-speech. Use it whenever the wording should be exact, from a noisy floor or a quiet ward. Leave it blank and the group gets the generic incoming-page notice instead.
- Per-page mode override. The dialog lets a single page flip the group's mode for that broadcast only, without touching the group's settings.
- Names and descriptions. Name the zone, not the department: Warehouse Floor, Sales Wall, Ward 4 East. Put who should answer in the description. A page button named after a place is self-explanatory at the moment it needs pressing.
- One page, one ask. A page is a sentence, not a meeting. If the topic needs discussion, page for the person and then call them.
Pages never leave your organization. A broadcast addresses only your own members' devices inside your tenant's voice path; it does not dial external numbers, and outbound calling in Orbit continues to terminate only over Devotel's wholesale softswitch, a path paging does not touch at all.
Frequently asked questions
What is the difference between paging and intercom?
Paging (simplex) is one-way: the sender types, and the announcement is spoken aloud on the group's paged deskphones while softphone members get the page on their screens. Intercom (duplex) is the two-way shape, where members talk back. On Orbit today a group carries the duplex mode setting and a page from either mode delivers the one-way announcement; live talk-back floors arrive as duplex intercom rolls out, and a duplex group is ready for them without a roster rebuild. Any single page can be forced back to simplex with the per-page mode override.
How is a page different from ring-all?
Ring-all makes every device ring and waits for a human to pick one up; the moment one answers, the rest go silent and the other listeners never hear the message. A page is a broadcast to the whole zone at once: every deskphone on the roster is paged with the announcement and plays it out loud, instead of the message reaching only the first person who grabs a handset. Ring-all finds one answerer; paging informs everyone.
Does a page call external numbers?
No. A page addresses member devices inside your organization only. Nothing about paging reaches the public network.
Can a page be sent away from the building?
Yes. The trigger lives in the browser dashboard, so a supervisor at a receiving desk, in the back office, or off-site opens the same group list and presses Page. Typed announcements make this practical from anywhere a keyboard is.
How do I know the page landed?
After each page, Orbit reports how many member devices were notified and how many resolved, so a sender sees the reach of the broadcast instead of guessing.
Published 12 October 2026.