Carrier-neutral SOA workflow

Carrier-Neutral Scope of Appointment for Medicare Agents

Independent Medicare agents often start a marketing appointment before they know which plan the beneficiary will actually enroll in. The Scope of Appointment documents the product types the beneficiary agreed to discuss, not the first carrier portal the agent happened to open.

Diagram of one carrier-neutral SOA captured first, then routed to UHC, Humana, Aetna, Anthem, Wellcare, HealthSpring, or a no-sale record based on the appointment outcome.
Illustrative routing workflow only. Verify current carrier, FMO, and platform instructions before submitting an enrollment.

Capture the SOA in your own agent-controlled vault first. Then store, upload, attach, or produce the record based on the final carrier workflow, including no-sale appointments where no carrier enrollment system is involved.

Send by text or emailMobile-friendly signingPending and signed statusReplacement SOA workflowAgent-controlled vaultExportable records

Built for licensed Medicare agents using their approved scripts, disclosures, carrier procedures, state recording notices, and enrollment workflows.

Workflow problem

Starting the SOA inside the wrong carrier portal

Most major Medicare carriers and enrollment platforms offer an electronic SOA tool inside their own system. Those tools can work well when the sale stays with that carrier. The problem starts when the needs analysis points somewhere else.

An agent may open one carrier hub because that carrier is usually the answer. The beneficiary signs there. Then doctors, prescriptions, network, county plan design, LIS/Medicaid status, or benefits clearly point to a different carrier. Now the SOA sits inside the first carrier system while the enrollment is heading somewhere else.

A carrier-neutral SOA workflow avoids that mismatch. Capture the appointment scope in your own vault before the recommendation is final, then route the signed record according to the final enrollment path.

Definition

What carrier-neutral SOA actually means

A carrier-neutral SOA is a CMS-aligned Scope of Appointment captured independently of any single carrier enrollment platform. The form documents the product types the beneficiary agreed to discuss and stores the signed record in the agent's own vault.

It is not a universal SOA accepted by every carrier in every situation. It is not blanket permission to discuss product types outside the agreed scope. It is a cleaner capture point for the appointment record.

Current CMS regulations describe the SOA as a documented agreement about which product types will be discussed and require a separate SOA for additional health-related lines of business not identified before the appointment. Read 42 CFR 422.2264.

It is

A way to capture the SOA once for the appointment before the carrier decision is final.

It is

A way to keep the SOA under the agent account so it is portable across enrollment systems.

It is

A way to preserve the appointment record when no enrollment results from the conversation.

It is not

A claim that every carrier accepts every externally generated SOA in every workflow.

It is not

A workaround for replacement SOA rules when the product scope changes.

How it works

The capture-once, route-later workflow

Step 1

Capture before the recommendation

Create a new Scope of Appointment from your agent account before the final carrier recommendation is clear.

Step 2

Beneficiary signs from their device

Send the private link by text or email. The beneficiary reviews and signs from a phone, tablet, or computer.

Step 3

Discuss the product types listed

Use your approved scripts, disclosures, and needs analysis to compare plans across the carriers you represent.

Step 4

Determine the enrollment path

The beneficiary enrolls with a carrier, asks for more time, or decides not to enroll.

Step 5

Route the SOA to the right destination

Retain it, upload it, attach it, reference it, or pair it with a carrier-specific process when required.

Step 6

Retrieve later if needed

Keep the signed SOA with related call recordings, plan documents, notes, and supporting files.

Carrier delivery matrix

Illustrative carrier workflow planning matrix

Carrier-by-carrier handling varies. Some workflows expect the agent or agency to retain the SOA and produce it upon request. Others support or require upload with the application. This matrix is an illustrative planning summary, not carrier guidance.

Informed + Choice does not speak for UnitedHealthcare, Humana, Aetna, Anthem/Elevance, Wellcare/Centene, HealthSpring, HCSC, CMS, or any carrier or platform. Always verify the current SOA capture, upload, retention, and submission process with the carrier, FMO, or platform before relying on a specific path.

Carrier or platform Workflow context Carrier-neutral SOA path
Humana Enrollment Hub Humana workflows may require SOA submission with enrollment materials and long-term retention under the applicable broker process. Capture in Vault first, then follow current Humana submission rules for the enrollment packet.
UnitedHealthcare LEAN UHC workflows commonly distinguish SOAs completed in LEAN from SOAs collected outside LEAN and retained by the agent or agency. Capture in Vault, keep the agent-side copy, and produce or submit it according to current UHC instructions.
Aetna Think Agent / Producer World Aetna materials have described acceptable SOA methods including hard copy, telephonic recording, and electronic signature. Capture in Vault, then attach, upload, or include the exported SOA when the carrier workflow requires it.
Anthem / Elevance mProducer mProducer workflows have supported access to electronic SOAs, printed forms, and upload paths for completed SOAs. Capture in Vault, export the signed SOA, and upload through mProducer where the current workflow supports it.
Wellcare / Centene Ascend Ascend workflows have supported scanning, photographing, or uploading completed SOAs with enrollment applications. Capture in Vault, export the SOA file, and upload it to Ascend when required for that enrollment.
HealthSpring / HCSC Cigna Medicare/HealthSpring workflows have changed ownership and branding; current HealthSpring/HCSC instructions should be verified before use. Capture in Vault, retain the agent copy, and follow the current carrier or FMO workflow for submission or production.
HealthSherpa Medicare HealthSherpa Medicare materials have described upload actions when an SOA was collected outside the platform. Capture in Vault, export the SOA, and upload it into the supported contact or enrollment record when applicable.
ConnectureDRX / PlanCompare Connecture workflows have described completing, adding, uploading, and storing SOAs on the beneficiary profile. Capture in Vault and upload to the beneficiary profile when the enrollment runs through that platform.
SunFire SunFire workflows have included an Upload Scope path alongside email, text, and voice scope methods inside the platform. Capture in Vault and upload to the SunFire beneficiary record when that is the chosen enrollment path.
MedicareCENTER MedicareCENTER stores SOAs and has recommended agents keep their own downloaded records for long-term access. Capture in Vault for an independent copy; use MedicareCENTER tools alongside it when that platform is part of the sale.
No-sale appointment No carrier enrollment system is involved, but the appointment record still matters. Capture in Vault. The vault is the system of record for the appointment.

Why timing matters

Why before the carrier decision matters

CMS regulations describe the SOA as documenting the product types the beneficiary agreed to discuss, not the carrier the beneficiary has agreed to choose.

The CY2027 final rule removed the 48-hour waiting period between SOA completion and a personal marketing appointment, while keeping the requirement that the SOA be agreed upon and recorded before the appointment. Read the CY2027 final rule.

The practical effect is simple: the SOA captures appointment scope at a moment when carrier-specific decisions may not have been made. A carrier-neutral capture point keeps the record aligned with the appointment instead of locking it inside the first carrier system opened.

No-sale SOA problem

Carrier enrollment systems are built around enrollments.

A no-sale SOA is a routine outcome. The beneficiary may want time to think, involve a family member, stay on a plan that already fits, or decide not to enroll. The signed SOA still exists, and it still belongs in a searchable record system.

The vault treats no-sale appointments as normal records, not exceptions.

What changes

What this changes

The point in the workflow where the SOA is captured
The system that holds the long-term record
The portability of the record across enrollment platforms
The clarity of the workflow when the carrier recommendation shifts
How no-sale appointments are documented

What stays the same

What it does not change

The product types the agent is allowed to discuss
The requirement to obtain the SOA before the marketing appointment
The 12-month validity of the signed SOA under current regulation
The need for a new SOA when the beneficiary requests a different plan type
The retention period that applies to each record type
Carrier-specific submission rules for each enrollment
The agent's obligation to follow CMS rules, carrier procedures, state recording-consent laws, and approved workflows

Informed + Choice workflow

How Informed + Choice supports carrier-neutral SOA

Informed + Choice gives licensed Medicare agents the capture point, storage layer, and routing flexibility that a carrier-neutral SOA workflow needs.

Capture once

Create an electronic Scope of Appointment, send the private link by text or email, or use a recorded telephone SOA workflow when a phone workflow is the better fit.

web-based electronic SOA workflow

Store under your agent account

Completed SOAs sit next to call recordings, ACA consent records, eligibility review documentation, uploaded files, and supporting sales documents.

agent compliance vault

Route to the carrier when needed

Export the signed SOA from your vault and upload, attach, reference, or produce it according to the receiving carrier workflow.

compare SOA Vault to Google Drive

Update the scope when the conversation changes

Create a replacement SOA when the beneficiary asks to discuss a product type not listed on the original appointment record.

electronic SOA FAQ

Keep no-sale records

Store appointments that do not result in an enrollment in the same vault with notes, uploaded files, and any related call recording.

off-season storage for agent records

Start with SOA Vault at $9.99/month.

Add Business Line + Vault at $39.99/month when you also need automatic call recording.

Fits your stack

Where this fits beside your existing tools

A carrier-neutral SOA Vault is not a replacement for your CRM, quoting platform, FMO tools, or carrier enrollment systems. The vault sits beside them as the agent-controlled compliance record layer.

Stack layer Examples What the vault changes
Quoting and plan comparison CSG, Connecture, SunFire, MedicareCENTER Unchanged. Keep using them.
Carrier enrollment Humana eHub, UHC LEAN, Aetna Think Agent, Anthem mProducer, Wellcare Ascend Unchanged. Submit the enrollment in the carrier's system as required.
Agency management / CRM AgencyBloc, RadiusBob, AgentCRM, MedicareCENTER CRM Unchanged. Keep your contact and pipeline workflows.
Phone system Carrier calling tools, generic VoIP, traditional landline Replaced or supplemented by Business Line + Vault when recorded-line storage is the right fit.
Compliance record layer Email folders, Google Drive, scattered carrier portals, FMO archives Replaced by SOA Vault as the agent-controlled record system.

FAQ

Carrier-neutral SOA questions

What is a carrier-neutral Scope of Appointment? +

A carrier-neutral SOA is a Medicare Scope of Appointment captured independently of any single carrier enrollment platform. The form documents the product types the beneficiary agreed to discuss and is stored in the agent's own vault.

Is a carrier-neutral SOA accepted by every Medicare carrier? +

No. Carrier rules vary. Some carriers accept compliant SOA formats captured outside their platform; others require the SOA to be captured, uploaded, or paired with the carrier enrollment workflow. Always verify the current SOA submission process with the carrier or FMO.

Can I capture the SOA before I know which carrier the beneficiary will enroll in? +

Yes. CMS regulations describe the SOA as documenting the product types the beneficiary agreed to discuss. The SOA is required before the marketing appointment, not before the carrier recommendation.

Can I upload a Vault-generated SOA to a carrier portal? +

Often, but not universally. Some carrier and platform workflows support upload, attachment, or production-on-request paths for SOAs collected outside the platform. Verify the current workflow with the receiving carrier or broker support before submitting the enrollment.

What happens to the SOA if the beneficiary does not enroll? +

A no-sale appointment still has an appointment record. A carrier-neutral SOA workflow stores that signed SOA in the agent's vault with any related call recording, notes, and uploaded documents.

Do I still need a new SOA when the beneficiary asks to discuss a different plan type? +

Yes. The current regulation requires a separate Scope of Appointment for additional health-related lines of business that were not identified before the appointment. The vault makes it easier to create and store the replacement record.

How long do I have to keep the SOA? +

SOA retention instructions vary by carrier, plan, FMO, and agency process, and many broker materials use long retention periods such as 10 years. SOA Vault is designed for long-term SOA storage, retrieval, and export. Verify your current retention obligation with the carrier or FMO.

Does Informed + Choice work alongside my existing CRM, FMO, and enrollment tools? +

Yes. Informed + Choice is built to sit beside your existing stack as the compliance record layer. Keep using your quoting tools, CRMs, FMO platforms, carrier portals, and enrollment systems.

What about call recordings tied to the SOA? +

When you add a recorded business line, Medicare sales calls can be recorded and stored in the same vault as the related SOA. CY2027 creates a six-year framework for Medicare marketing and sales call recordings, while enrollment records remain subject to separate requirements.

Can I export my SOAs if my workflow changes? +

Yes. Records are designed to be exportable if you change agencies, FMOs, CRMs, phone systems, or enrollment workflows.

Does a carrier-neutral SOA workflow guarantee compliance? +

No software can guarantee compliance by itself. Informed + Choice provides capture, storage, retrieval, and export workflows. Agents remain responsible for using the scripts, disclosures, carrier procedures, state recording laws, and enrollment workflows that apply to their business.

For source context, see 42 CFR 422.2264 and the CY2027 final rule. Always follow current CMS rules, carrier guidance, state rules, and agency compliance procedures.

Related workflows

Related agent compliance workflows

Business Line + Vault

Dedicated recorded line with automatic call recording and secure vault storage.

Business Line + Vault

Agent Compliance Vault

The agent-controlled vault for SOAs, call recordings, ACA records, and supporting files.

Agent Compliance Vault

Capture before the carrier decision

Capture the SOA once. Route it to the right workflow.

Independent Medicare agents do not always know at the start of an appointment which carrier the beneficiary will choose. Capture the SOA in your agent-controlled vault, discuss the product types the beneficiary agreed to discuss, then route the record based on the receiving carrier workflow.

Built for licensed Medicare agents. Always verify current SOA submission rules with the carrier or FMO before relying on any specific path. Informed + Choice is not an insurance agency and does not sell insurance.

Start SOA Vault