For immediate release · September 14, 2026
AgencyView Integrates HealthSherpa for ACA and Medicare Quoting and Enrollment From the Client Record
Agents quote marketplace plans, enroll on- or off-exchange, and keep Medicare-eligible clients in sync with HealthSherpa without leaving AgencyView; enrollment and policy status flow back to the client record automatically.
SHERIDAN, WYO. — September 14, 2026 — AgencyView, the all-in-one agency management and commission tracking platform for insurance agencies, today announced its integration with HealthSherpa, the ACA quoting and enrollment platform, and with HealthSherpa Medicare. Agents quote Affordable Care Act marketplace plans from a client’s record in AgencyView, enroll the household on-exchange through HealthSherpa or off-exchange directly through its API, and see the application and policy status come back to the same record. Medicare-eligible clients are kept in sync with HealthSherpa Medicare automatically, and an enrollment submitted there returns to AgencyView as a policy. The integration is live now for AgencyView agents and agencies with a HealthSherpa account.
Marketplace plans returned by HealthSherpa, shown inside AgencyView with the subsidy applied. Captured from the AgencyView Agency Demo account.
HealthSherpa describes itself as the “#1 ACA Quoting and Enrollment Platform,” used by 45,000 agents and 4,800 agencies, with full Healthcare.gov synchronization and no cost to agents. AgencyView chose to build on that platform rather than beside it: enrollment stays with the system agents already trust, and AgencyView supplies what surrounds the application: the client record, the household, the policy, the commission that follows it, and the compliance file.
“Enrollment is a solved problem, and HealthSherpa solved it. What agencies were missing was everything on either side of the application: the lead before it, and the policy, the commission and the compliance record after it. We built the integration so an agent never re-keys a household and never wonders whether an application went through.”
— AgencyView, in a company statement
What the ACA integration does
- Quoting from the client record. The primary applicant is prefilled from the record; the agent confirms the ZIP code and county, adds household members, and enters income. AgencyView sends the household to HealthSherpa and renders the returned plans with the estimated subsidy, deductible, copays, and a link to each plan’s Summary of Benefits and Coverage.
- On-exchange and off-exchange in one window. The same household can be quoted against the marketplace or off-exchange with a toggle; HealthSherpa’s response tells AgencyView which enrollment path a plan supports.
- Enrollment. Selecting a plan writes a pending policy to the client record, sets a follow-up task for the carrier-issued policy number, and either continues the enrollment on HealthSherpa with the applicant already loaded (agent-assisted) or issues a client link with that plan pre-selected (self-service). Off-exchange plans are submitted directly through the HealthSherpa enrollment API.
- Status written back. Application and policy status are read from HealthSherpa on a schedule and reflected on the record and in AgencyView’s Policy Status Queues, so pending, effectuated and terminated cases are visible without a second login.
- Providers to the care team. Doctors and facilities the household wants to keep are searched through HealthSherpa’s provider reference and saved to the client’s care team in the CRM.
- One connection for the agency. An agency admin connects a HealthSherpa API key once and shares it with the team; agents use it automatically and never handle the key.
The household step. The primary applicant comes from the client record; other linked contacts are offered as applicants.
Selecting a plan creates the pending policy and the follow-up task, then hands the enrollment to HealthSherpa or to the client.
The pending policy on the client record, before the carrier issues its number.
What the Medicare integration does
- Automatic contact sync. Clients who are 65 or older, who turn 65 within nine months, or who already hold an MAPD, MA or PDP policy are created or updated in HealthSherpa Medicare, with the client’s Medicare number included when it is on file. HealthSherpa’s own contact identifier and quoting link are written back to the AgencyView record.
- Two triggers. A change to a client record syncs that client at once; a daily sweep catches anyone who became eligible since the last run.
- Duplicate protection. Before creating a contact, AgencyView searches HealthSherpa Medicare for an existing match and updates it instead of creating a second one.
- Enrollment submissions returned. When an application is submitted in HealthSherpa Medicare, its webhook delivers the submission to AgencyView, which records a policy on the matching client, adds a note, and ignores repeated deliveries.
- Turning-65 report. A monthly report lists the clients who will age into Medicare, drawn from the same eligibility rule.
Both connections are managed by the agency admin and shared with the team.
How the integration is built
The ACA side runs on HealthSherpa’s published API. An agent or agency admin pastes a HealthSherpa API key into AgencyView; the key is verified against HealthSherpa before it is stored, is held server-side, and is never returned to the browser. Quotes, county and provider lookups, hosted enrollment sessions, direct enrollments and policy-status reads each go through AgencyView’s own server functions, which add the key and forward the request, so no HealthSherpa credential ever reaches a user’s device. Direct enrollments carry an idempotency key so a retried submission cannot create a second application. Credential sharing is a per-user grant, not a copied key: revoking a grant removes access without rotating anything.
The Medicare side uses HealthSherpa Medicare’s partner API with an OAuth 2.0 authorization-code connection. Refresh tokens rotate on every use and the newest one is persisted. Contacts are created and updated by HealthSherpa’s own contact identifier, with the AgencyView client identifier carried as the external reference so that submissions coming back through the webhook resolve to the right record. Each connected agent registers a unique webhook key in HealthSherpa Medicare, which is how AgencyView attributes an inbound submission to the right agent without relying on an email address.
About HealthSherpa
According to its website, HealthSherpa is the largest ACA enrollment platform since 2013, used by 45,000 agents and 4,800 agencies, with 10 million lives and $71 billion in premiums enrolled, offered at no cost to agents because carriers pay its fee. HealthSherpa Medicare is its FMO-neutral, multi-carrier Medicare platform for brokers. HealthSherpa is not affiliated with AgencyView, and this announcement is AgencyView’s alone.
Availability
The integration is live now for AgencyView agents and agencies with a HealthSherpa account: connect HealthSherpa ACA and HealthSherpa Medicare under Settings, share the connection with the team, and quote from the client record. AgencyView plans start at $159 per month with a 14-day free trial. A plain-language guide for agents is on the AgencyView blog, and future announcements will be posted to the AgencyView newsroom.
About AgencyView
AgencyView is the all-in-one agency management and commission tracking platform for insurance agencies. It brings clients, policies, commissions, and compliance behind one login: quote-to-enrollment workflows, AI commission reconciliation against carrier statements, agency hierarchy and split management, call coaching, and HIPAA-compliant client records. AgencyView is built for independent agents, agencies, and the FMOs and IMOs that support them. Learn more at agencyview.net.
Media contact
AgencyView
30 N Gould St, Sheridan, WY 82801
media@agencyview.net
https://agencyview.net/press
Related links
Source: https://agencyview.net/press/healthsherpa-integration
Back to the newsroom