PAN Lab example
Propel in-app SNAP benefits assistant
Read-only by design: a benefits assistant grounded on the record it never writes
Propel's app uses AI to help people learn why a SNAP food-benefit deposit did not arrive. It reads the state's record, never writing to it.
See more
Propel Inc., a private Brooklyn company, runs a free benefits app used by people on SNAP, the US food-benefit program. Its missed-deposit alert flags a benefit deposit that did not arrive, and its AI help tells the recipient why and what to do next. The tools read the state's deposit history but never write to it.
The app and the programs
SNAP stands for the Supplemental Nutrition Assistance Program. Benefits arrive as deposits into an Electronic Benefit Transfer (EBT) account.
More than five million people use Propel's app to check their balances for SNAP and two other public benefit programs, WIC and TANF. The app connects to state benefit portals with each user's permission.
The problem the tools target
Propel says about 200,000 of its monthly users have a benefit deposit interrupted each month. Most interruptions follow the periodic reports due about six months after applying, or the yearly recertification.
An interruption can end with benefits stopping and the person reapplying. This is program churn, and it is the failure Propel's AI tools target.
How the tools work
A detection algorithm reads the recipient's deposit history from the state benefit portal. It flags an expected deposit that did not arrive. The state verifies that history, so the signal is almost certainly right.
Two tools then help the recipient find out why, and what to do next. One is a multi-step self-diagnosis flow, whose code was written with AI and then edited by hand before launch. The other is an AI chat assistant. It answers from a curated state-by-state SNAP knowledge base, and it runs on another company's commercial customer-support platform.
When the chat detects that it cannot help, it hands the case to a named Propel staff member. That person contacts the user directly.
The 2025 pilots
In spring 2025, Propel ran two deliberately small pilots, each over one deposit cycle. The self-diagnosis flow served about 1,300 CalFresh recipients. CalFresh is California's SNAP. The chat helped about 1,000 SNAP recipients nationwide with missed deposits. Propel held the pilots to about that size so its team could monitor results and handle every escalation by hand.
Propel reports that 53 percent of eligible users offered the tools used them. It reports that randomized testing against a control group showed "modest but meaningful" improvements. They were in the days until the next deposit, and in the share of users restored in the same month. Propel did not publish the size of either effect.
The chat gave state-specific answers and recognized state-specific shorthand. It switched to Haitian Creole when a user began replying in it, which the team had not designed in advance. Users could rate conversations. Most did not, and among those who did, very few ratings were negative.
How far the tools have gone
As of mid-2026, no source documents a full rollout of the AI chat to the app's millions of users. The deployments the sources describe are the capped pilots and one pipeline built for the November 2025 federal shutdown.
That shutdown delayed SNAP payments to about 42 million recipients. Propel checked all fifty state SNAP agency websites every hour. A language model sorted real updates from formatting changes before people reviewed them.
Where the facts come from
Every outcome figure here comes from Propel itself. The case file found no independent evaluation, replication, or outside coverage of the pilots.
NPR independently reported the app's scale of about five million users. Propel says more than 25 percent of EBT cardholders nationwide use the app. As of July 2026, Apple's App Store listed about 574,000 ratings for it, averaging 4.9 out of 5.
What this case asks
Most cases in the Lab follow a mistake from an AI into a record, and back out into someone's decision. Here that loop is cut at the source, because the help tools never write to the deposit history. AI-written text is never saved into it and read back later as fact.
The risk moved somewhere quieter. It moved onto the staff who catch what the AI misses, a channel sized for a pilot. It also moved onto a gap: no one outside Propel checks any of it. No state agency, regulator, or independent auditor governs the tools.
What this network is drawn from
This network follows the pattern the Propel case file describes. It is not a reconstruction of the actual app. The people using the app are outside the network, which draws Propel's own support and escalation staff. It computes no restored benefits and no difference in who the tools help.
What the available tools can and cannot address
A failure pathway is a link between two parts of the network where a mistake made by one part can be passed on to the other. Closing a pathway means mistakes stop passing along it. The work along it goes on.
This case has a budget of 8 units. Each tool costs the same at every target level.
Explore (No Targets) sets no targets. Under Service Targets Only, the targets are met before any tool is used or pressure added. Any single tool on offer also keeps them met.
Under Service and Safety Targets and All Governance Targets, the targets can be met within the budget. Both levels ask you to close every failure pathway, among other targets. Before any tool is used, three failure pathways are open: Results and hand-offs to staff, Alert reads deposit history, and Staff read deposit history.
Escalate checks closes the first. Mark AI-written records closes the other two. Every way of meeting these targets uses both tools, which cost 4 units together at their standard settings. Within the budget, 14 different sets of tools meet the targets, or 35 counting the stronger settings.
More is not better here. Using every tool on offer, each at its strongest setting, costs 31 units, nearly four times the budget. It meets the targets at none of the three levels that set them, because the help tools then add too little to the work.
Open this example in PAN Lab v0.1 to apply pressures and levers and watch what the system does.
What this models
This example runs on the Propel-class read-only benefits assistant network: 6 components and 11 pathways between them. Every context in the Lab is a stylized model, never a reconstruction of any actual deployment, and each assumption behind it carries a provenance label.
Evidence base: 5 assumed · 2 published baseline. In the Lab, the shaded evidence band behind each headline readout draws its width from the least-established class below.
Show all 7 assumptions
- assumed
This network follows the pattern the Propel case file describes: an assistant that reads a state-verified record and never writes to it. It does not reconstruct the actual app.
- assumed
The people who use the app are the recipients it serves, and the network leaves them out. As the Lab does for other tools the public uses directly, it draws Propel's own support and escalation staff instead. It computes no restored benefits, and it does not show whether some recipients are harmed more than others.
- baseline
The network assumes the help tools never write to the state's deposit history. They read the state-verified history by design, and only the state agency can change it. That read-only boundary is the case's defining protection and its strongest control.
- baseline
The network draws the escalation practice as a team check among staff, not as a second read of each case. When the AI reaches a dead end, it hands the case to a named staff member. Propel held the pilots to about 1,000 users so staff could handle every escalation.
- assumed
The network includes outside oversight as a check this deployment did not have. No state agency, regulator, or independent auditor governs the tools. The only published evidence that they work is Propel's own. So every protective step on the network is internal and at Propel's discretion. Of the tools on offer, Peer sharing rules is the one that switches the outside check on. The network draws that audit as a check on staff, so the tool that governs staff checks switches it on.
- assumed
The network assumes the AI chat always sends data out to the platform it runs on, and marks that pathway as sensitive for privacy. The platform belongs to another company. The sources document no data-processing agreement with it. It is the one place the network draws app data leaving Propel's app.
- assumed
Every outcome figure behind this case comes from Propel, and Propel did not publish the size of its effects. So the network shows how mistakes could pass and in which direction, never how large any harm would be.
What this example does not show
Show all 3 limitations
- This example does not promise that any real deployment is safe. Its fairly safe start comes from how the network is drawn, not from any measurement of the real app.
- The people who use the app are outside this example. It computes no restored benefits, and it does not show whether some recipients are harmed more than others. Whether a deposit arrived, and the pilot effects Propel reported, are outside what a network like this can show.
- Every outcome figure in this case comes from Propel, which did not publish the size of its effects. The sources describe no independent evaluation. So this example shows how mistakes could pass and in which direction, never how large any effect is.
Sources and evidence
What this example rests on, claim by claim. Every entry resolves to the same ledger the Evidence Registry publishes.
In a spring-2025 randomized pilot inside a large consumer EBT app, the vendor reports that 53% of eligible SNAP recipients took up in-app AI help for missed deposits and that treated users were restored faster and more often in the same month than a control group, with every AI dead-end escalated to a named human; all outcome figures are vendor-published and the effect magnitudes were not disclosed.
empirical- Vendor Propel Inc. (Propel Insights), Using AI to help SNAP recipients diagnose and restore lost benefits (2025) https://www.propel.app/insights/using-ai-to-help-snap-recipients-diagnose-and-restore-lost-benefits/
- Vendor Guarino, Using AI to help SNAP recipients diagnose and restore lost benefits and reduce churn (Substack, 2025) https://daveguarino.substack.com/p/using-ai-to-help-snap-recipients-377
By the vendor's own account of the design, the assistant grounds on a state-verified deposit record it reads but does not write to, and steers recipients to act on the state system of record rather than acting for them.
empirical- Vendor Propel Inc. (Propel Insights), Using AI to help SNAP recipients diagnose and restore lost benefits (2025) https://www.propel.app/insights/using-ai-to-help-snap-recipients-diagnose-and-restore-lost-benefits/
Where this connects
Institutional pressures in this domain
- Workload surge — Demand outruns staffing; per-case attention shrinks and review becomes triage.
- Vendor opacity — The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
- Data & policy drift — The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
- Reviewer bottleneck — One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.
- Compliance over substance — Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.
All of them in context on the Benefits navigation & public-facing chat domain page.
Levers available here and the patterns behind them
- Mark AI-written records — Provenance labeling
- Escalate checks — State-feedback vigilance
- Keep prompts neutral — Framing and mirroring reduction
- Peer sharing rules — Peer-edge governance
- Gate record entries — Human-in-the-loop write gating
- Vet connections — Connection authorization
- Gate vendor updates — Vendor quality gate
- Store less data — Data minimization
- Review on schedule — Oversight cadence & retrospectives
Documented case histories
- Propel in-app SNAP benefits assistant
- Nava assistive benefits chatbot
- Caddy adviser copilot at Citizens Advice
- GOV.UK Chat
- Mass.gov Virtual Assistant
- Frida (NAV Norway)
- SSA 800-Number Conversational AI Assistant
- EDD Virtual Assistant
- Burokratt
- Singapore's chatbot fleet refresh: eighty scripted engines slated for retirement onto a shared LLM platform
- IRS collection chatbots: expanded and made permanent with no performance measures
- Albert France Services
- GetCalFresh: the nonprofit front door that carried most of California's online SNAP intake
- MyFriendBen benefits screener
- Benefits Data Trust wind-down