The HealthSherpa Medicare : AgencyBloc integration syncs your contact data from AgencyBloc (AMS+) to HealthSherpa, and syncs enrollment and contact data from HealthSherpa back to AgencyBloc when you submit an enrollment.

This eliminates the need to manually re-enter client data into HealthSherpa and manually reconcile enrollment data back into AMS+ – so you're spending less time on data management, and more time helping your clients.

This is what the flow looks like – starting on AMS+, syncing data into HealthSherpa to quote and enroll with, and syncing enrollment and contact data back to AMS+. Click through the demo below, or here.

↗️ View AgencyBloc's detailed guide

⏯️ Watch a webinar of the integration setup

MAPD, MA, Part D, Med Supp.

Any agency using AMS+. The integration is activated at the agency.

Not in this release. ACA support via HealthSherpa is planned as a separate integration and will be communicated when available.

Yes, if you're have Rx Collect turned on in AWS. If you don't they'll still come over but entered as plan text inside of the Contact's notes records.

In HS, on the Contact Detail, scroll down to the Activity Log and you'll see the logs:

If you see an error when you click "Send to HealthSherpa Medicare" in AMS, such as "An error occurred while communicating with HealthSherpa" check a couple things:

Is their MBI entered correctly? If it doesn't match the CMS pattern described here, it's considered invalid and will cause an error.

Is agent assigned on both sides? For the sync to work, 2 things must be true:

1. The Individual in AWS must be assigned to the agent who is syncing, as seen here:

2.The corresponding Contact record in HealthSherpa must be assigned to the agent doing the syncing, as seen here:

Is the integration connected?

If you're the agency owner for AWS, log into your account and ensure the integration is connected, as shown here:

If a client synced successfully once, but every attempt to update them now fails, the client is likely assigned to a different agent in HealthSherpa than the one syncing from AMS. HealthSherpa Medicare requires the agent sending the update to be the same agent already assigned to that client in HealthSherpa. If they don't match, the update is rejected immediately – no data goes through at all, and you'll see an error right away. To fix this reassign the Contact to the correct agent in HealthSherpa.

Each person on your team who sends clients from AMS needs their own individual HealthSherpa Medicare login, connected separately. A shared or agency-wide login won't work for every team member. Check:

If they don't have an account yet, they'll need one created and connected before any of their syncs can succeed.

This usually happens when a client already exists in HealthSherpa under a teammate's account, and someone else tries to send that same client from AMS. Because each agent can only see their own clients, AMS can't find the existing record and creates a brand new one instead – leading to two separate contacts for the same person. To avoid this: