Close
AI Closer
In beta: an AI voice agent that works final expense leads and warm-transfers qualified callers to a licensed agent. Every call opens with a clear AI disclosure.
Beta
Documentation
The manual
What each part of the AI Final Expense Operating System does, where it sits, and how agencies interact with it. New surfaces ship to this page as features stabilize.
Getting started
LegacyCore is the AI Final Expense Operating System: one system that closes, submits, monitors, and keeps final expense policies on the books across a whole downline, with compliance underneath every step. It is built for agency owners, managers, and agents running final expense business across multiple carriers.
The six modules
Six modules follow the life of a policy, from the first conversation to the day it is still in force a year later.
Submit
Portal Worker Submission
Pre-fills and submits applications through authorized carrier portals. When needed, an agent can move to the next carrier without re-entering the details. Checks status on a schedule and sends a daily reminder for outstanding work. Access and workflows are confirmed during setup.
Live
Monitor
Book Health
A scheduled worker checks every connected carrier portal for lapse signals, missed payments, and pending requirements, reconciles carrier status against the agency's own book, and ranks the result by at-risk premium in a weekly report. It sits alongside a spreadsheet, CRM, or AMS and does not replace a CRM or AMS.
Live
Retain
Conservation AI
Follows up with clients about missed payments and policies at risk of lapsing. Each contact is recorded so the agency can review the follow-up.
Live
Underneath
Compliance Engine
TCPA and Do-Not-Call screening that blocks outbound calls when it cannot verify a number, an AI disclosure at the start of every AI call, and an audit log of every portal pull and status change that can be handed to compliance without editing it first.
Live
Oversight
Downline Command
One product, three role-scoped views on the same book: an agent sees their own book, a manager toggles through their team, an admin toggles through every manager across the agency.
Live
Book Health: the four pillars
- Monitoring, not selling: Book Health watches carrier portals and reconciles status. On its own it doesn't contact your clients and it doesn't replace your CRM or AMS: it sits alongside whatever you already use to track your book.
- Written-authorization credential model: Every carrier connection requires written authorization before it happens. Credentials never leave the monitored worker flow.
- Role-scoped, not one-size-fits-all: An agent sees their own book. A manager toggles through their team. An admin toggles through every manager. Nobody sees more than their role should.
- Priced by what it protects: Standard scales per agent beyond 10, because a larger downline carries proportionally more at-risk premium to monitor.
What you'll find in this manual
Each section below covers one slice of the system at the level appropriate for public documentation. Internal implementation details (worker infrastructure, carrier-portal automation specifics, security architecture) are not published here.
- How the scheduled worker checks carrier portals
- How a weekly report gets built and ranked
- Security controls that gate every carrier connection
- The public API surface for integrators
Inside Book Health: five capabilities
The Book Health module does five distinct things, each owning a slice of the monitoring lifecycle — from first carrier connection to the report that lands in an upline's inbox.
Portal Monitoring
A scheduled worker checks every connected carrier portal for lapse signals, missed payments, and pending requirements — daily, weekly, or hourly.
Reconcile Mode
Matches what each carrier says against what your own book of record says, and flags every mismatch, agent by agent.
Weekly Report
A single ranked report — by at-risk premium, not raw policy count — built to hand to an upline or a downline agent.
Audit Trail
Every portal pull and every status change is written to a log you can hand to compliance without editing it first.
Role-Based Views
One product, three views on the same book — agent, manager, and admin each see the right slice, automatically.
Talk to a human
Still stuck on something?
Open a support ticket. We reply within one business day — usually faster.