What the documented connection does.
AgencyZoom’s official AMS360 documentation describes lead and activity handoffs into AMS360 and customer information returning to AgencyZoom. The setup includes an AMS360 web-service connection, notifications, and field mapping. The supported details and settings matter; this should not be interpreted as every field or event synchronizing in both directions.
Before connecting the accounts.
Identify who can authorize and administer the integration in each system. Agree on which records should participate, how producer identities map, and which system your team treats as authoritative for each piece of information. Keep integration credentials out of shared notes, public forms, and client-side website code. Follow the vendor’s current setup instructions rather than an old screenshot.
Treat mapping as an operating decision.
A technically valid mapping can still put a record in the wrong business context. Review the meaning of policy types, staff assignments, statuses, and customer identities with someone who knows the agency’s data. Use a small, representative set of records to verify the result before relying on the connection for a wider workflow.
- Check a new prospect and an existing customer.
- Confirm the intended producer or service owner.
- Compare relevant contact and policy values on both sides.
- Decide how the team should handle a potential duplicate.
Verify the next action, not just the copied data.
After the data arrives, check what the agency expects to happen. Does the right person receive a task? Does the record enter an appropriate workflow? Could an import unintentionally enroll existing customers in a new-customer sequence? Confirm the configuration before turning on customer-facing communication.
Allow for synchronization and exceptions.
Initial transfer timing depends on data volume and settings. Document the test time and expected result so an apparent delay can be distinguished from a mapping or permission problem. When behavior falls outside configuration you control, collect a concise example for official vendor support. Do not repeatedly reconnect or re-import a large dataset without understanding the effects.
Verify the vendor requirements before connecting.
This guide adds workflow planning and testing considerations. It is not a substitute for the provider’s current setup instructions or confirmation of features in your account.
AgencyZoom: AMS360 integration documentation ↗Let’s take CRM work
off your plate.
Tell us what your agency needs. We’ll discuss the next step.