Skip to main content

AFR Life Gives Policyholders a No-Account Upload Link and Automates Broker File Delivery With Files.com

Policyholder and broker files now move through Life-team review to an external administrator without individual sender accounts or manual delivery.
American Farmers & Ranchers Life Insurance CompanyFiles.com

American Farmers & Ranchers Life Insurance Company, known as AFR Life, is an Oklahoma City life insurer within the American Farmers & Ranchers group. It serves farmers, ranchers, and rural families across Oklahoma through a statewide network of independent agents.

Almost none of that work happens inside the company's own walls. Policies move through independent agents and brokerages. The enrollment and member-change files those brokers send are processed by a third-party administrator. Policyholders themselves send in policy-change forms and supporting documents. Nearly every step is a file crossing between AFR Life and someone it does not employ, and those files carry personal and policy data. Files.com now connects no-account uploads, the Life team's review, and automated delivery to the external administrator.

Files That Moved on Memory and Hand-Offs

Customer intake was manual and awkward. The Life division had a lot of customers trying to send in documents, and the path they had was clunky: sensitive paperwork arriving however each customer could manage to send it, handled ad hoc on the other end. Broker files needed hand-routing. Someone had to check each enrollment file's formatting and then get it to the administrator that processes it. Recurring reports depended on a person remembering: an end-of-month report went out only if someone thought to send it, and when they forgot, everything downstream waited.

And when a file had to move urgently, the business team could not move it alone.

You need to hurry, but you have to get IT involved and do all these things.
Brandice Rhoades, Vice President, AFR Life

Every one of those exchanges moved sensitive data, and every ad hoc path was one more thing the team had to secure by hand.

Senders Who Couldn't Be Provisioned, a Destination AFR Life Didn't Control

The problem had survived because the counterparties didn't fit the standard fixes. A policyholder submitted documents occasionally, sometimes once. Creating an account and a folder for every customer would never scale, and the Life team's requirement was explicit: a link customers could use to drop documents securely, with no individual folder set up per customer. Brokers were independent businesses, not employees. And the destination on the far end was not AFR's at all. The third-party administrator picked files up from its own external SFTP folder, on its own terms.

The fix had to serve an unsophisticated sender with no account on one side and an automated machine hand-off on the other, with the Life team's review in the middle and AFR's name on all of it. Recurring reports had to go out because a schedule said so, not because a person remembered. AFR Life selected Files.com to be that exchange layer.

A Branded Front Door, With Automation Behind It

Files.com became the Life division's single exchange layer: one branded front door for everything coming in, and automation for everything going out.

Intake ran through Files.com Inboxes. The division sent policyholders and brokerages a branded link on AFR's own domain. The sender opened the page, filled in a short form, and dropped their documents. There was no account to create, nothing to install, and no folder provisioned per customer. Each submission landed in a folder the Life team controlled and triggered an email notification to a shared team address, so nothing sat unseen.

The broker pipeline worked the same way with a review step in the middle. Brokers uploaded enrollment and member-change files into a folder structure scoped by group permissions. A Files.com Automation renamed each upload to identify which broker sent it, so a reviewer always knew whose file they were checking. Once the Life team had reviewed the formatting, Files.com pushed the file automatically to the administrator's external SFTP folder. People do the judging; the platform does the carrying.

Recurring distribution ran on Automations too. The daily policy report moved into the leadership folder on its own, and month-end files were copied into date-stamped subfolders so each month's copy was preserved and nothing was overwritten.

Internally, the site was set up on AFR's own custom domain with single sign-on through Microsoft Entra ID, so staff now reach it with the credentials they already have.

We go to our favorite, we single sign on, and we're in.
Mandy Coulter, Director of the Life Division, AFR Life

What No Longer Depends on a Person

With the workflow in production, the Life division replaced an exchange built on memory and hand-offs with a standing, repeatable pattern.

  • Any policyholder or brokerage can submit sensitive documents through one branded link, with no account and no per-customer setup. The same link serves every sender.
  • Broker enrollment files reach the third-party administrator with nobody hand-carrying them: identified by sender, reviewed once, delivered over SFTP automatically.
  • Daily and month-end reports distribute themselves on schedule, so a forgotten report can no longer delay the work downstream.
  • Moving a file to an outside party no longer starts with getting IT involved. The Life team works from the browser, behind single sign-on.

The vice president puts the whole of it in business terms:

You get end-of-month reports, and you forgot to send it to somebody who needed it, and then it delayed everything. So this automatically does all of that work for us, so there's no single point of failure.
Brandice Rhoades, Vice President, AFR Life

The pattern also compounds. Bringing on another broker means a folder and permissions inside a structure that already exists. A new policyholder needs nothing set up at all; the same link serves everyone.

One Layer Between the Life Division and Everyone Outside It

AFR Life never had to provision its counterparties to get there. It gave them a branded front door and put Files.com automation behind it: external file exchange does not require an account for every sender. The exchange that used to run on memory now runs on its own, and the division spends its attention on the insurance, not the carrying.