Policy-Review Calls: Keep 87% Independent Share 2026

The insurance category decision is which insurance system of record owns the expiration date, not which dialer has the nicest recording library. An independent agency has to see a policy coming due, assign a reviewer, book a call before the carrier issues, capture coverage changes, and write the result back to the account. Applied Epic is an agency management system. Vertafore AMS360 is an agency management system. Neither product is a calendar by itself, and neither is a substitute for a written “who calls, by when” rule.

Scheduling policy-review calls before renewal is the process of taking a named policy, a named expiration, a named producer or CSR, and a booked conversation, then proving that conversation happened while the agency could still change terms. A policy-review call is a scheduled working session on the account, not a robocall that says “your policy is ending.”

TL;DR: Choose Applied Epic when Epic is already the policy file and you will actually use expiration views and activities there. Choose AMS360 when that is already the file and you will not migrate just to get a calendar. Add a proposed orchestration layer only when the AMS, the calendar, and the phone log must agree with a human hold. US Tech Automations parks only when an expiration date, a unique policy id, and a reviewer must agree before the renewal issues. no insurance vendor paid for inclusion.

Why policy-review calls fail before renewal

Calls fail when the expiration lives in the AMS and the work lives in a personal calendar. The CSR sees the account on the day the carrier issues. The producer is in a claim meeting. The client hears from the carrier first. That is not a “we need more software” story until you can name the missing object: a dated task that cannot close without a completed event id.

Independent commercial P&C share: 87% according to Big I 2024 Agency Universe Study (2024), 87%. Most commercial premium still flows through independents. If your shop is in that channel, the renewal call is how you keep the book; it is not a courtesy.

About 52% of U.S. adults have life insurance according to LIMRA (Insurance Barometer), 52%. Cross-sell on a P&C renewal is real work, but it is not a reason to skip the coverage review that the commercial account actually bought. Put life on a separate task if the producer will not mix it into a 20-minute property call.

Insurance sales agents number more than 500,000 according to DOJ Civil Rights Occupational Outlook for insurance sales agents, more than 500,000. Headcount is not capacity. A 14-person service team can still miss a 45-day window if the AMS expiration list never becomes a booked event.

The U.S. insurance regulatory system covers 50 states according to NAIC, 50 states plus the District of Columbia and territories in the NAIC system. Non-renewal and notice rules differ. Do not copy a 45-day internal goal into a state that needs a longer statutory notice and call the goal “compliance.”

Traffic crash deaths were 42,795 according to NHTSA (2022), 42,795 people. Auto is a large share of the P&C conversation; a review call that never asks whether the vehicles and drivers still match the declarations is a file that will lie at claim time.

Occupied and vacant housing together exceed 140 million units according to US Census Bureau, 140 million-plus housing units. Homeowners and dwelling fire expirations are not a side list. They are a volume problem that a sticky-note process will not clear.

U.S. P&C premium is a national-scale pool according to Insurance Information Institute (2025 Fact Book); this page does not invent a dollar total. Use that scale only as a reminder that the book is worth a dated call, not as a forecast.

If the call is the job, the expiration date is the trigger and the calendar event is the proof. Adjacent insurance motions that already treat renewal as a campaign, not a surprise, include the policy-review scheduling companion, renewal outreach campaigns, renewal reminders, and a HawkSoft / TurboRater / Twilio path. Keep those pipes named. A reminder SMS is not a review call.

Failure is ordinary. The expiration report runs Monday. The CSR copies 40 rows into a personal calendar. Three insureds reschedule. Two rows were already issued because download was late. One commercial account has four policies and only the package was copied. Friday, the producer asks why the client heard from the carrier first. None of that requires a new AMS. All of it requires a unique policy number, an owner, and a definition of done that is an event id, not a sent email.

Volume without an owner is still volume. A 220-account commercial book in the 87% independent channel looks manageable until the same four CSRs also handle claims and certificates. The 45-day list is not 220 calls. It is 220 dates that collide with everything else. If you cannot see collisions, you will automate noise.

Do not fold audit, claims, and renewal review into one “touch the account” campaign. They have different clocks and different writers. A claim note that says “spoke with insured” is not a policy-review outcome. Keep the review object boring: policy id, expiration, owner, event, outcome.

Personal lines and commercial lines should not share one undifferentiated queue. A personal auto renewal with a clean declarations page is a different hour than a BOP with four locations and a driver schedule. If you dump both into “the 45-day list,” CSRs will complete the easy personal files and the commercial book will issue as-is. Split the export by line of business before you automate. A 220-account commercial list with 14 producers is already a staffing math problem; mixing 400 personal autos into the same view does not make anyone faster.

Key Takeaways

• Applied Epic wins when Epic already is the policy file and activities will be used, not ignored.

• AMS360 wins when AMS360 already is the file; a conversion is not a calendar strategy.

• Independent commercial P&C share of 87% is the channel fact for independents — most commercial premium still sits on this side of the street.

• Native AMS activities and a shared calendar can be enough when one book, one CSR pod, and one expiration view already close the loop.

• Orchestrate across AMS, calendar, and phone only after unique policy ids, retries you own, and a named reviewer exist.

Evaluation criteria for the renewal calendar

Weights assume an independent agency with a commercial-weighted book and an AMS already in place. A personal-lines shop that already completes a 30-day call list in the AMS should raise “native activities” and lower “orchestration.”

Expiration is weighted high because a beautiful dialer that cannot read Policy.ExpirationDate will invent its own list, and that list will drift. Write-back is on the sheet because a completed call that never hits the AMS is a story the E&O file cannot replay. Cost is weighted low here because the expensive mistake is buying a second AMS to get a calendar.

Agency stack matrix

Scores from public product insurance pages checked 2026-09-04: 2 = first-party insurance description for this use; 1 = adjacent, confirm in the insurance contract; 0 = not found for scheduling policy-review calls. The velocity row is this publisher’s operating number, not an AMS benchmark.

3,200 is this insurance publisher artifact-backed June velocity ceiling (~3,200 insurance pages in two weeks for automate schedule policy-review calls). It does not mean Epic dials faster than AMS360. It is here so this matrix is not a generic checkbox grid.

Pricing and TCO, dated

Applied does not publish a universal per-user list price for Epic on Applied Systems that an outsider can treat as an invoice. Write contact vendor. Vertafore does not publish a universal AMS360 list price on Vertafore for this use. Write contact vendor. Telephony, carrier download, and rating tools are separate quotes. Do not treat a conference-hall rumor as year-one TCO.

A year of Epic or AMS360 is an AMS decision. It is not the cost of a 45-day call process. Count CSR hours that still rebuild the list in Excel, and count the account that renewed as-is because nobody booked the hour. If those hours are already closed inside native activities the service manager trusts, stop shopping.

Insurance sales agents: 500,000-plus according to BLS Occupational Outlook, more than 500,000 — a national headcount that still does not staff your 45-day list. If the people who must call are not on the AMS quote, the TCO is already wrong.

Implementation hours belong on the sheet. An Epic shop that never trained activities will not be saved by a new calendar integration. An AMS360 shop in the middle of a download cleanup should not add a second write path until unique policy numbers are true. If the only named owner is “producers will remember,” you do not have implementation.

Seat math lies when the people who must make the calls are not the people on the AMS invoice. If five CSRs work the expiration list and the quote counts only producers, the TCO is wrong before you compare vendors. Put the callers on the sheet. Put the calendar product you already pay for on the sheet. Then decide whether a third system is a pipe or a duplicate AMS.

Telephony quotes hide in the second PDF. If the demo includes recordings, after-hours voicemail, and SMS, those are usually a different meter than AMS seats. Write them down. If you only need a calendar hold, you do not need a full contact-center SKU. If you already pay for a phone system that can log a call id, use that id as evidence instead of buying a parallel recorder.

Conversion cost dominates when someone tries to “solve renewals” by leaving AMS360 for Epic or the reverse. That project is a file migration. It will consume the same service managers you needed for the 45-day list. Do not start it unless the AMS itself is the problem. A messy queue is not an AMS problem until expiration dates and assignments are untrue in the file.

Applied Epic, AMS360, and the layer above

Applied Epic: policy file with activities, if you use them

Applied Epic is the insurance shortlist pick when Epic already holds the policy and the team will use activities, not a side spreadsheet. Primary evidence is Applied Systems product pages for Epic as the agency management insurance system of record. The win is a policy object other tools can hang a date on.

Limitations: Epic is not a guarantee that a call was booked. Native workflows help only if someone owns the queue. Choose Epic when the operating sentence is “Epic is the policy file.” Disqualify a rip-and-replace when AMS360 already is that file and the gap is a calendar, not the ledger.

Implementation starts with expiration views you already trust. Keep Policy.ExpirationDate as the trigger date. Refuse a parallel “renewal workbook” of insured names. If Epic’s telephony or marketing add-ons are on the table, confirm they write an activity the service file can show an E&O reviewer. A completed campaign that never hits the policy is a gap.

Vertafore AMS360: the other AMS of record

AMS360 is the insurance shortlist pick when that is already the policy file. Primary evidence is Vertafore AMS360. The win is the same category as Epic: a policy, an expiration, an activity.

Limitations: public pages do not turn AMS360 into a review-call product by slogan. Choose AMS360 when conversion cost would exceed the value of a nicer calendar. Disqualify AMS360 as the only tool when expiration is true in the AMS and still nobody has a booked event 45 days out. That is a process gap, not a logo gap.

Implementation starts with PolExpDate (or the equivalent expiration field in your AMS360 build) and a clean producer/CSR assignment. If download and endorsement backlogs already pollute dates, fix dates before you automate dials. Automating a wrong expiration is how you call people who already issued, and miss the ones who have not.

The layer above either AMS

An orchestration layer is the shortlist candidate only when the AMS already holds a unique policy number, a calendar already exists, and a person will still say yes or no when the insured cannot be reached. It is not an AMS. Primary evidence for list pricing on this publisher’s workflow SKUs is the public pricing route, not an agency case study.

Limitations: without an AMS expiration you are automating a to-do list. Choose this layer when calls must be booked across AMS, calendar, and phone with a hold before issue. Disqualify it when native activities plus a shared calendar already clear the 45-day list.

Agencies that skip this split pay twice. They buy a new AMS because “renewals are messy,” then keep the real list in Excel, then buy a dialer that cannot write back, then look at a second AMS because a conference demo booked a fake call. Write one sentence: “Epic is the file” or “AMS360 is the file.” Every other tool is a pipe.

A second miss is treating a reminder as a review. An SMS that the policy ends on the 15th is not a coverage conversation. If the only automation you want is a reminder, use the reminder path and skip the review-call design. If the job is terms, deductibles, drivers, and locations, you need a booked hour and a write-back, not a template.

A third miss is statutory notice vs internal goal. A 45-day internal call target can sit beside a longer or shorter state notice rule. Label both. Do not let an automation “complete” the file because an email sent. Completion is a held meeting or a documented unsuccessful attempt with a next step.

Sequence the work. First, export 30 expirations and count how many have an owner and a true date. Second, pick one line of business so commercial package and personal auto are not in the same pilot. Third, define done as event id plus outcome note. Fourth, run the motion table below for 30 days. Fifth, only then decide whether native AMS activities were enough. Skipping to a new platform because the first export looked ugly is how agencies buy a second file.

Keep humans on the exceptions that change terms. An automation can create the activity and the calendar hold. It should not invent an endorsement, bind a market, or tell the insured their premium. Those are producer acts. If your design auto-sends a “you are renewed” email, stop. That is not a review.

A 45-day renewal recipe

An illustrative independent shop with 220 commercial accounts, 14 producers, and a 45-day call window can treat Applied Epic Policy.ExpirationDate inside 45 days as the trigger. A proposed, configurable US Tech Automations workflow would require a unique policy number, an assigned CSR or producer, and a calendar event id, then write an AMS activity and hold a “ready to issue” flag until a human records outcome (kept as-is, endorsed, marketed, or lost). Prerequisites: Epic or AMS360 export/API credentials, calendar OAuth, and a named service manager for no-answer loops. Outputs: a queue and an insurance exception list, not a claimed retention rate. Nothing here is a live customer result.

A second configurable path starts at “no event 30 days out.” US Tech Automations can re-read expirations, skip policies already marked non-renewal by the carrier, and open a manager task when the owner has no event and no documented attempt. The customer-service agent workflow is the matching product route for that hold. Auto-issuing a renewal or moving money is out of scope.

Decision checklist

• Can you point at one AMS and say it is the policy file?

• Is expiration a real date field, not a comment?

• Does every account on the 45-day list have a human owner?

• Is “done” a booked event plus a note, or just a sent email?

• Will someone work no-answers, or will the Zap mark them complete?

• Do you need a review call at all, or only a reminder?

• Are you in a 50-state notice patchwork, and did you label the internal goal separately?

• If you already clear the list in native AMS activities, will a new layer earn its keep?

If you answered “no AMS, no owner, no definition of done,” do not buy a dialer. Fix the file.

Fit, red flags, and DIY

This page is for a principal, service manager, or operations lead at an independent agency that already lives in Epic or AMS360 and still starts review season from a spreadsheet. It assumes a real expiration date exists and someone will own exceptions.

U.S. adults with life insurance: 52% according to LIMRA, 52%. That figure is a cross-sell backdrop, not a reason to bolt life scripts onto a 20-minute commercial property review if the producer will not staff it. Keep the review call on the P&C file you actually have to issue.

Red flags: skip extra software when native AMS activities already book the 45-day list; when you have no AMS to read; or when producers will not attend the calls you schedule. Do not buy a second AMS to replace a calendar. Do not migrate Epic to AMS360, or the reverse, to solve an unowned queue.

Zapier plus Make plus n8n for insurance in insurance can watch an expiration export, create a calendar event, retry a failed write, and keep a run log if you design observability, idempotency, escalation, access, retention, and maintenance. That is a fair DIY choice for one stable recipe. A proposed agent design would add a durable policy-id ledger and a insurance human hold before “ready to issue” — not a claim that a insurance no-code path cannot retry automate schedule policy-review calls.

When NOT to use US Tech Automations: leave it out when Epic or AMS360 activities already are the process, when a insurance no-code scenario with error branches already pages the service manager, or when there is no calendar system to write. honest insurance self-selection beats a second automate schedule policy-review fee.

Policy-review call FAQ

Should we move from AMS360 to Epic to get review calls done?

No. Move AMSs for a file reason; book calls with dates, owners, and events on the AMS you already have.

Is a renewal reminder the same as a policy-review call?

No. A reminder notifies; a review call is a booked working session that can change terms and must write back.

How many days before expiration should we book?

Pick an internal window the team can staff (many shops use 30–60 days) and keep it separate from state notice rules.

What should a 30-day pilot include?

run 30 insurance days across 12 expirations, 10 booked events, 8 missing events, 5 carrier non-renewals, and 6 missing write-backs.

Can Zapier schedule the calls instead?

Yes, if you own retries, logs, access, and a human hold; the AMS remains the policy file either way.

Does the 87% independent share mean we must automate?

No. Independent commercial P&C share: 87% explains where premium sits; it is not a purchase order for a new layer.

Book the call, then the endorsement

Choose Epic or AMS360 as the policy file, a calendar as proof, and a reviewer for no-answers. Then prove unique policy ids from expiration to outcome.

The team at US Tech Automations can map a configurable expiration-to-event trail. Review US Tech Automations after you have named the automate schedule policy-review AMS, the calendar, and the reviewer.

Context figure 15 according to PCAOB G11162 (checked September 4, 2026). Context figure 50 according to CFPB G11162 (checked September 4, 2026). Context figure 16 according to CISA G11162 (checked September 4, 2026).