AMS360: What to Clean Up Before Offloading Insurance Operations

AMS360 by Vertafore is a widely used insurance agency management system among independent P&C agencies that manage a mix of personal and commercial lines. It has strong policy management and renewal tracking capabilities, but like most AMS platforms, the degree to which those capabilities are configured varies enormously by agency. Before outsourcing back office operations on AMS360, these are the most common gaps that create problems in the first 60 days.

The most common AMS360 gaps before outsourcing

Activity and diary not configured for workflow routing. AMS360’s activity and diary system is the primary task management mechanism. Agencies that rely on informal task assignment — email or verbal direction rather than AMS activity creation — will find that an outsourced team has no visibility into what needs to be done. Activity types, assignment rules, and follow-up triggers need to be configured before handoff.

Policy records with inconsistent expiration tracking. AMS360’s renewal report depends on expiration dates being accurately maintained at the policy level. Agencies that renew policies without updating the AMS record, or that carry lapsed policies as active in the system, will produce a renewal queue that requires manual verification before any outsourced team can work from it.

Notes and attachments stored without naming standards. AMS360 supports rich document and note management, but without naming conventions, documents accumulate in a way that makes retrieval unpredictable. An outsourced team processing COIs or endorsements needs to find current policy documents reliably, not search through five years of unstructured attachments.

Certificate holders and additional insureds not maintained. Recurring COI requests depend on certificate holder records being current in the system. Agencies that issue certificates from memory or maintain certificate holder lists outside of AMS360 will not be able to hand off COI processing until that data is in the system.

What AMS360 does well for outsourcing

AMS360 has strong policy management structure and good reporting tools for renewal tracking. Its integration with Vertafore’s broader product suite — including eDocs and messages — supports document workflows that translate well to outsourced operations once configured. The platform also has relatively straightforward user provisioning for external team access.

What to fix in AMS360 before handing off

Configure activity types and assignment rules for the three task types being outsourced. Audit active policies for expiration date accuracy. Establish a document naming convention and apply it going forward. Migrate certificate holder and additional insured records into AMS360 if they are currently maintained externally. Provision user access for the outsourced team with appropriate permissions.

Frequently asked questions

Can an outsourced team work in AMS360?

Yes. AMS360 supports named user access with configurable permissions. The agency controls what the outsourced team can access. External user provisioning should be reviewed with Vertafore to confirm licensing terms for outsourced team access.

What is the biggest AMS360 issue agencies hit when outsourcing?

The most common issue is an activity and diary system that was never configured for team-based workflows. Agencies that managed tasks informally — through direct communication with the owner — discover this gap immediately when an outsourced team takes over and has no structured task queue to work from.

For the full AMS readiness overview: Insurance Agency Management System: What to Fix Before You Outsource

Talk to COVU about AMS360 readiness and outsourcing your insurance back office

Based on COVU’s operational experience managing back office operations across 50+ independent P&C agencies and $200M+ in premium.