ACA health-insurance calls are not generic insurance calls with a different label.

The value of an ACA call depends on what the consumer is actually seeking, whether the timing fits an enrollment opportunity, which state the consumer is in, whether the receiving agent or organization can legally and operationally assist, how the caller reached the phone, what the caller was told, and what event ultimately makes the call billable or payable.

A buyer can receive a long call and still have a poor outcome if the consumer expected something else. A publisher can generate genuine health-coverage interest and still lose trust if the source, creative, traffic type, or enrollment context cannot be explained. An exchange can route the call correctly at the telephony layer and still create a bad result if buyer capacity, licensing, source approval, or settlement rules are weak.

That is why pay-per-call for ACA health insurance needs more discipline than a broad promise of “qualified calls.”

This guide explains the operating questions buyers and publishers should answer before ACA traffic starts, how consumer-initiated inbound calls differ from transfers, why enrollment timing and state eligibility matter, and how routing, qualification, compliance review, and financial reconciliation fit together.

This article is educational and operational. It is not legal advice. ACA marketing, telemarketing, insurance licensing, Marketplace enrollment, privacy, consent, and state-law requirements are fact-specific and can change. Buyers, publishers, agencies, and technology providers should work with qualified counsel and current program guidance before launching or changing a campaign.

Start by defining what “ACA call” means

“ACA call” is often used too loosely.

One buyer may mean a consumer asking for help enrolling in a Marketplace qualified health plan. Another may use the term for a broader under-65 health-insurance conversation. A third may accept calls involving multiple health-coverage options, while another may only want consumers who appear to have a valid Open Enrollment or Special Enrollment opportunity.

Those are different offers.

Before discussing volume, price, or payout, the campaign should define:

The product or coverage category the buyer handles.
Whether the buyer assists with Marketplace enrollment.
Whether the buyer handles only ACA-compliant major-medical plans or a broader under-65 health category.
The states the buyer serves.
The licenses, appointments, registrations, and training required for the receiving agent or organization.
Whether the buyer accepts consumer-initiated inbound calls, transfers, or both.
Whether Open Enrollment and Special Enrollment traffic use different rules.
What the publisher is permitted to say in advertising and pre-call interactions.
What makes a call routed, connected, qualified, billable, payable, or converted.
What records must be available if a call or enrollment is reviewed later.

A campaign cannot be controlled if “ACA” is the only definition everyone shares.

The buyer, publisher, and routing operator need the same picture of the consumer journey. Otherwise, one party may think it is buying Marketplace enrollment opportunities while another is sending general health-insurance interest.

Enrollment timing changes the call opportunity

ACA demand is seasonal, but it is not limited to one annual window.

HealthCare.gov currently lists the federal Marketplace Open Enrollment period as beginning November 1 and ending January 15. It also notes that consumers may be able to enroll outside that window if they qualify for a Special Enrollment Period, while Medicaid and CHIP applications can occur throughout the year. See the current HealthCare.gov enrollment dates and deadlines before relying on a campaign calendar.

That matters operationally because a call during Open Enrollment and a call during the rest of the year may need different handling.

Open Enrollment can create burst demand

During Open Enrollment, buyers may see:

More consumers actively shopping or renewing.
More publisher competition.
Higher call volume in compressed time windows.
Longer hold times if staffing does not match demand.
More urgency near effective-date deadlines.
More pressure to expand caps before a source has been adequately tested.
More risk that publishers blend weak traffic into a strong seasonal campaign.

A buyer that says, “We can take 500 ACA calls per day,” still needs to define hours, state coverage, agent availability, concurrent capacity, and what happens during a burst.

A daily cap does not prove that a team can handle 30 calls arriving in five minutes. The relationship between schedules, accumulated caps, and simultaneous load is covered in how caps, schedules, and concurrency shape call flow.

Special Enrollment Period traffic needs its own discipline

Outside Open Enrollment, Marketplace enrollment generally depends on a qualifying Special Enrollment Period. HealthCare.gov lists examples such as marriage, the birth or adoption of a child, certain moves, and loss of qualifying health coverage. Some events require documentation, and the details vary by event. The current HealthCare.gov Special Enrollment Period guidance should be treated as a starting point, not a substitute for case-specific eligibility review.

This creates a practical distinction:

A consumer can be interested in health coverage.
A consumer can need health coverage.
A consumer can be eligible to enroll in a Marketplace plan at that moment.

Those are not automatically the same thing.

Publishers should not make eligibility determinations they are not equipped or authorized to make. Buyers should not assume every off-season caller has a valid enrollment path. The call flow should support careful verification by the properly licensed and registered party rather than turning a marketing qualification into a legal conclusion.

Consumer-initiated inbound calls and transfers are different products

ACA campaigns commonly use at least two traffic types:

Consumer-initiated inbound calls, where the consumer sees or hears marketing and chooses to place the call.
Transfers, where an upstream publisher, call center, or agent speaks with the consumer before connecting the consumer to the buyer.

Both can work. They should not be blended casually.

Consumer-initiated inbound ACA calls

A consumer-initiated inbound call may carry strong intent because the person took the direct action to call. But “inbound” does not prove the marketing was clear or the consumer understood the destination.

The buyer still needs to know:

What did the advertisement say?
What did the landing page present?
Was the call-to-action about health insurance, a government benefit, a subsidy, a cash card, or something broader?
Was the advertiser identity clear?
Did the consumer reasonably expect to speak with a licensed insurance representative?
Was the phone number attached to a specific source and creative?
Can the source be isolated if complaints or poor performance appear?

A consumer can initiate the call and still be confused.

ACA transfers

A transfer adds another operating layer.

The upstream party may ask screening questions, explain the handoff, or confirm basic interest. That can make the call more relevant. It also creates additional questions:

How did the upstream party first contact or acquire the consumer?
What script was used?
What did the consumer agree to?
Did the consumer understand that another organization or agent would receive the call?
What information was collected before transfer?
Was any sensitive information passed?
Was the handoff warm, cold, blind, or recorded?
Does the buyer accept that exact transfer process?
Were the upstream representatives permitted to make the statements they made?

The buyer should approve consumer-initiated inbound and transfer traffic separately when the call paths differ. Source labels, qualification rules, reporting, and disputes should preserve that difference.

For a broader comparison, see consumer-initiated inbound calls vs transfers.

Caller intent begins before the phone rings

A call is not high intent merely because someone stayed on the line.

ACA caller intent is shaped by the marketing promise.

A useful call path aligns four things:

The message: What the consumer sees or hears.
The action: What the consumer is asked to do.
The expectation: Who the consumer believes will answer.
The destination: What the buyer can actually provide.

Problems begin when those pieces do not match.

A person attracted by a vague promise of “free benefits,” a spending card, cash, or government money may not be seeking an insurance conversation. A person looking for Medicaid may not be a fit for a buyer focused on Marketplace plans. A person seeking Medicare coverage should not be treated as an ACA caller merely because both are health-insurance categories.

The buyer should review the marketing context, not just the resulting duration.

Questions worth asking include:

Is health insurance named clearly?
Is the consumer told that licensed insurance assistance may be involved?
Is the advertiser or publisher identity presented appropriately?
Are claims about premiums, subsidies, savings, benefits, or eligibility accurate and supportable?
Does the call-to-action create the same expectation as the buyer’s opening?
Are Medicare, Medicaid, ACA Marketplace, and other under-65 products kept distinct?
Are geographic limitations clear where needed?
Can the creative be tied to a source and time period?
Is there a process for withdrawing a creative when rules or buyer requirements change?

The strongest source is not the one with the most persuasive headline. It is the one that can generate real consumer intent without creating a false expectation.

Licensed-state routing is a core eligibility rule

Health-insurance call routing cannot rely only on buyer appetite.

The destination must fit the consumer’s state and the receiving party’s ability to assist. Current federal Marketplace rules require agents and brokers working through a Federally-facilitated Exchange to register in advance, receive applicable training, comply with privacy and security standards, and comply with state law. Web-broker arrangements must verify that the agent or broker is licensed in the state where the consumer is selecting coverage. See 45 CFR 155.220 and the current CMS resources for Marketplace agents and brokers.

A routing rule should therefore answer more than, “Does this buyer want ACA calls?”

It may need to answer:

Is the buyer active for this campaign?
Is the target open?
Is the source approved for this target?
Does the consumer’s state match the target’s accepted geography?
Is the receiving agent or organization properly licensed and eligible for that state and workflow?
Is the relevant Marketplace registration and training current where required?
Does the buyer have budget and capacity?
Is the traffic type accepted?
Has a source, target, or campaign cap been reached?
Is the call a duplicate under the agreed policy?
Is there another eligible destination if the first target cannot take the call?

The exact implementation will differ by buyer and operating model. The principle should not.

A call should not route merely because a destination number answers.

A pay-per-call operator should distinguish between consent or permission associated with marketing and the records required when an agent, broker, or web-broker assists with Marketplace enrollment.

Under current 45 CFR 155.220, an agent, broker, or web-broker assisting through a Federally-facilitated Exchange must obtain and document the consumer’s consent before assisting with or facilitating enrollment. The documentation must reflect the scope, purpose, and duration of the consent; the date; the consumer or authorized representative; the agent, broker, web-broker, or agency receiving consent; and a process for rescission. The rule requires those records to be maintained for at least ten years. It also requires protection of personally identifiable information and specific consumer authorization around Special Enrollment Period submissions.

That does not mean every publisher should collect a Marketplace enrollment consent record.

It means each party should understand where its role begins and ends.

A publisher may be responsible for documenting its advertising path, call initiation, source, creative, transfer process, or other marketing records. The licensed enrollment party may be responsible for the Marketplace-specific assistance and consent records. The exchange or routing operator may need enough metadata and auditability to explain which source and target handled the call without unnecessarily exposing consumer information.

Do not collapse all of those records into a single checkbox called “consent.”

The record should match the action being authorized.

What an ACA buyer should define before launch

A buyer should be operationally ready before asking for more supply.

1. Accepted states and agent eligibility

The buyer should maintain a current, usable map of:

States accepted.
Agents or teams eligible by state.
Any product or carrier limitations.
Marketplace registration or training requirements.
State-specific restrictions.
How quickly changes are reflected in routing.
What happens when an agent’s eligibility changes during a campaign.

A spreadsheet that is updated occasionally may not be enough for live routing. The routing path needs an authoritative source of truth.

2. Hours, caps, and concurrency

ACA volume can be seasonal and bursty.

The buyer should define:

Operating hours and timezone.
Holiday or special enrollment hours.
Daily and hourly caps.
Concurrent-call limits.
Whether ringing calls consume capacity.
Whether different teams have different limits.
What event consumes a cap.
How quickly capacity is released after no-answer, disconnect, or transfer failure.
Whether overflow is allowed.

A target can be under its daily cap and still be full right now.

3. Call opening and handoff

The first few seconds often determine whether the consumer trusts the call.

The buyer should know:

How the agent identifies the organization.
How the agent confirms the consumer’s purpose.
How transferred callers are introduced.
What the agent does when the caller expected a different benefit or product.
How the agent handles consumers who may need Medicaid, Medicare, employer coverage, or another path.
When the agent ends the conversation rather than forcing a fit.

A clean call opening should resolve confusion quickly rather than exploiting it.

4. Qualification and settlement definitions

“Qualified ACA call” is too vague for billing.

The agreement should specify:

Whether qualification is duration-based, event-based, conversion-based, or hybrid.
Whether duration uses connected time or total call time.
Whether IVR, queue, hold, or transfer time counts.
Which geographies qualify.
Whether repeat callers are duplicates.
Whether a call can be qualified but not billable.
Whether a conversion can occur later.
How conversion data is returned.
How disputes and corrections affect buyer charges and publisher payouts.

The difference among routed, connected, qualified, billable, payable, and converted is explained in the difference between a routed call, a qualified call, and a billable call.

5. Complaint and escalation handling

The buyer should define how it will handle:

Caller confusion.
Allegations of misleading advertising.
Unauthorized enrollment concerns.
Wrong-state routing.
Agent conduct issues.
Sensitive-data exposure.
Repeat or duplicate calls.
Requests to identify the source.
Requests to stop a source immediately.
Regulatory or carrier inquiries.

A complaint process that starts with “Which publisher sent this?” is already too late if the operation cannot answer.

What an ACA publisher should prepare

A publisher should package ACA traffic for review before sending meaningful volume.

Useful materials may include:

A plain-language source description.
The traffic type: consumer-initiated inbound, transfer, or another approved flow.
Sample ads and creatives.
Landing pages and call-to-action language.
A map of owned-and-operated, partner, and sub-publisher traffic.
Source and sub-source labels.
Transfer scripts or handoff descriptions.
Call samples or recordings when legally appropriate.
Geographic controls.
Operating hours.
Expected volume range.
Known seasonality.
A description of how creatives are approved and retired.
A compliance attestation.
A process for responding to a buyer or operator review.
A process for pausing one source without stopping all traffic.

The goal is not to hand over every trade secret.

The goal is to provide enough information for a serious buyer or exchange to understand what is being offered and decide whether it belongs in the call path.

Dependable Calls has a broader guide on how to prepare traffic for buyer review, and buyers can use the publisher call-traffic review checklist.

Source review should be specific to the ACA call path

A source can be legitimate and still be inappropriate for a particular buyer.

The review should examine the actual flow:

Search ad to landing page to consumer-initiated call.
Social ad to lead form to outbound contact and transfer.
Owned content site to tracked phone number.
Partner traffic to an upstream call center and then a warm handoff.
Existing customer or referral traffic to a licensed agency.
Another path approved by the buyer and reviewed for the applicable requirements.

Each path creates different evidence and failure modes.

Creative and landing-page review

The reviewer should compare:

The headline.
The benefit or coverage claim.
The visual presentation.
The advertiser identity.
The call-to-action.
Disclosures.
The expected caller.
The actual buyer experience.

A creative should not pass review merely because it contains a disclaimer somewhere on the page. The overall consumer impression matters.

Transfer review

For transfers, review:

The original acquisition source.
The outreach or call basis.
The script.
The screening questions.
The consumer’s understanding of the handoff.
The identity presented before and after transfer.
The fields or information passed.
Recording and retention practices where applicable.
How the transfer is labeled in reporting.

Sub-source control

Aggregated ACA supply can hide meaningful differences.

One sub-source may use clear search traffic. Another may use broad social ads. Another may rely on an upstream call center. If all three arrive under one label, performance and complaint patterns cannot be isolated.

The buyer does not necessarily need the publisher’s full private relationship map. It does need enough scoped transparency to approve, pause, and review materially different sources.

That is why compliance is becoming a main differentiator in pay-per-call.

Routing should preserve the reason a call did or did not move

A professional ACA routing decision should produce a reason, not just a result.

Possible exclusion reasons include:

Source not approved.
Traffic type not accepted.
Buyer or target inactive.
Outside schedule.
State not accepted.
No eligible licensed destination.
Cap reached.
Concurrency full.
Budget unavailable.
Duplicate policy triggered.
Destination unhealthy.
Required data missing.
Campaign paused.
No valid bid or reservation.

Those reasons matter to both sides.

The buyer needs to know whether volume is being blocked because of capacity, eligibility, or source quality. The publisher needs feedback that distinguishes “buyer closed” from “source rejected.” Finance needs to understand whether a call was merely offered, actually routed, connected, qualified, converted, or excluded before buyer delivery.

A single status called “failed” is not enough.

Duration-based and CPA ACA campaigns settle differently

ACA calls may be purchased under a duration rule, a conversion rule, or a hybrid arrangement.

Duration-based settlement

A duration-based campaign might make a call billable after a defined connected-time threshold, subject to geography, traffic type, duplicate policy, and other rules.

The appeal is speed: the billable result may be known soon after the call ends.

The risk is that duration can be mistaken for value. A confused caller can stay on the line. A queue can inflate total time. A long conversation can still be outside the buyer’s accepted criteria.

Duration should be one measured event, not a substitute for source review.

CPA or conversion-based settlement

A CPA campaign may depend on a later policy, enrollment, or other defined conversion event.

That changes the financial workflow:

The call can route today.
The conversion can be reported later.
Buyer revenue may not be final when the call ends.
Publisher payout may depend on the confirmed conversion.
Conversion data may come from a buyer report, CRM, carrier-related record, or approved integration.
Duplicate, cancellation, or correction rules may affect the final result.
The operation needs a reliable way to match the later event to the original call.

The agreement must define what counts as a conversion and which system or record is authoritative.

A buyer price is what Dependable Calls charges the buyer.

A publisher payout is what Dependable Calls pays the publisher.

Those amounts and statuses should not be collapsed. A converted buyer charge and a publisher payable event may be related, but they remain separate financial legs that need their own records.

Reconciliation is part of ACA call quality

A campaign is not complete when the phone disconnects.

The operation still needs to reconcile:

Calls offered.
Calls routed.
Calls connected.
Calls that met the qualification rule.
Calls reported as converted.
Calls treated as duplicates.
Calls disputed.
Buyer charges.
Publisher payables.
Adjustments.
Invoice and payout batches.

CPA reporting can arrive after the original call date. That creates a risk of missing conversions, duplicated conversions, unmatched records, or rate disagreements.

A clean process should support:

Stable call identifiers.
Source and target attribution.
Consistent timestamps and timezones.
Defined matching keys.
Idempotent conversion posting.
Exception queues for ambiguous matches.
Read-back verification after adjustments.
Buyer-facing and publisher-facing reports that reconcile to the same operating record.
A documented cutoff and correction process.

A buyer may judge a source poorly if conversions are not posted correctly. A publisher may believe it was underpaid if the payout report cannot explain delayed outcomes. Reconciliation is not merely accounting. It affects source decisions and partner trust.

Common ACA campaign failure modes

The consumer expected a different benefit

The marketing emphasized cash, a card, or a government benefit more than health insurance. The buyer receives a consumer who did not expect an insurance conversation.

ACA, Medicare, Medicaid, and general U65 traffic were blended

The source uses a broad health label, but the buyer only handles a narrower category.

The call reached an ineligible destination

The consumer’s state did not match the receiving agent’s licenses, registration, product availability, or approved workflow.

Off-season traffic was treated like Open Enrollment traffic

The consumer wanted coverage, but the call path did not account for Special Enrollment eligibility or another appropriate coverage route.

Transfers were sold as direct inbound calls

The buyer expected a consumer-initiated call but received a caller who had already passed through an upstream center.

Buyer capacity was overstated

The buyer had a high daily appetite but insufficient live concurrency, causing no-answers, long waits, abandoned calls, and disputes.

One source label hid several traffic paths

Good and weak sub-sources were blended, so nobody could isolate the cause of performance or complaint changes.

Duration was treated as proof of quality

Long calls were paid even when caller expectations, geography, or product fit were wrong.

CPA conversions could not be matched reliably

Buyer reports arrived later without stable identifiers, creating manual reconciliation and payout disputes.

Records existed but could not be produced

The operation said it had consent, creatives, recordings, or approvals, but could not connect the record to the specific source and time period under review.

A practical ACA buyer launch checklist

Before the first call, the buyer should be able to answer:

What exact ACA or under-65 health category are we buying?
Which states are accepted?
Which teams or agents are eligible for each state?
Are Marketplace registration and training current where required?
Are consumer-initiated inbound calls accepted?
Are transfers accepted?
What marketing paths have been reviewed?
What source and sub-source labels will appear?
What enrollment periods or eligibility contexts are expected?
What does the caller hear when the buyer answers?
What makes a call qualified?
What makes it billable?
What makes it payable to the publisher?
What makes it converted?
How are duplicates handled?
What are the schedule, cap, concurrency, and budget rules?
What happens when the first destination is unavailable?
How are complaints tied back to a source?
How quickly can one source be paused?
What reports support invoice and payout reconciliation?
Who approves changes after launch?

The buyer is not ready to scale because the campaign has a phone number.

The buyer is ready when the operation can answer those questions and enforce the answers.

A practical ACA publisher readiness checklist

Before offering traffic, the publisher should be able to answer:

What creates the call?
Is the traffic owned, partner-supplied, or aggregated?
Is it consumer-initiated inbound or transferred?
What does the consumer see or hear?
What insurance or benefit category is presented?
Which states and hours can the source support?
How are ACA, Medicare, Medicaid, and other health categories separated?
What source labels will remain stable?
Are creatives and landing pages available for review?
Are transfer scripts and handoff steps documented?
What records are retained?
Can the publisher pause a weak sub-source quickly?
How will the publisher investigate a complaint?
What volume is realistic during Open Enrollment and outside it?
Does the publisher understand the buyer’s qualification and settlement rules?
Can the publisher reconcile call-level results to a payout report?

A publisher does not need to promise perfection.

It needs to show control over its own traffic.

How this fits Dependable Calls

Dependable Calls is being built as a controlled, operator-led pay-per-call exchange.

The current application implementation includes ACA as a campaign vertical, supports separate consumer-inbound and transfer traffic types, and includes a structured publisher campaign-application workflow with review materials such as creatives, landing pages, lead-generation methodology, data samples, recording samples, and compliance attestations.

That is implementation evidence.

It is not proof that every ACA workflow is available, fully hardened, or validated under live buyer and publisher conditions. Buyer availability, state coverage, counsel review, source approval, product eligibility, telephony behavior, settlement, and operational readiness still need to be confirmed for each live program.

The operating direction is based on two gates:

Dependable Calls determines which reviewed sources are appropriate to offer to a buyer.
The buyer decides which offered sources to enable for a particular target or call path.

Both gates must be satisfied before a curated source routes.

For ACA traffic, that model matters because not every source belongs with every buyer, and not every buyer is eligible or ready for every caller.

The goal is not to make ACA traffic move as freely as possible.

The goal is to create a call flow that can explain:

Where the call came from.
What the consumer expected.
What traffic type was used.
Why the buyer was eligible.
Why the source was enabled.
Why the call routed.
What happened after connection.
Why the call became billable, payable, or converted.
What records support the result.

That is the difference between moving health-insurance calls and operating a dependable ACA call program.

Ask Dependable Calls which health-insurance verticals are currently open for buyers or publishers. Start a conversation with Dependable Calls.