Your people, already caught up
A full call center for human staff sits inside the same product as the agents. Queue, routing, dial pad, assist, wrap-up, tickets, QA and a supervisor view. When a call moves from an agent to a person, nothing about it starts over.
- Claim 4821 denied, code CO-197.
- Agent confirmed the appeal window is open.
- Promised a specialist would explain the code.
One queue, agents and people in it together
The queue does not separate calls an agent is handling from calls a person is handling. A supervisor watching it sees the whole line: who is waiting, why they rang, how long it has been, and who has them. Which is the only way to answer the question that actually matters, which is whether the line is coping.
Routing
A call reaches the right person because of what was decided before it rang, not because someone picked it out of a list.
The desk
Staff work one screen. The live transcript runs beside the call as it happens, so nobody is reconstructing what was said thirty seconds ago. Caller history is one panel over: previous calls, previous tickets, what was promised last time.
Assist while the call is live
Staff get the same grounded answers the agents use, in a panel beside the conversation, cited to the section of the plan document it came from. It is the plan knowledge your newest hire does not have yet, available without putting the member on hold.
Suggestions are prompts, not scripts. Nobody is reading them aloud. They are there so the answer is in front of someone who then says it in their own words.
“I need to know if the MRI needs prior authorization.”
Prior auth required for advanced imaging on this plan. Turnaround is 3 business days.
Warm transfer carries the call
When an agent hands to a person, the transfer is not a phone number. The staff member accepting it gets the claim in question, what was already checked, and anything the agent committed to. They open on the member’s actual problem rather than on an introduction.
That is the difference between an AI that deflects calls and one that clears the routine so your people spend the day on appeals, hardship and the calls that need judgment.
Wrap-up, and what it feeds
Dispositions are configured per call center rather than fixed, so the list matches how your team actually categorises work. Notes can start from a template. A ticket can be created or linked from the wrap-up itself, which is what stops follow-up work from living in someone’s head.
Tickets
Some calls end with work left to do. A ticket carries it: a queue, a priority, an assignee, a due date, and links back to the call, the claim and the member. Ticket queues have their own routing, so the appeals backlog is not a shared inbox.
What a supervisor sees
Live metrics across the top: in queue, longest wait, answered, within SLA, abandoned, staffed. Then the floor itself, who is on a call and who is in wrap-up and who is on break, with how long they have been there.
The same view runs as a wallboard for a screen on the floor, read-only and stripped to the numbers worth looking up at.
Quality, without a listening rota
Scorecards are built per line from your own criteria, and a call can be scored from the same screen it is reviewed in, with session replay to see what the member and the agent were doing. Because every call is analyzed automatically, the calls a reviewer opens are the ones worth opening rather than a random sample.
Callbacks, missed calls and surveys
Calls that abandoned and calls that came in after hours are a list, not a gap in a report. Callbacks scheduled during a call appear as work with a time attached. A survey at the end of the call feeds the same reporting as everything else.
It slots into the contact center you already run
Most health plans are not replacing their telephony to try this. Vocalis connects natively to the platforms already carrying your calls, so numbers, transfers and call data keep flowing through the stack your team knows.