Your provider inbox, answered.
AI agents that read, verify and answer provider emails about claims — inside your mailboxes, from your own claims data, with your team in charge of every category that goes live.
of a typical provider inbox is routine claim-status traffic the assistant answers or filters at level one.
coverage, English and Spanish, inside the 30-day response standard.
amounts, dates or statuses composed by AI. Every figure comes from your claims system.
to switch any category back to draft mode — by configuration, no software change.
Reads. Verifies. Answers. Escalates what it shouldn't answer.
The assistant sits between your professional mailboxes and your claims database. It classifies every provider email, authenticates the sender, finds the claim and assembles the reply from templates your team approved. Doubt goes to a person.
Thread-aware reading
Long email chains, forwarded threads, mixed questions: the classifier assigns every message to one of fifteen-plus inquiry categories and extracts the identifiers it needs — claim, member, dates of service, provider.
Provider authentication
A claim number alone is never enough. The sender proves identity with name plus TIN or NPI before anything is disclosed; more than one matching provider means an automatic escalation.
The claim, found
A read-only view of your claims data, adjustment-chain aware, with thirteen accepted identifier combinations — so the reply is about the right claim in the right state.
Policy-constrained replies
Bilingual templates filled from your data, worded to your guidelines. The model decides which template; it never composes an amount, a date or a status.
Five sequential gates
Unknown category, missing keys, ambiguous provider, anomalous claim, unconfigured question — each stops the automatic path and routes the thread to your reviewers with the claim already attached.
Closed-loop optimisation
Every edit your team makes to a draft is measured. Templates, rules and categories are tuned on that signal — with a monthly accuracy report, not a "set-and-forget" deployment.
Categories go live one at a time, approved in writing by your claims team. Everything else keeps reaching your reviewers as a prepared draft.
Nothing goes out without your say-so.
Automation is a per-category switch your team controls. The system is designed so that the failure mode is always a human reading a draft — never an invented answer.
The provider proves identity
Name plus TIN or NPI, checked against your provider records before any claim detail is shared.
Doubt goes to a human
Anything unknown, ambiguous or anomalous is escalated with the thread, the claim and the reason — never guessed.
Assembled from your data
The reply is filled from the claims system into a template your team approved, in the provider's language.
Your team stays in charge
Automatic sending is switched on per category, in writing, and switched off in minutes if it ever needs to be.
Your stack stays in place.
No new portal for providers, no new system for your examiners. The assistant works in the mailboxes and folders your team already uses, on infrastructure you control.
Your data never leaves your tenant — and we do not train on it.
- Mailboxes. Microsoft 365 via Graph with certificate authentication scoped to one mailbox, or Google Workspace. Drafts appear in Outlook or Gmail; routing folders and an exception mailbox keep the flow visible.
- Claims data. A read-only view of your adjudication system, refreshed on your schedule — Azure SQL, SQL Server, Postgres or a flat extract.
- Attachments and portals. Encrypted mail, secure portals and scanned documents read by a dedicated retrieval layer, so the correspondence that arrives sideways is handled too.
- PHI separation by design. A two-account boundary keeps HIPAA and GDPR workloads apart; protected information is removed before any model call and re-identified only inside your KMS.
- The record. An append-only audit trail per thread — every email, draft, edit and send — documented for your HITRUST or ISO programme. BAAs and NDAs as standard.
- AWS, inside your tenant. Deployed with your IAM, in your region, under your CISO's gating. Amazon Bedrock models where you allow them; nothing leaves the boundary you set.
Draft-first. Then category by category.
The path from a signed order to automatic replies is the same every time, and every step is reversible.
Wired in, drafts only
Mailbox and claims connections established inside your security review. Every provider email gets a prepared draft; your team sends, edits or rejects. Nothing leaves without a person.
Tested by the people who own the work
User-acceptance cases written and run by your claims team. Misses become new categories or new gates. Sign-off happens per category, in writing.
Watched, measured, maintained
Monitoring and incident response within one business day, a monthly accuracy report, templates and rules kept current as payer, CMS and state requirements change. Supported by the people who built it.
The same machine, a wider aperture.
Once the assistant reads, authenticates and retrieves reliably, the inbox becomes the front door to your claims operation — and each next step reuses what your team has already validated.
Your full category list
Missing information, records requests, refund and recoupment correspondence, appeals — added one at a time, drafts first.
Claims pre-worked for examiners
The assistant prepares the file: payment-integrity checks, duplicate and coding flags, risk-adjustment gaps — so your examiners decide with the evidence already gathered.
Prior authorization readiness
The same policy-to-rules engine that keeps replies consistent turns coverage policies into machine-readable criteria for CMS-0057-F timelines.
Bring us your inbox.
Share a week of anonymised provider correspondence and we will show you, category by category, what the assistant would have answered, what it would have escalated, and why. No new system to install first.