Launch and grow in-lieu-of services programs
Fertu enables organizations that provide Medicaid in-lieu-of services, such as medically tailored meals, to turn a health plan’s eligibility file into enrolled members. Each member is reached in English or Spanish, on the channel they prefer, and your team can download an outreach status report to share with the plan.
In-lieu-of services (ILOS) are services, such as medically tailored meals, that some Medicaid health plans offer in place of other covered care.

Example: an eligibility file becomes enrolled members
Example. Harbor Nutrition provides medically tailored meals to members of Northwind Health Plan’s Medicaid plan. Fertu collects Northwind’s eligibility file and checks it against the last one. Luis Ortega’s file lists Spanish, so his enrollment text and automated call are in Spanish, and pressing 1 on the call connects him to Harbor’s enrollment team. When Northwind’s next file shows him enrolled, his outreach turns to his meals: when his first order ships, Harbor’s system uploads it, and a delivery notice text goes out within minutes.
Example: Harbor Nutrition
Population
Eligibility file from Northwind Health Plan
Segments
English
Spanish (from the language in the file)
Steps
Text: enrollment invitation
Call: press 1 to reach enrollment
Outcome
Enrolled, from Northwind’s next file
See this in the tour
Follow one member through a meals program, from the eligibility file to a delivery notice.
From eligibility file to enrolled members
Every eligible member needs reaching
Fertu loads the plan’s files into your own dedicated data environment, maps each field you need, and checks every new file against the last one before your campaigns use it. Status and eligibility lists can be joined to the main roster, and the update is held if a supplementary file is missing or out of date.
Contact details go stale
Only about a third of surveyed Medicaid managed care plans had current contact information for most of their members (MedCity News, 2023). Fertu can standardize addresses and check them against USPS data as files load. Members who tell the phone menu they have the wrong number can be left out of future campaigns, and returned mail stops further letters.
Members speak different languages
Create templates in English or Spanish for texts, email, mail and calls, and send each member the version that matches the language in the plan’s file.
Members prefer different channels
Give each step its own channel and message for each group, chosen by a preference field in your data.
Members want to know when a delivery is coming
Send event-driven notices from the same platform as your campaigns. When an order ships, your systems upload the record and name the notice campaign, and the member gets a text or email within minutes. Label the campaign transactional or member updates, so email unsubscribes stay separate from marketing.
The plan wants to know who was reached
Download a per-message outreach status report from the Fertu Console as a CSV, keyed to the member IDs in the plan’s own file, and share it with the plan.
Members go quiet
Build an audience from a date in your data, such as a last delivery long past, and members who match enter a re-engagement campaign automatically.
The journeys behind an in-lieu-of services program
Enrollment from the eligibility file: new members join a daily cohort the day their data arrives, first contact goes out by text, call, email or letter, and the journey ends when the next file shows them enrolled.
Notices by channel preference: one notice step has one version per channel, matched to a preference field.
Delivery notices: an upload from your systems starts a text or email within minutes.
Outreach status for the plan: a CSV download from the Fertu Console, whenever the plan asks.
Re-engagement: members whose data shows inactivity enter a reactivation campaign, and leave it when the next file shows activity.
Your team builds each journey in the Fertu Console, or Fertu’s team does at your request.
Every channel, one member timeline
Each member’s texts, calls, email and letters, plus delivery notices, sit on one timeline. Every letter and postcard is tied to the member it went to and shows next to their other messages.
Built for plan-sponsored programs
We have experience with health plan–sponsored programs, where the plan supplies the eligible-member list and our customer runs the outreach on Fertu.
Campaign reports show which members met the conversion criteria your team set, such as enrollment in the plan’s next file, and at which step.
Security and compliance
A plan can share its member file with confidence. HIPAA is the baseline, not an add-on: every Fertu customer gets the same dedicated environment built for HIPAA, and built-in controls support your TCPA and CAN-SPAM programs, with opt-out checks before every campaign message. Security and compliance
For your technical team
The plan’s file arrives by scheduled SFTP pickup, supplementary lists are joined as they load, and your systems can upload delivery events as they happen. Outreach activity comes out as CSV. Integrations · How we work
Frequently asked questions
Can we reach members in Spanish?
Yes. Create templates in English or Spanish for texts, email, mail and calls, and each member gets the version that matches the language in the plan’s file.
How does the plan hear what happened?
Download a per-message outreach status CSV from the Fertu Console, keyed to the plan’s own member IDs, and share it with the plan.
Can members get delivery notices?
Yes. Your systems upload a record when an order ships, and the member gets a text or email within minutes.
What about members who stop engaging?
Define inactivity with a date in your data, and those members enter a re-engagement campaign automatically.
Can we start with one channel?
Yes. Start with the channels your program needs and add more as it grows, in the same environment.
