Enroll members without marketplace busywork.

Three controls stack: every field is verified against the source data before submission; runs check the portal for an existing application or payment before creating one, so a re-run can't double-enroll or double-pay; and you can gate any submission behind human approval: the agent fills, pauses, and waits for a Slack sign-off before it files. Portal-specific evals run continuously against mock copies of carrier UIs to catch drift before it reaches production.

It stops and routes. Missing applicant information halts the run with the specific gaps named; anything requiring licensed judgment (plan recommendations, attestations, SEP documentation calls) is out of the agent's authority by design and lands with your licensed staff carrying full context. An application correctly held for review is a completed run with a business exception, distinct from a portal failure, so your queue separates 'needs a human' from 'needs a retry.'

Agents read each enrollment screen as it renders, so carrier form changes are absorbed run to run rather than breaking a recorded path. The mock-UI evals catch behavioral drift early, and a change the workflow genuinely can't traverse stops the run with the step identified. During open enrollment that surfacing matters more than anywhere, because a silent failure costs coverage effective dates. Fixing the workflow is Asteroid's job, not your ops team's.

Enrollment data carries PHI and payment information together, so the posture is strict: HIPAA-compliant, SOC 2 Type II infrastructure, a BAA, and zero data-retention agreements with sub-processors: no PHI trains any model. Portal credentials are your accounts under least-privilege scoping. Every submission, payment step, and human approval is timestamped in execution history. Payment details stay in your systems; the full access posture is on the security page.

Carriers and CRMs are added per deployment: scope the flow in the builder with a worked enrollment example, or have Asteroid run it managed. Because the agent drives the portal a broker or admin would use, a regional carrier with no integration program is as automatable as a national one. The catalogue reflects where customers started, not a coverage ceiling.