RCM & Prior Auth AI
K

Kaylie

Kaylie automates dental insurance work for general practices, oral surgeons, billing teams and dental groups. It reads upcoming appointments from the practice schedule, checks each patient's benefits through payer portals, fills gaps from electronic eligibility feeds and turns the result into estimates by procedure code for the proposed treatment plan, showing waiting periods, frequency limits and plan maximums. Verified benefits write back into Open Dental, CareStack and Eaglesoft, and practices on Dentrix, Denticon, Curve, WinOMS or DSN get a formatted result for staff to enter.

The claims side tracks open claims and reads explanations of benefits line by line, showing what the insurer allowed, paid and denied and why. When settled claims for a payer and employer group consistently differ from the estimate, Kaylie learns a plan rule that fills future gaps, while any answer the payer itself gave takes precedence. Staff can open the source behind any finding, and a free EOB analyzer works without an account.

Kaylie reports 918,635 verifications across 207 insurers for more than 75 dental groups and 300 offices in 29 states. Measured against 18,768 settled claims over 90 days to September 22, 2026, 95.2% of paid procedure lines were paid at the verified percentage and 89% within $5 of the estimate. Louis Chan and Vere Whittome founded the company in 2025. Verification or claims each cost from $600 per office a month and both together from $999, as a flat fee rather than a share of collections, with a business associate agreement for every practice.

AI Health Index verifiedNovember 19, 2026
Compare Kaylie with other vendors
Founded
2025
Headquarters
—
Website
www.kaylie.ai
Categories
rcm-and-prior-auth
Indexed Products
Insurance Verification, Treatment Planner, Eligibility Engine, Claim Status, EOB Analyzer
Buyer Segments
Dental practices, Oral surgery practices, Dental service organizations, Dental billing and RCM teams
Assessment

Capability Axes

An AI Health Index grade measures what a buyer can verify from public sources on the date shown. It is not a rating of how good the product is. A vendor can build an excellent system and grade low on an axis because it publishes nothing an outsider can check. How grades read

AI Capability
BB on AI CentralityThe model is the engine of a core module. The platform carries other value, but this capability does not exist without it.
Vendor Published

Two learned functions carry the product. Document interpretation turns explanation of benefits files into structured payment and denial data line by line, and plan inference compares settled claims with earlier estimates and carries forward patterns for a payer and employer group to fill gaps in later verifications.

The rest runs on prescribed logic: portal retrieval, electronic eligibility checks, the precedence rules that decide which source wins, record writeback and notifications. A practice using only verification and writeback leans mostly on that automation, while the claims and learned plan rules are where AI changes what the estimate says.

BB on Autonomy and Oversight ModelThe oversight structure is described and one part is missing, commonly the threshold at which the system stops or what happens after it is wrong.
Vendor Published

The service checks the coming schedule on its own, retrieves eligibility and writes verified plan details back into supported practice software. It keeps the source of every payer result and leaves questions it cannot resolve for staff, and a rule learned from settled claims can fill an empty field but never overrides a value the payer portal reported.

Staff can trace a result, inspect a denial and work estimates flagged for review. No human approval is required before each writeback, and there is no central switch to suspend every learned plan rule at once if one starts producing bad estimates.

BB on Model and Technology TransparencyThe approach or the suppliers are named without the version and update discipline behind them. Naming a supplier is the entry to this band both here and on Model Supply Chain Disclosure, which ask different questions of the same disclosure: who receives the data, and what produces the output.
Vendor Published

The decision logic is partly documented. Kaylie explains which sources take precedence, separates what a claim paid from what the plan allows, and shows how an interpretation of a settled claim fills an empty plan field and flows into a later estimate. Explanations of benefits are broken down into individual procedures, payments and denial reasons, and accuracy is reported at the level of procedure lines.

The document and language model architectures are not named, their training data is not described, and extraction error rates are not broken out by document format or payer.

DD on Model Supply Chain DisclosureNothing establishes who else sits between a patient record and an answer.
Vendor Published

Data sources and destinations are named: insurance portals, electronic eligibility feeds and practice management systems, plus an optional Google or Microsoft mailbox connection. The privacy policy describes service providers for data storage and error logging without naming them, and the coverage page lists the 207 insurers the service has worked with.

The models that read explanation of benefits documents and help interpret plan rules are not identified. No model provider, version or hosting arrangement is given, so a practice cannot tell whether those models run with Kaylie or with an outside partner.

BB on Clinical and Operational EvidenceNamed deployments with dated outcome figures and enough method to test them, or published research short of independent validation.
Vendor Published

Kaylie measures its estimates against what insurers actually paid. Across 18,768 settled claims over the 90 days to September 22, 2026, 95.2% of 40,875 paid procedure lines were paid at the verified coverage percentage, 92.5% of 47,543 lines were correctly called covered or not covered, and 89% of lines were paid within $5 of the estimate. Scale behind that is 918,635 verifications across 207 insurers, and a September 2026 release added learning from settled claims.

The measurement is the company's own, pooled across customers, with no named practice and no independent check. It shows how estimates compare with adjudication, not what that does to denials or collections.

CC on AI Safety and PHI StewardshipGeneral assurances of privacy and security that do not answer the questions artificial intelligence raises: what is retained, what reaches a model, and what happens to it there.
Vendor Published

Patient and insurance information is handled under a business associate agreement, and optional practice mailbox data is used only for a stated limited purpose, with administrators able to revoke the connection and request removal of stored mailbox records. Documents uploaded to the public EOB analyzer are processed and not stored.

Lessons from settled claims can shape later estimates at other practices on the same employer plan. The policy does not fully explain how that learning across practices is stripped of identifiers, how long it is kept or whether a practice can opt out, nor how production patient data is governed with any model provider.

Regulatory and Compliance
BB on HIPAA and BAA PostureBusiness associate status is stated and supported by a substantive privacy document, with the agreement or its scope not fully published. For a vendor outside the United States, an equivalent regime documented to this depth grades here. A vendor whose product does not process protected health information grades here too when it says so plainly and explains the scope, with a service privacy document behind it: stating a position a buyer can rely on is the posture this axis grades, and the band above is closed to it because there is no agreement to publish.
Vendor Published

Kaylie says it handles protected health information as each dental practice's business associate and signs an agreement with every practice on every tier, and its homepage describes the service as HIPAA compliant. The privacy policy separates the application from website tracking and sets confidentiality terms for providers that handle connected mailbox data.

The full agreement is not posted, and nothing states that every provider touching protected health information is bound by equivalent terms. The free EOB analyzer, which anyone can use without an account, carries no agreement, though uploaded documents are not stored.

DD on Security Certifications and Trust CenterControls are asserted with nothing independent behind them, or nothing is published. Read the note before concluding anything: this is the grade most often corrected on a second pass, because assurance material frequently sits on a parent domain or inside an old announcement rather than on the product pages.
Vendor Published

The privacy policy describes scoped access for the optional practice mailbox, logging and administrator revocation, and the marketing site keeps visitor analytics separate from the patient application. Documents uploaded to the public EOB analyzer are processed securely and not stored, according to the company.

No independent audit or current certificate is named for the production service. There is no SOC 2 report, accredited ISO certificate or trust center identifying the assessed entity and system, and the business associate agreement is a contractual promise rather than evidence of external testing.

CC on FDA and Regulatory StatusNo device claim is made and the product is scoped accordingly. Most administrative and operational products sit here and are not penalized for it, because this axis grades the appropriateness of the positioning rather than possession of a clearance. A stated limit on use, such as research use only or a clause that the product gives no medical advice, beside marketing that sells the product for clinical decisions also sits here, with both quoted, because the buyer has to ask which one governs.
Vendor Published

The treatment planner estimates insurance and patient costs for procedure codes in a plan the practice has already prepared, and the claims service reports payer status and reads benefit statements. Nothing in it forms a dental diagnosis or recommends a procedure, and it is sold to the administrative and billing staff who manage insurance across offices.

No device clearance or regulatory classification is presented, and none would be expected for insurance administration. Suggested next steps in the claims workflow concern processing and denial follow up, and the clinical plan always comes from the dentist.

BB on AI Governance and Bias DisclosureA governance framework with named process behind it, such as certification to an artificial intelligence management standard, or material written for a customer own review committee to evaluate the product with. A framework covering the vendor whole portfolio counts when its scope reaches this product; what it cannot supply is the product specific evaluation the band above asks for. Published results within the one group where the performance of this product is most at risk also sit here: evaluation on the question this axis asks, short of the comparison across groups the band above requires. A medical device clearance or certification, and the quality system behind it, does not reach this band on its own; it is graded under regulatory status. A regulator reviewed plan governing how the model may change does reach it.
Vendor Published

Source rules are published. A direct payer response outranks every other source, inference from settled claims only fills gaps for a payer and employer group, and each finding links to its source. An estimate can be checked against the later explanation of benefits, and the company reports accuracy against settled claims across its whole customer base.

Those controls show what the software does with a discrepancy and leave an audit trail. Accuracy is not broken out by payer, practice type or patient group, and no independent review of the learned inference process has been published.

CC on AI Liability and RecourseMechanisms exist that let someone challenge an output, such as audit trails, source traceability or review before commit, with nothing standing behind the output and no route for the harmed party.
Vendor Published

A billing team can open the evidence behind a verification, compare an estimate with each line of the insurer's explanation of benefits and see the reason for a denial. The workflows show staff handling exceptions and checking a plan before relying on the estimate, and the published accuracy figures tell a practice how often to expect a miss: about 11% of lines paid more than $5 away from the estimate in the 90 day measurement.

No correction timetable or remedy for a wrong benefit estimate is published. There is no accuracy warranty, no compensation for a denied claim and no commitment to make a practice whole when the insurer pays a different amount.

Integration and Deployment
BB on EHR and Interoperability DepthNamed systems with read access or one directional writing, or standards support with named deployments behind it.
Vendor Published

The practice schedule is the input, and verified plan information goes back into Open Dental, CareStack and Eaglesoft, with dedicated pages for Open Dental, CareStack and the WinOMS oral surgery workflow. Dentrix, Denticon, Curve, WinOMS and DSN receive formatted output for staff entry where direct writeback is not available. The automation also draws on payer portals and electronic eligibility feeds.

The directions of exchange are clearly split between integrated writeback and copy and paste. No public case shows both reading and writing at a specific named practice on one of these systems.

DD on Deployment Model and Data ResidencyNothing published about where the system runs or where the data rests.
Vendor Published

Practices use a hosted web application, reached at a sign in address separate from the marketing site, connected to their scheduling system and to US payer portals, with customers in 29 states. Website analytics are kept apart from the patient application, and the privacy policy describes hosting and operational providers in general terms.

Where original claims, extracted data, processing logs and backups are stored is not stated, and there is no residency commitment, choice of region, customer owned cloud deployment or onsite version. A practice can control some connection permissions, such as the optional mailbox link, separately from the vendor's hosting.

Commercial
BB on Commercial TransparencyA price or a pricing basis is published without full tiers, so a buyer can size the cost before making contact.
Vendor Published

Insurance verification and treatment estimates start at $600 per office a month for an office with two or three providers and five or six active chairs, claim tracking and EOB analysis cost $600 per office a month, and the bundle starts at $999. Pricing is a flat fee, not a percentage of collections, and the company compares itself directly with outsourced billing services.

Larger offices can cost more, though the step up is not published. Writeback is included with verification, a free EOB analyzer needs no account, and new practices go through a demo and onboarding without a published installation fee.

BB on Setting and Specialty CoverageCoverage is named with validation behind part of it.
Vendor Published

General dentistry, oral surgery, multisite dental groups and dental revenue cycle teams are the users, with dedicated pages for billing teams, dental groups and WinOMS oral surgery practices. The workflows cover benefit checks, estimates by dental procedure code and line level review of explanations of benefits, and the company reports more than 75 dental groups and 300 offices in 29 states.

The pooled accuracy figures do not say which specialties or practice sizes they represent. Medical billing outside dentistry is not part of the offer, and bank reconciliation is listed as coming soon.

Alternatives

Alternatives to Kaylie

Other products that do the same kind of work as Kaylie, and what each one does.

DayDream runs dental billing as a service, pairing its own software with a remote team of billers led by a US based account manager.

Toothy AI automates dental insurance verification and runs insurance billing with a team of revenue cycle specialists.

dentalrobot automates dental insurance verification for DSOs and dental groups.

Needletail AI verifies dental insurance eligibility and benefits for group practices and DSOs and writes the results into the practice management system before the patient arrives.

Lassie is AI that posts insurance payments for dental practices.

InsideDesk sells DSOs and multi location dental groups a revenue cycle platform their central billing teams run. InsideAssist syncs open claims from the practice system and payer portals each day, retrieves EOBs and surfaces the next action on each claim.

Commercial

Pricing

Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.

Entry Price Pricing Basis BAA Tier Implementation Source
From $600 per office per month
$600 baseline
Verification and treatment planning start at $600 per office monthly. Claims and benefits statement analysis are $600 per office monthly. Both together start at $999 per office monthly, as a flat fee rather than a percentage of collections. Kaylie says it signs a business associate agreement with every practice. The public offer does not list a separate agreement fee. Writeback into Open Dental, CareStack or Eaglesoft is included with verification. No separate implementation charge is published. Larger offices can pay more. Vendor Published

The entry verification rate is for an office with two or three providers and five or six active chairs. The public benefits statement analyzer provides a limited preview without an account.