Question 1

Every MCO we work with does enrollment differently. What gets configured per plan, and what stays ours?

Accepted Answer

One agent is built per MCO portal - your state's managed-care map decides the fleet size, not your headcount. Each build is configured around that plan's forms and document demands: how your roster's state Medicaid ID, licensure, locations, and specialties map in, which documents upload where, and how status is reported in the plan's own wording. Your roster stays the single input across every plan; the multiplication is what the agents absorb. The same setup handles revalidations, which rerun the whole gauntlet. Scope your state and MCO mix to size it.

Question 2

What systems and credentials does the agent use, and where do results arrive?

Accepted Answer

Each MCO's provider enrollment portal, accessed with credentials stored in an agent profile so nobody types a password at run time - provisioned with enrollment access only and cut off by rotating or disabling the profile. Inputs are your roster data and the plan's required documentation; outputs are captured confirmations, application identifiers, and scheduled status reports in the plan's wording, delivered as structured records. No integration with your practice-management system is required to begin. Least-privilege access and audit logging are detailed on the security page.

Question 3

What happens when roster data is missing or a plan comes back with questions?

Accepted Answer

Anything missing fails by name: the run stops and identifies the roster field rather than the agent inventing a Medicaid ID or license detail. Plan-side questions, document requests, and anything ambiguous about a provider's state enrollment status go to a person with the plan's exact request attached, so your team responds to a specific ask. Those are business exceptions - the run worked and surfaced a finding. A portal outage or failed sign-in is a technical failure reported distinctly, and a changed portal flow surfaces as a named blocker, not a wrong submission.

Question 4

How do we audit progress across four MCOs and multiple providers at once?

Accepted Answer

Per application: every submission captures the plan's confirmation and application identifiers, then the agent tracks it on schedule and reports each status change in the plan's own wording, giving each provider-MCO pair its own evidence trail from submission to answer. An MCO's rejection or document demand is a successful run with a business finding routed to your team, never conflated with a technical failure. Because runs are scheduled and logged, the application nobody has heard about in six weeks is visible in the record instead of silently stalled.

Question 5

Does this begin after state Medicaid enrollment, or can it coordinate both layers?

Accepted Answer

The MCO portals are the headline because they are where the volume multiplies - the state approving a provider is the starting gun, and every MCO between the provider and their patients runs its own gate. But the workflow class is the same, and state Medicaid portals are scoped the same way, so both layers can run under one program. The sequencing is respected either way: anything ambiguous about a provider's state enrollment status escalates to a person rather than the agent pushing an MCO application built on an unsettled state record.

Question 6

How are state, MCO, provider-type, and service-location requirements kept separate in a multi-state rollout?

Accepted Answer

By construction: each state adds its own MCO map, and each MCO is its own scoped build on the same workflow, carrying that plan's forms and document demands. Provider-type detail and service locations are submitted per plan exactly as your roster records them - the roster is one source, but every plan's submission is its own run with its own confirmation and identifiers, so a requirement unique to one plan in one state never leaks into another's application. Bring the full footprint to scoping, or have Asteroid run enrollment across it as a managed service.

Medicaid MCO Provider Enrollment

See it run on your systems.

State approval is the starting gun; this runs the MCO gauntlet

One state’s Medicaid can be four separate enrollments.

What runs today

Frequently asked questions