Pick the denial code, paste the payer's denial reason, add two sentences of context — get back a payer-ready appeal letter with the arguments that work for that specific CARC, plus the enclosure checklist. Review, merge your data privately, send.
Fill in the denial facts — use placeholders, never real patient data (the letter keeps [PATIENT NAME]-style fields so you can merge real details privately). A payer-ready draft with an enclosure checklist comes back in ~20 seconds.
Your appeal letter draft will appear here.
Straight off the ERA/EOB — the payer's own words drive the rebuttal.
Two sentences about the service. Real identifiers stay in your system — the letter uses [BRACKETED FIELDS].
Check the draft against the chart, fill the placeholders privately, attach the enclosures, submit.
Yes — leave your work email once to unlock, then draft letters within fair-use limits. We're building the denial-management toolkit for small billing teams; email updates are the whole price.
No — and please don't. The tool is designed around placeholders: the letter comes back with [PATIENT NAME], [CLAIM NUMBER], [DATE OF SERVICE] fields that you merge privately in your own system. Inputs are processed transiently and never stored.
Payers accept letters on their merits: correct facts, the right policy citations and the right enclosures. The draft gives you the structure and arguments for the specific CARC; you review, complete the placeholders and attach the documents — exactly as with a letter you wrote from scratch.
All the CARCs in our denial codes list — CO 16, CO 45, CO 50, CO 97, CO 197, PR 204 and 45+ more. Each code gets arguments specific to its denial reason, not a generic template.