Anthem and BCBS Medicare for Multi-State Agencies: A State-by-State Build Strategy
The phrase “contract with the Blues” collapses something that isn’t one decision into something that sounds like one. The Blue Cross Blue Shield Association is a federation of 33 independent health-insurance companies serving every US state and territory; Anthem (now Elevance Health) holds the BCBS license in 14 of those states, while different licensees operate in others. For an agency principal building a multi-state Medicare book, that fragmentation is the most underestimated piece of contract architecture in the entire carrier stack.
The Blue Federation at a Glance
The federation problem in plain English
BCBSA, the federation that owns the Blue marks, licenses the brand to independent licensees on a state-by-state basis. Anthem (rebranded as Elevance Health) is the largest single licensee, holding rights in 14 states including California, New York, Connecticut, Indiana, Ohio, Kentucky, and Virginia. In the other 36 states the BCBS license is held by a different operator — Highmark in parts of Pennsylvania and West Virginia, BCBS of Florida (Florida Blue / GuideWell) in Florida, BCBS of Michigan in Michigan, Blue Shield of California in parallel with Anthem in California, and so on. Each of these is a separate insurance company with separate Medicare Advantage products, separate commission grids, separate certification requirements, and separate provider networks.
For a multi-state agency, this means the “Anthem/BCBS” line on your stack isn’t one contract. It’s as many contracts as you have states in your service territory. Treating it as one carrier is the most common operational mistake agencies make when expanding their Medicare footprint.
The most common Blue-federation mistake
An agency contracts with Anthem in Indiana, then assumes the contract covers Anthem’s “sister” in Florida. Florida Blue is a different company; the Anthem contract doesn’t apply. Calls routed to Florida-licensed agents under that assumption are unappointed sales — CMS marketing-rule violations and clean grounds for the carrier to refuse to book the policy.
A state-by-state build plan
For a multi-state agency, Blue carriers should be built into the stack one state at a time, prioritized by where the local Blue licensee dominates the Medicare market and where the agency already writes meaningful volume. The pattern that works:
The 5-step state-by-state Blue build
Anthem vs. the other Blues: how to think about the difference
Anthem (Elevance) is operationally the most centralized of the major Blue licensees. The contracting workflow, the broker portal, the commission-grid format, and the certification requirements look very similar across the 14 Anthem states. For an agency contracting with Anthem in Indiana and Anthem in California, the documents are recognizable to each other — the rates differ, but the structure is the same. That centralization is one of the practical reasons Anthem is often the easiest Blue to build into a multi-state stack first.
The other large Blue licensees — Florida Blue, Highmark, BCBS of Texas, BCBS of Michigan, BCBS of North Carolina — each have their own broker workflows, their own commission grids, and their own certification requirements. Adding any of them is a separate project, and the agency’s back-office team should plan for it as such. The ROI is genuine; in many states, the local Blue is the dominant Medicare Advantage carrier and the agency simply cannot serve those counties without that contract.
State-licensing enforcement: the only thing that keeps you compliant at scale
At one or two states, manual state-licensing checks at the agent level work. At five or ten, they don’t. The CMS-published Medicare Communications and Marketing Guidelines are explicit that agents may only sell plans they are licensed and appointed to sell, and the carrier-side audit trail back to the agency is direct. An unappointed sale on a Blue plan is a CMS violation, a carrier-side authorization risk, and potentially a refused enrollment that you don’t get paid on.
The right operational answer is for the agency’s call routing to enforce state licensing automatically. When an inbound call arrives, the system identifies the caller’s state, checks each available agent’s licensing in that state, checks each agent’s appointment with the relevant Blue carrier, and only routes the call to agents who pass all three checks. This is exactly the same enforcement layer that’s needed for multi-state CMS compliance in general; the Blue federation just makes it more obviously necessary.
Commission grids: where Blue economics differ from national carriers
Most Blue Medicare Advantage products pay at the CMS-published commission ceiling for the state in question, the same as UHC, Humana, and Aetna. The differences show up in the override architecture and the renewal payment timing. Anthem and the other Blues tend to run cleaner administrative pipelines than some smaller carriers, and renewal payments arrive on a predictable schedule. The override percentages an FMO can offer on Blue contracts vary more than they do on national carriers — some Blue licensees give meaningful agency-level overrides, others retain almost all of it at the FMO. Read each contract on its own.
For agencies running the five-factor exercise from the carrier-stack framework, the Blues typically score very high on county-level network depth in their home states and low elsewhere — the federation structure means there is no “elsewhere” in the same sense that there is for UHC.
How the Blues fit on a 4-6 carrier stack
For a single-state agency, the local Blue is often the anchor carrier and one of the national majors (UHC, Humana, or Aetna) sits as a complement. For a multi-state agency, the architecture is inverted — UHC’s AARP-branded line covers the national footprint (described in our UHC and AARP guide), and the local Blue gets layered into specific states where its in-state share warrants the extra contract overhead. Humana typically fills the remaining gaps.
Key Takeaways for Agency Operators
- The Blue brand is a federation, not a carrier. Anthem holds 14 states; 19+ separate licensees hold the rest.
- Build the stack one state at a time. A contract with Anthem in Indiana doesn’t cover Florida, Michigan, or Pennsylvania.
- Sequence by in-state share, not FMO convenience. Where the local Blue holds 30%+ of MA enrollment, the contract is non-negotiable.
- State licensing must be enforced automatically. Manual checks fail at five-state scale; the carrier audit trail is direct.
- Track each Blue licensee separately. One unified “BCBS” line in your reporting hides the variance that drives operational decisions.
The Blues, taken seriously as a federation, are one of the highest-leverage stack additions a multi-state agency can make. Treated as a single carrier, they are one of the most common compliance disasters. The difference is operational discipline at the state level — in the contracting process, in routing, and in reporting.
Enforce state licensing on every Blue call — automatically
AgentTech Dialer tracks every agent’s state licenses and carrier appointments. Inbound calls route only to agents licensed in the caller’s state and appointed with the local Blue. Multi-state Blue books stop being a compliance tightrope and start being a clean operational layer on top of your existing stack.
Try AgentTech Dialer NowReferences & Authoritative Sources
The information on this page is supported by the following official and authoritative sources.
- 1
- 2
- 3
- 4