Part of The Busy Broker’s Guide to Jobs to Be Done Series: The real jobs employee benefits brokers deal with every day, and how BenefitsBridge gets them done.
A client calls with a question. Before you can answer it, you need to know who the main contacts are, what coverage they have, what happened at the last renewal, what your team has discussed with them recently, and whether there is anything still outstanding.
How many places do you need to look?
For many employee benefits agencies, the answer is more than one. Some information is in the agency management system. Other details are in spreadsheets. Recent conversations are sitting in Outlook. Someone maintains a separate list for key contacts. And there may still be information that lives primarily in the head of the account manager who works with the client every day.
None of those decisions necessarily seemed inefficient when they were made. The problem becomes apparent over time, as the agency accumulates more clients, more employees, more plans and more information.
The job isn't simply to "centralize data." The real job is to be able to understand the full history of a client when you need it, without having to reconstruct that history every time.
Five places can easily become the normal way of working
We spoke with one benefits agency that described exactly how this happens. Before centralizing more of its client information, the team maintained separate lists for different purposes: a "who to call" list, a birthday list and contact lists for individual clients. Now the team can go into one system, run the appropriate report and update the information there.
That may sound like a small operational improvement, but it points to a much larger issue. Every separate list creates another version of the client. The spreadsheet might tell you one thing, the contact list another, while the policy records and recent activities contain other pieces of the story.
Eventually, someone has to determine which one is current.
The more places employees have to maintain, the more opportunities there are for information to become incomplete or outdated.
The real test comes when someone else needs the information
A fragmented client history may not seem like a serious problem when the account manager who knows the client best is sitting at their desk. They know where everything is.
But what happens when that person is on vacation, out sick, leaves the agency or simply isn't available when the client calls? Someone else has to reconstruct the account. They need to know the right contacts, which policies are active, what changed recently, what is coming up and what has already been discussed.
This is why having a complete client history is about more than saving employees a few minutes of searching. It makes client knowledge agency knowledge rather than individual knowledge.
That's especially important as an agency grows. Clients should not receive a completely different level of service depending on whether the one employee who knows their account happens to be available.
A client record needs to be more than a contact record
Putting names, phone numbers and email addresses into one system is useful, but it doesn't solve the larger job. The account itself needs to provide a starting point for understanding the relationship.
In BenefitsBridge, information is organized from the account level down, giving the team a way to move from an employer account into the information associated with that client.
That includes the benefits information that makes an employee benefits relationship more complicated than an ordinary CRM relationship. For example, a client may have medical, dental, vision and disability policies. BenefitsBridge can maintain active policies as well as renewed or terminated policies, and users can drill into individual policies to see details such as the carrier, coverage type, policy number, effective date and primary producer. Policy terms can contain additional information including funding type, rate type, covered lives and premium information.
That changes what it means to "look up a client." You're not simply finding an address and phone number. You're getting closer to answering the question that actually matters: What is going on with this client?
The information becomes more useful when you can ask questions of it
Centralizing information isn't very valuable if the only way to use it is to open records one at a time. Sometimes the job is to understand one client. Other times you need to find a group of clients that share a particular characteristic or answer a question about your book of business.
One agency using BenefitsBridge described a request from leadership to see its groups based on revenue and headcount. Rather than requesting a new custom report, the user could add the needed columns, export the information to Excel and have what leadership needed.
The same agency said that after investing the time to build its data, it could see the value of having that information readily available.
That's an important distinction. The goal isn't to collect more data for the sake of collecting data. The goal is to have usable information when there is a job to do.
One client shouldn't require five searches
Benefits brokers deal with enough complexity already. Finding out what your own agency knows about a client shouldn't add another layer.
The ideal isn't necessarily that every piece of information looks exactly the same or that employees never use Excel or Outlook again. Those are useful tools and, in most agencies, aren't going anywhere. The goal is to have a reliable home for the client relationship so employees know where to start.
When someone needs to understand an account, they shouldn't have to hunt through a collection of disconnected lists and files or wait for the person who "knows that client" to become available. They should be able to find the client, understand the relationship and get on with the actual job that needs to be done.


