Insurance CRM and AMS: who does what
An agency management system keeps the policy, and an insurance CRM keeps the work around it. The AMS is the system of record for policies, terms and rating. The CRM owns the quote request, its owner, the renewal date and the next step with the household.
- The AMS answers what the client has. The CRM answers who is doing what about it, and by when.
- Neither replaces the other. The AMS stays authoritative for the policy.
- The work that falls between them is where agencies lose business: new Lead response, renewals and cross-sell.
What each system keeps
Two systems, with a clear line between them.
- Policies, terms and endorsements
- Carriers and the rating that produced the quote
- Client and policy documents
- The authoritative record of what the client has
- The quote request as a Lead, with its source and owner
- Routing by license, state and line
- Each renewal as a Lead with a date and a clock
- The household on one Contact, with consent, conversations and every action
Where work falls between the two
A policy record tells you a term expires in sixty days. It does not tell you who is calling the client, whether they tried, or what happens if they do not. That is work, and work needs an owner and a clock.
The same is true before the policy exists. A quote request from a marketplace is not yet anything in the AMS. Until someone licensed for the state and the line picks it up, it is only a Lead.
- A new quote request, answered by a producer who may quote it
- A renewal, worked as a Lead with a date inside the outreach window you permit
- A home-only household that could also insure the car
- A hand-off from the call center to the agency, with consent and source intact
What should flow between them
Policy terms and dates come from the AMS so the CRM can open renewal and cross-sell work at the right time. What the producer did, and what the client said, stays on the CRM record. The AMS remains the source for the policy itself.
The exact objects and direction depend on your setup. Get them written down before a pilot, and ask what happens when the two systems disagree.
- Does renewal and cross-sell work have an owner and a clock outside the policy record?
- Does routing check the producer’s license, state and line before the offer?
- Can the CRM read an AMS event and open a task from it?
- Does an opt-out follow the person across every line of business?
Is the CRM inside the AMS enough?
For an agency whose new business is mostly referrals, it can be. The case for a separate CRM grows with paid lead volume, several producers and licenses, a call center, or renewals nobody clearly owns.
Judge by function. Run the same scenario in both: a marketplace Lead for a state only two producers are licensed in, arriving at a busy hour. See who gets it, how fast, and what the record shows afterwards.
Common questions
Does an insurance CRM replace the AMS?
No. The AMS stays authoritative for policies, terms and rating. An insurance CRM owns the work around the policy and reads from the AMS only in the ways confirmed for your setup.
Is an insurance CRM a rating or quoting engine?
No. Quotes are produced where they are today. The CRM tracks the quote request as a Lead, routes it to a licensed producer and records what happened.
Do small agencies need both?
Not always. An agency that grows by referral may be well served by its AMS. A CRM earns its place when Leads are bought, several producers hold different licenses, or renewals and cross-sell have no clear owner.
Where should consent and opt-outs live?
On the person, visible wherever outreach starts. In Botsplash CRM consent and suppression sit on the Contact and show on every Lead. Your compliance team sets the rules; no software setting makes a business compliant on its own.