EOI Exchange

The workflow, end to end

The 9-step EOIX workflow.

The shape matters. One rulebook owned by the carrier, two systems that share it, a real-time decision returned inside the enrollment session, and a portal that shows the carrier exactly what happened. This page is the product story written for the technical buyer.

Carrier writes the rulesEOIX runs the workflowBen Admin runs enrollment

  1. Step 01

    The carrier's underwriting team writes the playbook.

    Before any employee touches anything, the carrier's underwriting team finalizes the rulebook. Who gets approved automatically up to what amount (GI thresholds), spouse rules, what counts as an open-enrollment increase, late-entrant handling, grandfathering, and which products require EOI at all. Every later step follows this rulebook.

    Operational pain it removes

    Today these rules live in PDFs, tribal knowledge, and scattered config spreadsheets. They never land the same shape in every downstream system. That is why platforms misfire.

    Who cares most:CarriersUnderwriters

  2. Step 02

    Implementation translates the playbook into configuration.

    The carrier's implementation team turns the rulebook into Ben Admin configuration (so it knows when to trigger EOI), an EOIX workflow spec (so the interview knows what to ask), and the integration requirements that wire them together.

    Operational pain it removes

    Removes the broken-telephone problem where the rules and the configuration drift apart, causing enrollment surprises and post-OE rework.

    Who cares most:Carrier implementationBen Admin partners

  3. Step 03

    Ben Admin and the EOIX portal both see the same rules. The carrier still owns them.

    The configured rules go to two places at once. The Ben Admin (where employees enroll) and the EOIX portal (where the underwriting workflow runs). EOIX never owns the rules. The portal shows what was received, what was configured, what was tested. The carrier holds the pen.

    Operational pain it removes

    Closes the visibility gap. Today carriers cannot easily see whether the rules they wrote landed correctly in the systems running enrollment.

    Who cares most:Carrier governanceComplianceRisk

  4. Step 04

    The Ben Admin sets up the enrollment experience.

    The Ben Admin (the platform employees log into during open enrollment) wires up the shopping cart, the GI thresholds, when to trigger EOI, and how the final approved coverage flows to payroll. EOIX does not replace this. The Ben Admin still owns the experience.

    Operational pain it removes

    Settles the question of who runs enrollment. The Ben Admin runs enrollment. EOIX runs only the underwriting moment.

    Who cares most:Ben Admin platformsEmployers

  5. Step 05

    EOIX builds the carrier-approved workflow links.

    Using the carrier-approved spec, EOIX generates the launch links employees and spouses click. Each link is pre-populated with employee info, opens directly into Reflex IQ, and connects in real time to the underwriting engine and integration mappings for write-back. The carrier approves the configuration before anything goes live.

    Operational pain it removes

    Removes the build-it-from-scratch-every-time tax. Mappings, pre-population, write-back wiring all stand up against carrier-approved specs.

    Who cares most:CarriersBen Admin engineering

  6. Step 06

    Nothing goes live until the carrier certifies it.

    Before any employee sees the workflow, the carrier runs it end to end. EOIX tracks every test. Who ran it, when, what passed, what failed, certification status. Each test sits in one of these statuses: Pending, In Review, Validated, Exception Identified, Retest Required, Certified for Launch.

    Operational pain it removes

    Removes the find-out-at-open-enrollment-if-it-works risk. Today validation is informal and undocumented. EOIX makes it an auditable trail.

    Who cares most:Carrier qualityComplianceImplementation

  7. Step 07

    Open enrollment runs as normal, with one new path.

    During open enrollment, if an employee elects more coverage than the GI threshold allows, the Ben Admin triggers the EOIX workflow. The employee launches Reflex IQ inside the same session. They do not leave the enrollment flow. They do not get a paper form in the mail two weeks later.

    Operational pain it removes

    Removes the multi-day paper delay and the abandonment that follows. The work happens at the moment of intent.

    Who cares most:EmployeesEmployersBen Admin platforms

  8. Step 08

    The decision is binary, and it comes back in real time.

    Reflex IQ runs the interview, pulls the third-party data the carrier's rules require, and returns approved or not approved. No modified offers, no partial approvals, no delayed paper workflows inside the digital path. If not approved, the employee is directed to contact carrier underwriting to appeal through the traditional channel.

    Operational pain it removes

    Removes the multi-week underwriting cycle and the ambiguity of pending. Removes the liability fear of automated half-decisions because the boundary is sharp and the appeal path is human.

    Who cares most:Carriers (clear liability boundary)UnderwritersEmployees (certainty)

  9. Step 09

    The approved amount lands in the shopping cart while the employee is still on the page.

    The decision feeds the EOIX portal and, where integrations exist, the Ben Admin shopping cart directly. Worked example: employee elects $500,000 voluntary life. GI is $100,000. So $400,000 is subject to EOI. Carrier rules return full approval. Final coverage in the cart updates to $500,000 immediately, and payroll deductions are calculated by the Ben Admin off that final number.

    Operational pain it removes

    Closes the open loop. Today, after EOI approval, someone manually updates enrollment, payroll has to be reconciled, and employees often discover months later that elected coverage never took effect. Write-back closes the loop at decision time.

    Who cares most:EmployeesEmployers / PayrollCarriers

The boundary

What EOIX does, and what it deliberately does not.

The carrier holds the risk. The carrier holds the rules. EOIX runs the workflow that wraps the decision.

Next step

Book a technical walkthrough of the 9 steps.

We walk your underwriting, implementation, and engineering leads through the full workflow, the validation tracking, and the portal. No carrier names in the room without your consent.

Book a technical walkthroughSee the admin portalSee pillar one: Real-time underwriting