Who it is for
Same platform. Four very different jobs.
Four portals, four data boundaries, all built in. None of them can see the others.
TPAs
Many client programs. No chance of them touching each other.
Every table carries a broker id and every request is scoped from the database, not from what the browser sent. Adding a client program is configuration, not a deployment.
Book a demo for tpasWhat you get
- Row-level isolation between brokers, enforced in the API
- Branding, products, pricing, and rules per broker
- One admin, several brokers, one login
- Group and single-bill CHOICE administration
- Usage billing per broker from the live ledger
Vendors & care teams
You work across programs. Your queue should too.
The vendor portal works across brokers on purpose. Staff resolve members through their active enrollment, so six programs is one queue rather than six inboxes.
Book a demo for vendors & care teamsWhat you get
- One queue across every broker you serve
- Office 365 email threaded to member, case, and request
- AI summaries, bill parsing, and draft replies, opt-in
- NPI lookup and CPT pricing beside the case
- Zoom calls stitched to the member with summaries
Agencies & affiliates
Quote it, enroll it, get paid. No spreadsheet.
Affiliates get their book, their downline, and their commissions in one portal. Owners see the whole agency. Recruiting an affiliate is a link with a contract code.
Book a demo for agencies & affiliatesWhat you get
- Quick quotes and AI-assisted plan proposals
- Reusable enrollment links and marketing links
- A prospect CRM with AI follow-up, or bring your own
- Live commission ledger, payouts, clawbacks, advances
- Training modules, quizzes, and leaderboards
Two of these at once?
Plenty of organizations are. Describe the program and we will map it.