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.
Demo
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.
Setup
That guide describes adding your AgencyBloc webhook URL and API key to a webhook in HealthSherpa – see how to add webhooks to HealthSherpa. This sends enrollment data back from HealthSherpa Medicare to AgencyBloc.
Passcode:
uQ0J^6sY
FAQ
Which plan types does the integration support?
MAPD, MA, Part D, Med Supp, and DVH.
Which agencies are eligible to use this integration?
Any agency using AMS+.
Will this integration support ACA plans?
Not in this release. ACA support via HealthSherpa is planned as a separate integration and will be communicated when available.
Do drugs, providers and pharmacies transfer over?
Yes, if you have Rx Collect turned on in AMS. If you don't they'll still come over but entered as plain text inside of the Contact's notes records.
How do I know what data synced from AMS to HS?
In HS, on the Contact Detail, scroll down to the Activity Log and you'll see the logs:
For more information, see AgencyBloc's full setup & integration guide ↗️
Troubleshooting
I'm getting an error when syncing a client
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 AMS 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 AMS, log into your account and ensure the integration is connected, as shown here:
I sent a client before with no problem, but now updates to that client fail
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.
One of my team members can't sync any clients – every attempt fails
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:
Does this person have their own HealthSherpa Medicare account?
Is that account connected in AMS under their own AMS login?
If they don't have an account yet, they'll need one created and connected before any of their syncs can succeed.
I'm seeing two contacts for the same client in HealthSherpa
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:
Before sending a client, check whether a teammate has already synced them.
If a duplicate is created, combine data into one, and merge the other.
How does AgencyBloc match clients to existing HealthSherpa Medicare contacts?
When you click Start Quote in AgencyBloc, AgencyBloc checks whether the client already exists in HealthSherpa Medicare before creating a new contact.
See details
See details
First send of a client
If the client has a Medicare Beneficiary ID (MBI) in AgencyBloc, AgencyBloc looks for a HealthSherpa Medicare contact with the same MBI. It does not check name or date of birth.
If the client has no MBI in AgencyBloc, AgencyBloc looks for a contact with the same first name, last name, and date of birth.
If a match is found, that contact is updated with the client's AgencyBloc data.
If no match is found, a new contact is created.
Later sends
Once a client is linked to a HealthSherpa Medicare contact, AgencyBloc remembers the link. Later sends update the same contact directly, even if the client's name, date of birth, or MBI changes.
Avoiding duplicates
A match only works if your existing HealthSherpa Medicare contact has the same information AgencyBloc searches on. This is common with contacts that were imported or entered with only a name. Before sending a client from AgencyBloc for the first time:
If the client has an MBI in AgencyBloc, add the same MBI to their HealthSherpa Medicare contact.
If not, make sure the HealthSherpa Medicare contact has the same first name, last name, and date of birth.
If a duplicate was already created, keep the contact with the client's history, make sure it has the MBI, and archive the extra contact.
For more information, see AgencyBloc's full setup & integration guide ↗️
Questions?
For AgencyBloc issues, contact help@agencybloc.com or (866) 338-7075
For HealthSherpa issues, contact (855) 521-4984 or medicare-agents@healthsherpa.com.