Case Study

Zchut-AI |
Rights and benefits
assistant

I designed and tested a prototype that turns an Israeli benefit letter into one plain-language next step, and says when the AI is unsure.

Role

Solo product designer

Scope

Mobile app and web prototype

Tested

4 moderated sessions · June 2026

Prototype

Product overview

Personalized Zchut AI home screen
01Home
Rights search and category discovery screen
02Rights search
Right details and eligibility screen
03Eligibility details
Benefits application tracking screen
04Application tracking
Context

The problem

Non-take-up

People can qualify for support and still never claim it. In three Israeli benefit programs, the gap was larger than half.

53%of those eligible for long-term income support never claim it
61%of eligible unemployed never file for unemployment benefit
57%of those eligible for rent assistance never receive it

National Insurance Institute research series, Prof. Daniel Gottlieb with the Hebrew University School of Social Work, published in Social Security, May 2021. Pre-COVID data.

Design persona 01 - Isaac, 72
"I just want to know what I'm entitled to without feeling like I need a law degree to use an app."
Design requirement

One decision per screen

Design persona 02 - Elena, 29
"I can build a bridge, but I can't decipher this one-page letter from the tax office."
Design requirement

Letter explanation before next steps

Design rule

The interface explains the document before asking the user to take action.

Structure

Interaction models

01

Guided flow

Known rules and deadlines

  1. Focused question
  2. Structured check
  3. Clear action
02

AI interpretation

Letters, voice, and open questions

  1. Natural input
  2. Interpretation
  3. Clarify or escalate
Response requirements

Every answer includes an official source, a confidence state, or an option to continue with an adviser.

Prototype

Core interactions

Isaac scenario

Voice input

The app confirms the transcript before the AI answers. Voice entry moved earlier after usability testing.

Voice assistant - mobile
Elena scenario

Document scanning

The scan separates routine information from deadlines and required action, without asking the user to retype the letter.

Document scanner and AI chat - mobile
Trust boundary

Adviser handoff

The system explains why it is escalating and passes the conversation to an adviser, so the user does not repeat the story.

AI chat with escalation - desktop
System

Confidence and escalation

01 - Input

Input

02 - Interpretation

Structured interpretation

Intent and entities Structured output
03 - Confidence gate

Confidence check

ConfidentAnswer and official source
PartialAnswer with verification step
EscalateNo answer, route to an adviser
04 - Outcome

Response

  • Act with a source
  • Verify before acting
  • Continue with a person

Guided flow

This requires maintaining a second interaction pattern.

Confidence states

This adds more interface states.

Adviser handoff

This depends on adviser tools and governance.

Tooling note

I used AI to scaffold prototype states and edge cases. I set the product rules, research questions, and validation boundary.

Research

Usability testing

Sessions4 moderated tests
Cohort2 seniors
Cohort2 immigrants
Method & dateWizard-of-Oz · June 2026
Participants

Simcha, 76 - former chemical engineer; Tami, 72 - former kindergarten teacher; Yevgeny, 58 - musician with a mobility disability; Genia, 54 - musician whose husband is disabled.

014 of 4 participants

Warning icon

"What does this '!' want from me? If there's nothing to submit, why is it there?" - Tami

I changedReserved "!" for required action and used a neutral state when nothing was needed.

before
Confidence action buttons - before
after
Confidence action buttons - after
022 of 2 immigrants

Disability in onboarding

"Ask me if I have a disability - that's the most important thing to me." - Yevgeny

I changedAdded disability as a first-class onboarding category instead of forcing a workaround.

before
Status category options - before
after
Status category options - after
034 of 4 participants

Source placement

"608 isn't a round number someone made up. It looks real." - Tami

I changedPut the official source inside the answer, not in a footnote.

before
Result card - before
after
Result card - after
04Secondary pattern

Search and eligibility labels

I sawSearch categories missed users' language, and condition lists did not communicate "all" versus "any."

I changedMoved voice entry earlier and labelled the eligibility logic explicitly.

before
Navigation card before usability changes
after
Navigation card after usability changes
Methodology note

Four qualitative sessions are not statistically representative. Wizard-of-Oz responses tested comprehension and trust, not model or legal accuracy.

Results and limitations

The usability tests informed four interface changes. Model accuracy, legal correctness, and governance were outside the scope of testing.

Limitations

Participant recruitment

The strongest gap surfaced by accident.

Icon testing

A short isolated test would have exposed it.

Baseline measurement

I can explain the changes, not quantify comprehension improvement.

Contact

guybsn@gmail.com