Your insurance card
🪪Card — a side
front or back — read as-is
🔄Card — other side
front or back — read as-is
starting…
🔒 read entirely in your browser — images never leave this device (no upload, no AI). Drop, paste, or click each side.
Read from your card
tap a phone number to set the call target
raw OCR text (what the reader saw)
From the card · filled by the scan, or type them
type it as printed — the IVR uses the numeric portion only and ignores the letter prefix
optional for this line — BCBS NC authenticates on DOB + ZIP + member ID (it doesn't spell the name)
Not on the card — you add these · required to authenticate
the line authenticates on it (e.g. 01/02/1980)
the ZIP on your account / home address
a valid provider NPI authenticates the provider-inquiry call so it will read member-specific benefits (deductible, copays, out-of-pocket). Leave blank to run unauthenticated.
Nothing here is stored. Fields are kept in memory for the call, then discarded — no localStorage, no server copy, no transcript of these values.
1 · dial
Dial payer
2 · menu
IVR nav
3 · enter
Enter member data
4 · capture
Capture readback
5 · done
Verified
🩺
Ready to verify
scan the card, enter DOB + ZIP (+ NPI for full detail), then verify — the payer's line reads the benefits back
Live call
Captured benefits
Eligibility & benefit structure · read back on the automated line
Coverage status—
Plan / product—
Effective date—
Group number—
Deductible (individual)—
Out-of-pocket max—
Office visit copay—
Specialist copay—
Emergency copay—
Coinsurance—
Amounts met to date · gated behind provider authentication (PIN)
Deductible met—
Out-of-pocket met—
values will fill live from the IVR's readback as the call runs — captured by our self-hosted transcription, matched to fields without passing through a third-party AI. The automated line reads eligibility & benefit structure without a provider PIN; deductible/out-of-pocket met-to-date amounts require provider authentication.
Now: the card-capture step is live — scan the front and back of your card and the fields fill client-side (no upload, no AI). Next, once the data is accurate:
- keypad injection of member ID / DOB from the form (the proven 0zsip data-entry workflow — out-of-band DTMF fired only into a quiet line, with read-back verification)
- menu navigation — a deterministic map, or an LLM that sees only the IVR's menu text (never your member data)
- live readback capture into the benefits card, with a per-field confidence check
- rehearsal mode against our in-house mock-insurance IVR (no real payer, no real data)