The most important differentiator, and the most commonly obscured. Purpose-built A&G intake platforms embed CMS regulatory definitions — from 42 CFR 422/423 Subpart M and the CMS ODAG/CDAG protocol — directly into their classification logic. They distinguish appeals from provider disputes, grievances from inquiries, and expedited from standard based on regulatory criteria, not surface document language.

Generic document AI tools classify by document type patterns — identifying “complaint letters” or “appeal requests” based on language modeling, not regulatory law. In a CMS audit context, this distinction produces systematic classification errors that generate ODAG findings.

CMS timeliness is measured from the moment the plan received the request. A platform that captures receipt timestamps only when a case is created in the system — rather than when the document arrived — produces timeliness records that are systematically inaccurate. This creates ODAG timeliness findings regardless of how good the actual review process is.

Compliant platforms capture the receipt timestamp at document arrival across all intake channels: fax, mail, email, web portal, and EDI. The case creation timestamp and the receipt timestamp are recorded separately and both are visible in the audit log.

Expedited appeals and coverage determinations have 24-72 hour windows. Missing an expedited indicator because a document arrived in an ambiguous format, or because a fatigued staff member didn’t recognize the language, is one of the most direct paths to an ODAG timeliness finding. Purpose-built platforms detect expedited indicators automatically — from explicit expedited language, from clinical urgency signals, and from provider-submitted forms that trigger expedited processing under CMS rules.

The intake agent’s job isn’t just to classify the document — it’s to produce a complete case record that a reviewer can begin work on immediately. That means extracting the issue description, claim number, event date, member ID, respondent, issue type, AOR information, and case sub-category from the incoming document and auto-populating the case record. Reviewers who receive a shell case with only a classification label and have to re-read the source document for data are getting less than half the value of intake automation.

CMS program auditors will request case documentation including evidence of how cases were received, classified, and processed. A platform that produces case records but not classification audit logs — showing the criteria applied, the confidence level, and the document evidence used — is not defensible in a CMS audit context. The audit log must be available at the case level, not just in aggregate reporting.

Even more critically: the platform should support the production of a CMS-ready universe export that reflects accurate case types, receipt timestamps, and case counts — because universe accuracy is tested directly in ODAG and CDAG audits.

The intake agent creates the case and routes it — but a human reviewer makes the determination. The platform must structurally require human review before any determination affecting member benefits is issued. This isn’t a policy requirement layered on top of the AI — it should be the architectural design of the system. The reviewer should receive a complete, classified, enriched case with all extracted data visible, so their time is spent on clinical and regulatory judgment rather than data entry.

Platforms that allow AI agents to issue correspondence or close cases without a human reviewer in the chain are not compliant with CMS requirements for MA plans, regardless of how they are marketed.

CMS updates Parts C and D A&G guidance regularly. The November 2024 guidance update added grievances to the requirements for coverage determinations and appeals, clarified provider versus enrollee filing rights, and modified the standards for grievance notification. A platform whose classification logic is not updated in synchronization with CMS guidance changes will systematically misclassify cases under outdated criteria.

More importantly: the update process must be change-controlled — meaning the plan knows when a guidance change is implemented, can validate the new logic before it goes live, and has a documented record of when each regulatory update was incorporated.

Intake automation that operates as a standalone module produces classified cases that still require manual transfer to the plan’s case management system and universe tracking. The full value of intake automation is realized when the intake agent creates a case directly in the case management platform — with the universe record, timeliness clock, and SLA tracking all initiated simultaneously at receipt.

Plans that are preparing for CMS audits also need their intake data connected to their CMS Universe Scrubber, so that classification errors detected in the universe can be traced back to the intake record and corrected before submission. And Star Ratings appeal measures require accurate universe data that flows from intake through to IRE reporting — a connection that only works if intake, case management, and universe tracking are on the same data platform.