Carriers

Carrier matrix: what is built today

LegacyCore is the Final Expense Agency Operating System. This page shows what it can do in each carrier portal today. Every other carrier is set up during implementation.

The matrix

What is built for each carrier

Two capabilities, carrier by carrier. Your agency's access to each portal is confirmed during setup.

Last updated

American AmicableAmerican Amicable

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Set up during implementationAfter your written authorization for that portal.

AmericoAmerico

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Run in productionYour own access is confirmed during setup.

CorebridgeCorebridge

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Set up during implementationAfter your written authorization for that portal.

EthosEthos

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Set up during implementationAfter your written authorization for that portal.

Mutual of OmahaMutual of Omaha

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Run in productionYour own access is confirmed during setup.

TransamericaTransamerica

Application map
BuiltConfirmed for your agency during implementation.
Policy status sync
Run in productionYour own access is confirmed during setup.

Any other carrier your agency writes

Both capabilities are set up during implementation, after your written authorization for that portal.

Carrier names identify carriers the software works with. Their appearance does not imply endorsement by, or affiliation with, the carrier. We don't claim any carrier has approved or endorsed the Portal Worker.

Reading the matrix

What each label means

Built

The application map ships in the Portal Worker kit. It names the carrier portal pages and the fields the worker may fill. We confirm each map for your agency during implementation, on a supervised run.

Run in production

LegacyCore has already read policy status from this carrier's portal in production. Each read runs as a dry run first, and an incomplete read changes nothing. Your own access is confirmed during setup.

Set up during implementation

This capability is not built for this carrier yet. It is set up during the done-for-you implementation, after your written authorization for that portal. Supported carriers carry no per-carrier fee.

Portal Worker

The agent stays in control of every application

  • Portal Worker runs in the agent's own Chrome, on the agent's own computer, signed in with the agent's own carrier login.
  • It fills the pages its map names and stops before Submit. The agent reviews, signs and presses Submit.
  • A captcha, a lockout or a page it does not recognise stops the run, and the agent sees the reason.

How Portal Worker accesses carrier portals

Your carriers

Writing with a carrier not listed here?

Book a demo. We confirm your carriers and the access your agency authorizes, then set them up during implementation.