With Noyo, you get everything you need to power seamless benefits enrollment and management. These guides are for ben-admin platforms who are integrating with Noyo’s API. After one up-front integration, you’ll be connected to an entire ecosystem of carrier partners. You’ll spend less time dealing with multiple pipelines and inefficient data transmission and more time creating great benefits experiences for your customers. Here’s what you’ll use Noyo for:
  • Connecting with many carriers through the same API
  • Getting on-demand access to the carrier’s version of enrollment data
  • Automatically submitting enrollment changes for employees as they happen
  • Confirming that coverages and enrollment changes are correct
  • …and anything else you can dream up!

​
Connect with many carriers through the same API

Noyo works closely with insurers to build deep, bi-directional integrations into their existing systems. We design and build for each carrier’s specific capabilities–whether that’s endpoints, files, or a mix of the two–so you don’t have to. Plus, we manage all upgrades, security, and connection maintenance so you get a universal experience across carriers.

​
Get on-demand access to the carrier’s version of enrollment data

When you manage a group through Noyo, we source that group’s data from the carrier and make it available to you through our endpoints. This opens up a world of possibilities, including faster group setup, better reporting, identifying discrepancies, and a better OE experience.

​
Automatically submit enrollment changes for employees as they happen

Coverage or eligibility changes that occur during policy administration, like enrolling new members or editing someone’s demographic details, can be sent and managed through Noyo’s API. No portals, emails, or weekly files; with Noyo, most changes are at the carrier for processing within 15 minutes of being made.

​
Confirm that coverages and enrollment changes are correct

Noyo validates and routes changes to the correct carrier(s), who process them in their own systems. Then we confirm the changes and make the updated data available to you. All changes sent through Noyo are also trackable. Did the carrier accept that new hire enrollment? There’s an endpoint for that.

​
The Benefits Lifecycle

Noyo handles enrollment data for employee health and supplemental benefits, including medical, dental, vision, life, accident, and disability insurance coverage. The lifecycle of a group’s coverage plans generally looks like this:
1

Shopping

A broker presents different plan options to the group admin
2

Quoting

The group submits information to carriers to get quotes for plans
3

Selling

The group selects their plans and signs the contracts
4

Installation

The carrier(s) put the group’s selections into their system(s)
5

Setup

The ben-admin platform builds the group’s selections in their system
6

Enrollment

Employees use the ben-admin platform to choose which plans to enroll in or waive
7

Maintenance

Employees use the ben-admin platform to make updates to their data throughout the plan year
8

Open enrollment and renewal

The broker and group admin decide whether to continue the same plans for the next year. This is the time for employees to re-enroll or choose different plans.

​
Where does Noyo fit in?

Noyo enters the picture after Step 4 - Installation. All of the shopping, quoting, and selling has been done, and the carrier has already installed the group’s plan information in their systems. This often means that they have already received census data, which is typically gathered by the group’s broker and sent as a file. Noyo can help you with Step 5 - Setup by making the carrier’s data available for you to use if you are setting up the group in your own system. See Using Noyo Data for more on what data you can get through our endpoints. During Steps 6–8, your Noyo integration will take the place of whatever you’re using today to transmit enrollment and demographic changes to insurance carriers. Examples of current methods include EDI (834, .csv, LDEx), carrier portals, paper forms, custom-built integrations, or phone calls.