Frequently askedquestions
Find answers about how PolicyLantern works, setup, security, and pricing — plus plain-English explanations of common insurance terms your team encounters every day.
About PolicyLantern
Does PolicyLantern replace my AMS?
No - PolicyLantern works alongside existing systems (EZLynx, HawkSoft, NowCerts). It fills the real-time monitoring gap. PolicyLantern detects status changes the same day they appear in the portal. No data migration, no workflow disruption.
What does PolicyLantern do, in plain English?
We catch pending cancellations across all your carriers before they cost you a renewal. PolicyLantern is a cancellation detection system for independent agencies — it runs through a Chrome extension that quietly monitors your carrier portals as your team uses them, then surfaces every pending cancellation in one dashboard and emails the right person the moment a policy is at risk.
How does it work with my carrier portals?
Your team logs into carrier portals exactly the way they do today. The Chrome extension reads what's already on screen and pulls policy and status data into a unified dashboard. Because detection happens at the page level, we can flag pending cancellations even on carrier portals that have no built-in search, filter, or report for those statuses.
How does pricing work - and is there a guarantee?
Yes. We back every plan with a 7.5x Return Protection Guarantee: if the savings identified in your first 90 days don't reach at least 7.5× your subscription cost, you don't pay for that quarter. For a typical 1,000-policy book on the basic plan, catching roughly one policy per month clears the threshold.
Will this add complexity to our workflow?
The opposite - we're built to replace complexity. Instead of logging into dozens of portals, stitching together emails and CSVs, and hoping nothing slips through, your team works from one dashboard with real-time alerts and pre-written Save-the-Policy scripts.
How does PolicyLantern help my team respond to cancellations?
When a policy hits pending cancellation, the responsible team member gets an alert with the policy details and ready-to-use phone, text, and email scripts - matched to the cancellation reason (non-payment, underwriting, client-requested, and so on). Outreach stays fast, consistent, and professional no matter who handles it.
How are alerts routed to the right people?
Through Agency-Wide Team Access with Smart Alert Routing. Each alert goes to the person or role responsible for acting on it - for example, account managers for service follow-up - so producers stay focused on selling instead of hunting through portals.
Why did ASNOA endorse PolicyLantern?
ASNOA endorsed PolicyLantern for partner agencies because it provides a system - not just a person - for catching cancellations: detection where portals fall short, routing that gets alerts to the right team member, and fast, consistent responses within the typical 30-day window before lapse.
Is my carrier login data safe?
Yes. We never store your carrier logins or passwords on our servers — credentials stay encrypted in your own browser, and your team keeps signing in exactly the way it does today. The extension is built on Manifest V3, Google's current extension standard, and all traffic between the extension and your dashboard is encrypted in transit.
Which carriers are currently supported?
The current list lives on our Supported Carriers page, and it keeps growing — we add carriers based on what agencies actually ask for. Because detection happens on the portal page itself, adding a carrier does not require that carrier to build anything for us. If one you rely on is missing, tell us and we will look at it.
What if some of my carriers don't show pending cancellations in their portals?
That is the gap we were built for. Detection happens at the page level — the extension reads the policy and status data already on screen — so we can flag pending cancellations even on portals that offer no search, filter, or report for those statuses. You do not need the carrier to expose a list we can query.
Can my whole team use PolicyLantern?
Yes. Agency-Wide Team Access puts your team on one dashboard, and Smart Alert Routing sends each alert to the person or role responsible for acting on it — account managers for service follow-up, for example — so producers stay focused on selling. Nobody has to share a login or forward emails to the right colleague.
Do we need IT, APIs, or custom integrations?
No. There are no APIs to negotiate and no custom integrations to build or maintain. Your carriers stay exactly where they are, and PolicyLantern layers monitoring on top of the workflows your team already knows.
How fast can we get up and running?
Most agencies see pending cancellations in their dashboard during the first session. We include a 30-minute White-Glove Carrier Setup where we configure your carrier mix, alert cadence, and routing rules - so your team is ready on day one.
What kind of results do agencies see?
Results depend on book size and carrier mix. As one example, Family First Insurance loaded over 5,000 policies into PolicyLantern, identified 115 pending cancellations, and protected an estimated $37,375 in commission in their first 90 days. Our built-in Revenue Protection Tracker quantifies your savings automatically over time.
We have multiple locations. Can PolicyLantern work across all of them?
Yes. Monitoring follows your carrier portals rather than your offices, so every location your team logs into is covered from the same dashboard. Smart Alert Routing is what keeps that manageable at scale: each alert goes to the team member who owns the policy rather than into one shared inbox.
Does it work for solo agents, or only large agencies?
Both. A saved policy is typically worth $500 – $2,000 in annual commission, so catching a single cancellation can cover a year of the subscription — the case for monitoring does not depend on book size. Solo agents often feel the manual checking most, because there is nobody else to hand a portal to.
I have 5,000+ policies. Can PolicyLantern handle that volume?
Yes. Family First Insurance loaded over 5,000 policies, identified 115 pending cancellations, and protected an estimated $37,375 in commission in their first 90 days. Plans are tiered by how many policies you monitor, and books beyond the largest tier are quoted individually — talk to us and we will size it with you.
What is the Save-the-Policy Playbook?
It is the response side of the product. When a policy goes pending, the alert arrives with ready-to-use phone, text, and email scripts matched to the cancellation reason — non-payment, underwriting, client-requested, and so on — so whoever picks it up acts fast and sounds consistent, inside the roughly 30-day window before the policy lapses.
How are savings calculated?
The built-in Revenue Protection Tracker quantifies it for you over time: it counts the pending cancellations you caught and values them against the commission that was at risk, typically $500 – $2,000 per saved policy per year. You see what the monitoring returned rather than having to estimate it.
We already have a process for catching cancellations. Why would we change?
Most processes lean on carrier downloads and manual portal checks. Downloads arrive three to seven days late, and many portals cannot list pending cancellations at all — so what fails is usually not effort, it is timing and visibility. PolicyLantern detects status changes the same day they appear in the portal, and agencies report eliminating 10+ hours of manual checks every week.
What about using VAs instead of PolicyLantern?
A VA can check portals; what no person can do is watch every portal continuously and never miss the day a status flips. PolicyLantern is a system rather than a person — detection where portals fall short, routing that gets each alert to the right team member, and scripts that keep the response consistent. Many agencies keep their VA and point them at one dashboard instead of a dozen logins.
What if I want to build something custom instead?
There is nothing to integrate against. Carriers do not expose APIs for pending cancellations, which is why detection has to happen on the portal page — and that page is what changes as carriers update their portals. With PolicyLantern that maintenance is ours: no APIs to negotiate, no integrations to build, and nothing for your team to keep running.
Still have questions?
Here is what happens when agencies stop relying on manual checks and start using PolicyLantern.