CClaimer

The AI agent that disputes your medical bills.

Keep policies, bills, payments, authorizations, disputes, calls, deadlines, and outcomes in one place. Built for families.

Start with email

Why we are building it

Families should not need to become insurance experts at the hospital desk.

This started with a simple, familiar problem: a family has medical insurance, but deductibles, EOBs, bills, and hospital payment requests are hard to understand in the moment. When someone asks for money, it is not always clear whether the family really owes it, whether the deductible was already met, or who to call.

Claimer is meant to keep the evidence in one place, explain the current situation, and handle the repetitive dispute work: finding the right number, navigating phone menus, asking for itemized bills or claim status, and showing whether the call actually achieved the goal.

How it works

From confusing bill to tracked dispute

1

Upload the documents

Add insurance policies, EOBs, medical bills, receipts, and provider forms from your phone or computer.

2

Understand what changed

Claimer organizes policy terms, deductibles, payments, claims, and bill status by family member and coverage period.

3

Authorize the agent

Sign an in-app authorization before any call that discusses billing, claims, appeals, or financial assistance.

4

Track the dispute

The voice agent calls the right department, navigates IVRs, records the transcript, and reports whether the outcome was achieved.

Product features

Everything tied to the claim record

Policy and plan version history

Deductible and payment ledger

Bill, claim, EOB, and receipt uploads

Phone number extraction from bills

Authorization and provider form workflows

AI call briefs, transcripts, outcomes, and follow-up tasks

Security and privacy

Built around PHI boundaries from the start

Email account access

Email/password accounts, password reset, private document storage, and household-scoped access controls.

Server-side PHI

The browser uses authenticated APIs. Service-role database access stays on the Fly voice/API service.

Restricted AI context

Call briefs include only allowed facts. Sensitive values like SSNs stay in an encrypted vault.

Authorization first

Calls that discuss PHI require an active signed authorization and track provider-specific forms.

Auditable outcomes

Transcripts, IVR actions, reference numbers, deadlines, and follow-up tasks are kept with the case.

Production compliance gate

Before real PHI goes live, BAAs are required across infrastructure, phone, AI, and delivery vendors.