A Photonics Manufacturer Replaced Zipped Email Attachments With Files.com Inboxes Tied to Salesforce Cases in Days

A global photonics manufacturer makes engineered materials, optoelectronic components, and laser systems for the industrial, communications, electronics, and instrumentation markets, with operations in dozens of countries.

Its lasers and instruments run inside other companies' factories, labs, and networks. An installed base of thousands of systems in the field is supported by hundreds of field engineers, and when one of those systems needs attention, the diagnosis starts with a file: the customer bundles up log data and sends it back to the manufacturer. A business built on a global installed base was always going to live or die by how well those files get home.

The Standard Intake Was a Zip File in an Email

For years, the instruction to customers was simple: zip the log files so they clear the mail filters, and email them to your field engineer.

That habit carried a lot of traffic. In a single two-month window, a thousand distinct external sender domains emailed zip files into the company. And it carried real costs. Each file landed in one engineer's personal mailbox, separate from the support case it belonged to. Anything larger than the mail system's attachment cap could not be sent at all, and diagnostic bundles are often exactly that large. The company wanted one governed intake path for those files: filed against the case on arrival, with no size ceiling.

Then security policy retired the old route. The company blocked zip attachments in external inbound mail company-wide. The global service organization needed a new intake path for customer files, and it needed one in days.

A Replacement for Senders Who Would Never Have Accounts

The replacement had a hard shape. The senders were customers: thousands of organizations, sending occasionally, always in connection with a specific ticket. They could not be pre-provisioned as accounts, and they could not be asked to install anything. Each file had to land tied to the support case it belonged to, not in an undifferentiated pile, because support automation runs downstream of the intake. And it had to be live in days, because the policy was already in force.

The company's IT infrastructure team knew the shape of the answer from the other side of the relationship: its own vendors handed out a temporary drop point per ticket. What the team wanted was that pattern as a permanent, branded channel of its own, running under the company's name rather than improvised one ticket at a time. The company built it on Files.com, the platform that already carried its automated file exchange with suppliers and contract manufacturers.

An Upload Page Tied to Every Support Ticket

A Files.com Inbox is a standing, branded upload page that accepts files from people who have no account. The team attached a custom registration form that captured the support case number and thread ID and pre-filled it: the link a customer received carried the ticket's parameters in the URL, so the customer clicked, confirmed, and uploaded.

Files.com automatically created a subfolder for each submission from the form fields, so every inbound file landed in a folder named for the Salesforce support ticket it belonged to, and the company's downstream support automation used that folder name to route it. The intake was stood up immediately after the block took effect.

The Mandate Held and the Files Kept Coming

With the Inbox workflow in production, the manufacturer replaced an intake channel built on email attachments with a governed upload path wired into its support system.

• The service organization kept receiving customer files. The new intake path was in production within days of the policy change.
• Every inbound file arrives already filed. It lands in a folder named for its case and thread, where automation picks it up. No engineer pulls attachments out of a mailbox and sorts them by hand.
• The size ceiling is gone. Log bundles that could never fit through email go through the same page as everything else.
• The channel is governed. Every registration and upload is recorded, and the exchange runs under the company's name on storage its IT team controls, instead of across a thousand senders' email threads.

The immediate result was continuity. The standing result is the pattern: external file intake now has one governed front door instead of a thousand mailbox destinations, and putting another workflow behind it means another Files.com Inbox with its own form, not another exception to the security policy.

One Governed Front Door for Customer Files

Today, a customer with an instrument that needs attention gets a link tied to their ticket, and the log bundle arrives on a company-branded page, filed against the case before an engineer ever touches it. The temporary per-ticket drop that the company's own vendors used to hand out now exists as the company's permanent, owned channel, on its Files.com site, with a record of everything that passes through.

The ban on zip attachments held, and the service organization kept its files coming. A company can shut the door on email attachments without shutting out its customers, provided the files have somewhere better to go: a front door that already knows which case every file belongs to.