“Very simple information.” What an insurance client portal should hold, and how I’d build one.

Why do benefits clients keep emailing instead of using the portal?

Benefits clients keep emailing because most portals hold the wrong things. They’re built around documents: the plan summary, the certificate, the enrollment guide, each one a long PDF. An employee with a claims question doesn’t want a PDF. They want a phone number.

So they email HR, who emails the account manager, who looks it up and emails back. One question, three people, most of a day.

What do most agencies try first?

Most agencies try client portal software or send people to the carrier’s website. Carrier sites are good at carrier things: claims history, ID cards, finding a doctor. They don’t know which agency placed the plan, who the account manager is, or that the dental plan sits with a different carrier than the medical.

Some agencies build a shared folder or a page on their own site. That works until nobody updates it after renewal, and the phone numbers still point to last year’s carrier.

Wanna fix it?

A benefits client portal gets fixed with five simple pieces of information, a chatbot that answers from the agency’s real answers, and an account manager who takes whatever the chatbot can’t.

1. Show each person their own plans. The medical, dental, vision, and life plans they’re actually enrolled in, named the way their ID cards name them.
2. Write the FAQs from your inbox. The questions account managers answer every week, answered once, in the words you already use.
3. List who to call at the carrier. One number per carrier, labeled by plan, updated at every renewal.
4. List who to call for claims. A separate line, because claims often go to a different team. In a self funded plan, that’s usually the TPA, the company that processes the claims.
5. Give them a line to a person. A support line or email that reaches an account manager at the agency, with a name attached.

Then the chatbot. If there were a 24/7 chatbot with a full database of questions and answers pulled straight from our email, plus every plan design for the health plans and the ancillary benefits, that would be a mainstay in a client portal. I built that chatbot once. Finn lived on every landing page I built, and it still runs on my last agency’s website. Anything it isn’t sure about goes to the account manager.

What would it look like once it’s running?

Once it’s running, an employee opens the portal, sees their own plans, and either finds the number or asks the chatbot. The account manager gets the questions that need judgment: an eligibility call, a claim that went sideways, a new hire who missed the window.

The agency’s job is keeping it current. At every renewal, someone updates the plans, the carrier numbers, and the FAQs.

I haven’t built the full portal for a client, so I can’t tell you how many emails it saves. Three pieces I’ve built are close. Finn is the first: about 300 emails’ worth of real questions and answers plus all of the agency’s plans. My CRM drafts replies to incoming email and holds each one in a queue until I approve it. My enrollment platform builds a page for each employee with their own plans and per paycheck prices. It ran in production for one group, though that group’s employees ended up enrolling on paper.

Can you do this yourself?

Yes. A simple web page per client with the five pieces, built in whatever website tool you already use, covers most of it. Put it behind a password if plan details are on it. Write the FAQ from the last month of account manager email.

The page stops being enough when the questions outnumber the answers on it, or when updating every client’s page after renewal becomes its own job. One or two big clients, build the pages by hand. A full book of groups, build the portal once and feed it from your plan data.

Quick answers

What is an insurance client portal?

A private page where a client’s employees find their plans, answers, and the right phone numbers.

What should an employee benefits portal include?

Enrolled plans, FAQs, carrier contacts, claims contacts, and a line to an account manager.

Can a chatbot answer benefits questions in a portal?

Yes, if it answers from the agency’s own emails and plan designs and hands anything uncertain to a person.

Who handles claims in a self funded plan?

Usually a TPA, a third party administrator that processes the plan’s claims.

How often does a portal need updating?

At least at every renewal, when plans, carriers, and phone numbers can change.

Has DoBetter built this?

The chatbot, yes. Chris Cordon built Finn, which still runs on his last agency’s website. The portal, not yet for a benefits client. He’d build it from the five pieces above plus a chatbot like Finn.