Quick answer: Some businesses still front every inbound call with a person. Law firms, medical clinics, insurance offices, and a lot of smaller companies route callers through a front desk because an IVR menu cannot screen a caller the way a receptionist does. The Attendant Console in Devotel Orbit is the screen that role works from: a live view of who is free, who is waiting, and which calls are parked, with transfer, park, retrieve, and release on the already-active call legs.
Who still needs a human operator
Not every business has automated its front line away. The ones that keep a person answering the phone usually share a reason:
- A law firm wants every caller screened by someone who can tell a referral from a sales pitch before it reaches an attorney.
- A clinic keeps a receptionist on the line because patients expect a person, and a missed caller is often a missed appointment.
- A service business with one office number still points that number at a desk, and the desk belongs to whoever is covering it that day.
The incumbent answer for that role is a desk phone with a lamp field: a hardware console that lights up which colleagues are on a call, plus whatever the phone system vendor teaches in a training session. The console works, but it is tied to the desk, it takes vendor-specific training, and it does not travel home with a hybrid receptionist.
The operator work loop
Strip the job down and one loop covers most of the day:
- See who is free. The lamp field shows live extension presence, so the operator glances at the screen before choosing a destination, rather than transferring blind and hoping.
- Answer the waiting caller. Callers still ringing or waiting in the queue appear in a waiting lane, so the operator picks the next one instead of the public number ringing everywhere at once.
- Send it to a person. The operator picks a free extension and transfers the caller straight to it. The caller carries on while the operator is back on the waiting lane.
- Manage the shared lobby. If nobody suitable is free, the operator parks the caller in the shared lobby. The right colleague retrieves it from their own softphone or desk phone when they are back, and whatever will not be answered gets released rather than left parked all afternoon.
That whole loop used to live on hardware. On a cloud phone system it belongs in the browser, next to everything else.
The shipped surface
The Attendant Console lives at Voice → Attendant console in the Devotel Orbit dashboard. It composes three primitives that already exist in the UCaaS pillar onto one screen:
- Waiting calls. A live list of inbound callers still ringing or queued.
- Extension presence. A lamp field of every colleague's line state, fed by the same busy-lamp signals the softphone uses.
- Park lobby. The shared parking bay with retrieve and release for each parked call.
The operator picks a waiting caller, taps a free extension, and the call transfers while the caller is already connected. Park, retrieve, and release work the same way: they act on call legs that already exist. The console never dials a new outbound call. It is the control surface for calls that are already on the switch, which is also why a revoked operator session cannot originate anything from that page.
Because the console runs in the browser, the role stops being tied to a desk phone. A receptionist covering from home gets the same waiting-call lane, the same lamp field, and the same park lobby, over the same tenant account.
Where the console sits in the cloud phone pillar
A UCaaS pillar is not a single feature. It is the set of surfaces a business phone system ships, and each of them solves a different distribution problem:
- Extensions route calls to people.
- Ring groups and hunt groups distribute a call across a team with no human in the path.
- Call park holds a caller in a shared slot so any colleague can pick it up.
- The attendant console puts distribution back in front of a human, when screening is the point.
The console is the last panel of that set: staffed routing for the businesses that want it, sitting next to the automated primitives rather than replacing them. The operations guide that covers shared lines, call park, ring groups, and hot-desking walks the automated side. The console is what the front desk gets when the team still wants a person deciding.
AI-powered UCaaS in 2026 maps where the console sits next to extensions, voicemail, and the AI agent layer in the wider pillar. Console operations stay inside the same Devotel-run voice path as every other Orbit call: inbound reach never changes hands, and outbound still terminates only over Devotel's wholesale softswitch.
Frequently asked questions
What is an attendant console?
An attendant console is the operator's screen: it shows live extension presence and the waiting inbound calls, and it exposes the actions that run an already-active call, such as transfer and park. It replaces the desk-mounted receptionist console with a browser page.
Does the attendant console make outbound calls?
No. The console operates on calls that already exist: transfer to an extension, park to the shared lobby, retrieve, or release. It does not originate new calls, so taking away an operator's access cannot leave an open dialer behind.
How is this different from a ring group or hunt group?
Ring groups distribute an inbound call automatically to a list of extensions. The console is staffed: a person picks who each waiting caller goes to. Use ring groups for the unstaffed teams; use the console where the front desk screens callers by hand.
Can the operator work from home?
Yes. The console is a dashboard screen, not a hardware phone, so everything the role needs travels with the operator's login, subject to the tenant's access rules.
Who typically uses it?
Law firms, clinics, insurance offices, service businesses with a public office number, and any team whose front desk is still a person.
Published 26 September 2026.