Low-income program enrollment (Lifeline)
How do we enroll a customer in the Lifeline program with eligibility verified against the national verifier and the benefit applied to the account on the rules?
Run the application as the program's own flow with the verifier inside it. Callvu prefills the applicant from the account where one exists, takes the application on a secure screen (the identity, the address, the household, the qualifying program or income basis, the one-per-household certification and the consents the program requires), submits the eligibility check to the national verifier (or guides the applicant through the verifier's own application where the state requires), chases the documentation the verifier requests (a program card, an income document, a household worksheet), classifies the result (approved, pending documentation, denied with the reason), routes a duplicate, an address flag or a verifier dispute to the program desk in the Decision Desk, enrolls the subscriber in the national database, and writes the benefit to the account in the BSS, the system of record, with the recertification date set.
In scopeComplex: multi-party handoffsCallvu moves: prefill, chase and verify, decide, write back
Last updated November 7, 2026.
The problem today
The applicant qualified, the paper application was missing the household certification, and the benefit started two months late.
Lifeline is a federal benefit with strict rules and real penalties for the carrier that gets it wrong: a subscriber enrolled without verified eligibility, a duplicate in a household, a benefit left on after the subscriber stopped qualifying. The carrier's answer has been paper and caution: long applications, repeated requests for documents, and applicants who give up before the benefit starts. The program's national verifier exists to make the eligibility decision, and the carrier's job is to get the application to it complete.
The FCC's Lifeline rules set the eligibility bases (participation in qualifying programs or income at or below the threshold), the one-per-household limit with the household worksheet, the required certifications and consents, the national verifier's role in the eligibility decision, the documentation it may require, the enrollment in the national accountability database, and the carrier's obligations on activation, usage and recertification. The application is a form with rules, and the rules are the process.
An application complete at submission, with the verifier's result applied by rule, is a benefit that starts when the applicant qualifies.
How it runs
From the requestto the system of record.
A customer applies for the Lifeline benefit in the app, on the web, in a store or on a call, as a new or an existing subscriber. Callvu opens the application.
- Applicant
- Completes the application, certifies and consents, and provides documents the verifier requests on a secure screen.
- National verifier
- Decides eligibility and holds the enrollment in the national database.
- Program desk
- Decides duplicates, address flags and verifier disputes in the Decision Desk.
- Callvu
- Prefills, takes the application, submits to the verifier, chases documents, classifies, routes, enrolls and writes.
Prefill and take the application
The applicant's identity and address are prefilled from the account where one exists; the application is taken on a secure screen with the program's required elements: the identity (the name, the date of birth, the last four digits of the identifier or the alternative the rules allow), the residential address (with the temporary address attestation where applicable), the eligibility basis (the qualifying program, or the household income with its size), the one-per-household certification and the household worksheet where the address is shared, and the certifications and consents the rules require, in the applicant's language.
Chase and verify with the verifier
The eligibility check is submitted to the national verifier through its carrier interface (or the applicant is guided through the verifier's own application where the state requires it); the verifier's requests for documentation (a benefit card or award letter, an income document, an address proof, the household worksheet) are chased from the applicant through a link with the specific item named, read on arrival and forwarded; the result is classified: approved, pending documentation, or denied with the reason.
Decide exceptions
An approval proceeds by rule; a duplicate subscriber or household flag, an address the verifier cannot validate, an identity mismatch, or an applicant's dispute of a denial goes to the program desk in the Decision Desk with the application and the verifier's response and only the allowed outcomes: resolve the duplicate with the applicant's choice, resubmit with corrected data, refer the applicant to the verifier's appeal, or close with the reason.
Enroll and write back
The approved subscriber is enrolled in the national accountability database with the carrier's identifier, the benefit (the service discount and any device benefit the program offers) is applied to the account in the BSS, the system of record, the service is activated or the discount starts within the rules' period, the usage requirement and the annual recertification date are set, and the applicant receives the confirmation with the program's terms.
Where it ends: The application reached the verifier complete, the eligibility decision was applied by rule, the exceptions were decided by the program desk, and the subscriber is enrolled in the national database with the benefit on the account and the recertification scheduled. The Decision Trace shows the application elements, the verifier's result and any decision; the Audit Trace shows the submission, the document chases, the enrollment and the write with time.
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 app, the web, the store or a call with a link; the applicant completes and provides documents on a secure screen in their language.
The back office
The program desk decides only duplicates, flags and disputes; the verifier decides eligibility and the BSS applies the benefit.
The Decision Desk
- A duplicate flag, an unvalidated address, an identity mismatch or a disputed denial goes to the program desk in the Decision Desk with the verifier's response and only resolve the duplicate, resubmit corrected, refer to the verifier's appeal, or close with the reason.
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.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
AT&T runs close to 100 processes on Callvu, used by 55,000 agents.
Questions
What buyers ask next,answered plainly.
Who decides eligibility?
The national verifier, from the application the process submits complete with the certifications; the carrier applies the result by rule and enrolls the approved subscriber in the national database.
What documents might be needed?
Whatever the verifier requests for the eligibility basis: a benefit card or award letter, an income document, an address proof or the household worksheet, chased with the specific item named.
What happens after enrollment?
The benefit is applied to the account, the service is activated within the rules' period, usage is tracked, and the annual recertification is scheduled.
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.