Help members use benefits they already have

Fertu enables food-as-medicine and community programs to tell each eligible member what their benefit is and how to use it, on the channel they prefer. Messages are personalized from the member’s own benefit and program fields, and reminders stop once your partner’s file shows the benefit used.

Example: a meal benefit notice by preference

Example. Harbor Nutrition notifies newly eligible Northwind Health Plan members about their meal benefit. Luis Ortega prefers text and his file lists Spanish, so he gets a short text in Spanish with his benefit details from Northwind’s file. Denise Carter prefers email, so she gets a branded email with the same details, and members with no digital contact get a letter. A reminder follows later, but only to members whose next file shows the benefit unused.

Example: Harbor Nutrition

Population

Newly eligible members

Segments

Prefers text

Prefers email

No digital contact

Steps

Text

Email

Letter: benefit notice, then a reminder only if the benefit is unused

Outcome

Benefit used, from the partner’s file

See this in the tour

See a meals program enroll members in their language and keep them informed.

Open the tour chapter →

Why benefits go unused, and how Fertu helps

Members don’t all want the same channel. In a 2024 survey, Medicare Advantage enrollees’ preferred channels for benefit notices were 73% email, 39% mail, 27% text and 6% phone, and nonwhite enrollees were more likely to prefer text or phone (Commonwealth Fund). Older Black and Hispanic patients said they wanted reminders on two or more channels (Annals of Family Medicine, 2026).

Members don’t know what they have

Personalize every message with fields from your own data, such as the member’s benefit and program details. Letters, postcards and self-mailers are personalized the same way, and each piece is checked for missing fields before it goes to print.

Eligibility arrives in separate lists

Fertu can combine a partner’s main roster with their supplementary files, such as consent or status lists, and holds the update if a supplementary file is missing or out of date.

Members prefer different channels

Tailor each step to sub-segments, with its own channel and message for each group, chosen by fields in your data such as a preferred channel.

A big rollout needs phasing

Your team can split an eligible population into cohorts in the Fertu Console to phase a rollout.

Reminders shouldn’t follow use

Members leave a campaign once your data shows they used the benefit, and follow-up steps skip members whose latest data shows they already responded.

The journeys behind benefit outreach

Benefit notice by channel preference

  1. One notice step has one version per channel (text, email, mail or call), each matched to a preference field in your data.

  2. Optional reminder steps follow.

  3. An exit rule ends the journey once the data shows the benefit was used.

Event-driven notices

Send event-driven notices, such as an order shipped, from the same platform as your campaigns. Your systems upload a record when something happens, name the notice campaign, and the member gets a text or email within minutes. Label each campaign as marketing, member updates or transactional, and every message lands on the same member record.

Your team builds both in the Fertu Console, or Fertu’s team does at your request.

Providing Medicaid in-lieu-of services from a plan’s eligibility file? See in-lieu-of services.

Every channel, one member timeline

Every notice, letters included, lands on the member’s timeline next to their texts, emails and calls. Returned mail automatically stops further letters.

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.

The progress grid shows sent, failed, scheduled, converted and exited members for every cohort and step, so you can see who used the benefit and left the campaign.

Security and compliance

Label each campaign as marketing, member updates or transactional, so email unsubscribes from marketing stay separate from member updates. Opt-outs are checked before every campaign message, inside a dedicated environment built for HIPAA. Security and compliance

For your technical team

Roster and eligibility files are joined as they load, and an upload from your systems can name the campaign it starts. Partner files arrive by SFTP or a secure upload endpoint, and outreach activity comes out as CSV. Integrations · How we work

Frequently asked questions

Can each member get the notice on their preferred channel?

Yes. Each step can have one version per channel, matched to a preference field in your data.

Can we send operational notices too, like an order shipped?

Yes. Your systems can upload a record when something happens, and the notice goes out by text or email within minutes, from the same platform as your campaigns.

Do reminders stop once a member uses the benefit?

Yes. Exit rules end the campaign once your partner’s file shows the benefit used.

Can we send messages in Spanish?

Yes. Create templates in English or Spanish for texts, email, mail and calls, and send each member the version that matches the language in your data.

See your benefit outreach in Fertu