Member enrollment and changes
How do we enroll a member or process a life event change with the member, dependent and plan details captured, the eligibility documents checked, and the change written to the enrollment system?
Run enrollment as a verified application the member finishes on their own phone. Callvu prefills the member from the employer's or the exchange's file and the plan's data, takes the application or the change (a new hire, a marriage, a birth, a loss of other coverage, a move) on a secure screen with only the fields the event needs, chases the eligibility documents the event requires (a marriage certificate, a birth certificate, a loss of coverage letter) through a link within the special enrollment window, reads and checks each against the event and the dates, applies the plan's enrollment rules and effective date logic, routes an exception to the enrollment team in the Decision Desk, and writes the member, the dependents and the coverage to the enrollment system of record with the ID card and the confirmation issued.
In scopeComplex: multi-party handoffsCallvu moves: prefill, chase and verify, write back
Last updated November 7, 2026.
The problem today
The newborn was added to the file sixty-five days after the birth, and the first pediatric claim denied for no coverage.
Enrollment arrives from employers' files, brokers, the exchange, and members themselves, each with a different form. A life event change comes by phone with a promise to send the certificate. The window for the special enrollment period closes while the document sits in a mailbox, the dependent is never effective, and the family finds out at the first claim. The enrollment team re-keys applications and chases paper instead of checking eligibility.
The rules are specific: the qualifying life events and their windows (thirty or sixty days from the event, by the plan and the market), the documents that prove each event, the effective date logic (the first of the month after the event, the date of birth for a newborn, the first of the month after the application), and the privacy obligations for the health information the application carries. Dependents added without proof cost the plan money and the member a surprise later.
An enrollment the member completes with the documents attached, inside the window, is one the claims will pay.
How it runs
From the requestto the system of record.
A new enrollment or a change arrives from the member (the portal, a call, a link), an employer or broker file, or the exchange. Callvu opens the enrollment with the event and its window.
- Member
- Confirms the prefilled data, enters the event and the dependents, uploads the documents and signs on their phone.
- Employer or broker
- Submits the group's enrollment and changes through their link or file and sees status.
- Enrollment team
- Decides exceptions in the Decision Desk.
- Callvu
- Prefills, captures, chases documents, checks, applies the rules, routes and writes.
Prefill and capture the event
The member's identity, address, the group and the plan options, the current coverage and the dependents on file are prefilled from the employer's or exchange's file and the plan's data; the event (new enrollment, open enrollment election, a qualifying life event) is captured with its date, and only the fields the event needs are asked: the dependents with relationship and date of birth, the plan choice, the other coverage, the primary care physician where the plan requires one.
Chase and verify the documents
The documents the event requires (a marriage certificate, a birth certificate or hospital record, a loss of coverage letter with the end date, a court order for a dependent) are requested through a link with the window's deadline visible, read on arrival and checked against the event date and the names, and a document that does not match is put back to the member with the specifics.
Apply the rules and decide exceptions
The plan's enrollment rules run: the event is a qualifying one, the application is inside the window, the dependents are eligible by age and relationship, the plan is available for the group and the area, the effective date is computed by the event; a late application, an unmatched document, an ineligible dependent or a conflict with the employer's file goes to the enrollment team in the Decision Desk with the record and only the allowed outcomes.
Write back
The member, the dependents, the plan, the effective date and the documents are written to the enrollment system of record, the ID card and the confirmation are issued, the premium or the payroll deduction is set with the employer or the billing system, and the member sees the coverage in the portal.
Where it ends: The enrollment or the change was completed by the member inside the window with the documents checked, the rules applied and the effective date computed, and the enrollment system of record holds the coverage the claims will pay against. The Decision Trace shows the prefill sources, the rules applied and any decision; the Audit Trace shows the documents, the signature and the write.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The portal, a call with a link, the employer's or broker's link or file, or the exchange; the member finishes on their phone.
The back office
The enrollment team decides only exceptions; the enrollment system is written by the process.
The Decision Desk
- A late application, an unmatched document, an ineligible dependent or a conflict with the employer's file goes to the enrollment team in the Decision Desk with the record and only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
23 hospitals in the Ministry of Health network run on Callvu.
Across Callvu customers
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
How long does a member have after a life event?
Thirty days for group plan special enrollment (sixty for Medicaid, CHIP and marketplace events); the window and its deadline are on the request and the document chase.
What documents are needed?
Those the event requires: a marriage certificate, a birth certificate or hospital record, a loss of coverage letter with the end date, a court order for a dependent, uploaded through a link and checked against the event.
When is coverage effective?
By rule from the event: the first of the month after the request for most events, the date of birth or placement for a newborn or adopted child.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.