No broker or employer is expected to know every question in this series, or what every answer means. I have written them out so you can use them. Putting them together, knowing which threads to pull and what one answer means next to another, is the work I do with plans and brokers in Under the RFP.
What the model looks like
During implementation and the first weeks after go-live, you have a full team: implementation leads, vendor partners, and the people setting up your plan. Once that period ends, there is no assigned contact. Questions go to a general mailbox, a chat tool, or a service queue, and whoever is available answers them.
This is a legitimate model, and it is becoming more common. For straightforward plan designs, for groups with a strong broker or HR team that holds the plan’s history, or for blocks of business where the broker is effectively the client, a responsive shared channel can be faster than waiting on one person.
The handoff
Ask when the implementation team steps back, and what decides it. Is it a date on the calendar, or a set of open issues being closed? Ask what gets handed off and to whom. An implementation that is still producing problems on day 91 needs someone to own them on day 92.
When something breaks
A general mailbox is good at answering a question. It usually is not built to notice that three tickets from the same group over two months share a cause. That is the gap in this model, and it is where groups can feel lost.
- Who owns your group after the handoff: a person, a pod, or a queue?
- When an issue is bigger than the shared channel can handle, who is the escalation contact? Get a name and a role, not a department.
- How does the TPA spot a pattern across tickets from one group when different people answer each one?
- Does the broker have a different path in than the group?
Who is answering?
The operations knowledge that matters for a dedicated account manager (Post 6) matters just as much here. Ask who staffs the shared channel, what their background is, and whether they can direct work or only pass it along. A shared queue can only resolve what the operation behind it can fix.
Can you reach a person?
Ask for the response time on the shared channel and whether it is measured. Ask whether there is a phone or text line a person actually answers, and what you do when something is urgent on a Friday afternoon.
What the sales cycle may not show you
During sales and implementation you will meet senior people who will not be your contact in month seven. Ask directly who you will be talking to after the handoff. If you can, ask for a reference from a group that is past its first year in this model.
What it means on your side
If there is no named contact and no defined escalation point after go-live, someone on your side will be the one holding your plan’s history. Usually that is the broker. That is workable when you plan for it, and much harder when you find out after something goes wrong.
Frequently asked questions
Is a TPA without a dedicated account manager a red flag?
By itself, no. It fits some groups well. What matters is the handoff, the escalation contact, and how patterns get caught.
What should I ask about the shared inbox?
Who staffs it, how fast it responds, whether that is measured, and who you escalate to when a ticket is not enough.
Who holds the plan’s history when a TPA uses a shared service model?
Often the broker or the group. Know that before you sign.