How an enrichment runs
One claim on request, or every claim that meets your rule, and the answer comes back as fields.
Claim status in the docs →- Step 1A 277 that says too little
- The 276/277 check comes back pending, or pending with a reason code, and your biller would normally phone the payer or open its portal to learn more.
- Step 2Ask for the richer status, or let a rule
- Enrich one claim on the spot, or write a rule that enriches every claim that has shown pending for 30 days straight, or pending with a given reason code.
- Step 3Daybook fetches it
- Daybook reaches the richer status through Availity, what Availity calls enhanced claim status, and for some payers through the payer's portal directly. Nothing is retyped.
- Step 4The answer lands
- What the payer holds on the claim comes back as fields, the reason behind the status, what the payer is waiting on and the next step, written onto the claim and sent to your system as a signed webhook.
For medical billers
A 277 often says a claim is pending and little else. That is the call your AR desk makes and the portal your biller opens. Daybook asks for the richer status instead and puts what the payer holds on the claim, so the next step is on the claim before anyone dials. Your billers keep every decision.
- The reason behind a pending status, what the payer is waiting on and the next step, as fields on the claim
- One claim enriched on request, or every claim your rule names, such as pending for 30 days straight or pending with a given reason code
- Reached through Availity, and for some payers through the payer's portal directly
- A claim that still needs a person goes to a payer call under your own rules
More for medical billers: the billers page and claim status automation for billing companies.
For dental billers
A dental 277 can say a claim is pending and leave out that the payer wants an attachment or a narrative. Where the payer holds the richer status, through Availity or in its portal, Daybook fetches it and writes what the payer is waiting on onto the claim, and your biller sends what is missing.
- What the payer is waiting on, an attachment, a narrative or a correction, read into plain words
- Enrichment by rule for the claims that sit pending, so a waiting claim is found before the remit
- The richer status fetched from Availity or from the payer's portal, with no retyping
- A payer call when neither answers, under your own rules
More for dental billers: the dental page and claim status for dental offices.
Starts from your knowledge base
Your billing company's own rules, appeal workflows, payer quirks and call scripts are what Daybook runs. You send the documents, Daybook imports them as payer guides, shows you what it produces, and you adjust it together on a call. Each solution runs on its own, so you start with one and add the next.
For enrichment that is how your billers chase a pending claim today, and what they do once the payer says why.
- Your rule for pending claims, by days or by reason code
- What your biller does with each reason the payer gives
- The payers your billers phone or sign in to for a pending claim today
Where it shows up
- The claim in your PM or EHR
- The reason, what the payer is waiting on and the next step, as fields
- A signed webhook
- The enriched fields, for your write-back to pick up
- The Daybook dashboard
- The enriched claims on the worklist, beside the 277 that said too little
Enrich from your own system
Start the check from your PM system, let a rule enrich the claims that sit pending, and hear back as a signed webhook when the richer status lands. The same operations are MCP tools for your own agents.
Read claim status in the docs →Frequently asked questions
What billing teams ask us about claim status enrichment, and our answers.
What does an enriched claim status add to the 277?
The 277 says whether a claim is pending, paid or denied. The richer status says why: the reason behind a pending claim, what the payer is waiting on and the next step. It is the answer your biller would get from a call or a portal, as fields on the claim.
Where does Daybook get the richer status?
Through Availity, what Availity calls enhanced claim status, which it shows in its portal and offers as an API, and for some payers through the payer's portal directly. Daybook reads it and writes it onto the claim.
Does every claim get enriched?
Only the claims you choose. Enrich one claim on request, or write a rule, such as every claim that has shown pending for 30 days straight, or pending with a given reason code, and Daybook enriches each claim that matches.
How is enrichment priced?
As an optional line, priced per enriched claim, on top of the 276/277 checks. No rates are published; the call covers them for your volume.
What happens when the richer status still does not answer?
The claim goes where your rules send it: to a payer call, to the worklist for your biller, or to denials and appeals when the payer has denied it. Daybook writes what it found and does not change the claim on its own.
Does this replace the 276/277 checks?
No. The 276/277 check stays the first ask for every unpaid claim with no portal login. Enrichment is the second ask, for the claims where the 277 was not enough.