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

A regional life insurer serves its policyholders through a 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 the insurer 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.

Intake, Broker Routing, and Reports Done by Hand

Customer intake was the first problem. The Life division had many policyholders sending in documents, most of them once, and it wanted one branded path for that paperwork instead of a sender account for each. Broker files needed hand-routing: someone checked each enrollment file's formatting and then got it to the administrator that processes it. The division wanted recurring reports to go out because a schedule said so, with the end-of-month report leaving on the same day every month without anyone carrying it.

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

Every one of those exchanges moved sensitive data, and the division wanted all of it on one governed path under the insurer's name.

Senders Who Couldn't Be Provisioned, a Destination the Insurer Didn't Control

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 the insurer'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 a one-time 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 the insurer's name on all of it. Recurring reports had to go out on a schedule. The insurer 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 the insurer'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 the insurer's own custom domain with single sign-on through Microsoft Entra ID, so staff now reach it with the credentials they already have.

What No Longer Depends on a Person

With the workflow in production, the Life division runs its external exchange as 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 nothing downstream waits on a hand-off.
• 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 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

The insurer 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 runs on its own, and the division spends its attention on the insurance, not the carrying.