Your source for Plansight help, training, and best practices.
Integrations
An overview of every system Plansight connects to — BenefitPoint, Employee Navigator, IDEON, A.M. Best, the Plansight Open API, and Bright Benefits — and what each integration does for your broker workflow.

Plansight sits in the middle of the broker's stack. The systems on either side — your agency management system, your enrollment platform, your plan-data sources, your post-sale benefits tools — were never built to talk to each other, which is why so much of the broker's day gets spent typing the same data into two places. Plansight closes those seams. The quote you build flows into the carrier-of-record system. The plans you sell appear in the employee app. The credit picture for every carrier shows up next to the rate. The data moves; the broker doesn't have to.


Here's what we connect to, and what each connection does for you.


BenefitPoint

A two-way sync with Vertafore's BenefitPoint — the system most brokerages use to manage their book of business and carrier-of-record relationships. When you quote a plan in Plansight, the sold plan flows into BenefitPoint with its full benefit design and rate structure. When the agency adds a renewal in BenefitPoint, the renewal context comes back so your next quoting cycle starts current. No re-keying, no reconciliation, no "which system has the right number?" The two systems stay in step automatically, every day.


Employee Navigator

Plansight is bi-directional with Employee Navigator, the enrollment platform a large share of brokers already use post-sale. Two flows do the work. Pulling in: Plansight can pull a group's census directly from Employee Navigator into a community-rated RFP — no spreadsheet, no Flatfile, no version control across email threads. Pushing out: when you finalize a sale in Plansight, the elected plans and the employer profile push into Employee Navigator so enrollment opens with carrier-accurate plan setup the first day. The hand-off from quote to enrollment, which is one of the most error-prone moments in the broker's year, becomes a button click.


IDEON

IDEON (formerly Vericred) is the plan-and-rate engine behind community-rated and ACA quoting. Plansight reads plan attributes, rates by rating area, and benefit summary PDFs from IDEON automatically, so when your broker quotes a small group, Plansight already has the right plans available at the right prices for the right ZIPs. The broker doesn't manage the plan library, doesn't import a rate sheet, and doesn't chase carrier portals for the current benefit summary. The data is there when the quote starts.


A.M. Best

A.M. Best is the insurance industry's standard for rating carrier's financial strength. Plansight pulls the full A.M. Best universe every night and stamps each carrier in the application with the current rating, outlook, and financial-size category. The broker sees the credit picture in one click — right next to the quote, never a tab away — so the conversation with the employer about why this carrier always has the data behind it. No separate lookup, no stale ratings.


Plansight Open API

The integrations above bring data into Plansight. The Open API is how partner systems read out. It's a bearer-token authenticated REST API, brokerage-isolated and rate-limited, that lets a brokerage's own dashboards, BI tools, or partner ecosystem reach into Plansight for employer and plan data. If a brokerage wants to surface Plansight data inside their own front-end, build internal reporting, or hand a partner read access to sold plans for a specific employer, the Open API is the door. We version it, document it, and run it as a production surface — not a side project.


Brite Benefits

Bright Benefits is a downstream consumer of the Plansight Open API and the post-sale employee-experience layer that closes the loop. When you enable Bright Benefits inside Plansight, Bright pulls the medical, dental, and vision plans you've actually sold for that employer — directly, no manual setup — so the employees see what they actually have, the way they have it. Plansight builds the plan picture once; Bright shows it to the employees who live with it.


Why it adds up

Every integration above does the same job from a different direction: it removes a moment in the broker's day where someone has to manually move data from one system to another. BenefitPoint keeps the carrier-of-record system aligned with quoting. Employee Navigator keeps enrollment aligned with sale. IDEON keeps the plan library aligned with reality. A.M. Best keeps the credit picture aligned with the quote. The Open API keeps the brokerage's own tooling aligned with Plansight. Bright Benefits keeps the employee experience aligned with what got sold.


Plansight isn't trying to replace the systems brokers already use. It's the connective tissue between them — so the quoting, sale, and post-sale lifecycle reads as one continuous flow instead of six disconnected systems sharing nothing but a spreadsheet.



Questions this article answers

• What systems does Plansight integrate with?
• Does Plansight connect to BenefitPoint?
• How does Plansight work with Employee Navigator?
• Can I pull a census from Employee Navigator into Plansight?
• What does the IDEON integration do?
• Does Plansight show A.M. Best carrier ratings?
• How does Plansight share carrier financial-strength data?
• Does Plansight have an API?
• Can a partner system pull data from Plansight?
• How does Plansight work with Bright Benefits?
• Does Bright Benefits pull data from Plansight?
• What integrations are bi-directional?
• Does Plansight replace BenefitPoint or just integrate with it?
• Why are integrations important in Plansight?