Tellabs Tracks Every Firmware Download Through Files.com Without Making Customers Log In

Tellabs makes fiber-based Optical LAN equipment and the software that runs it. It sells predominantly through channel partners into government, education, healthcare, and hospitality networks across North America.

That model puts the people who ultimately download its software across an installed base the company reaches at arm’s length. Distributing software to those customers is standing work for Tellabs, and it was work the company was doing blind.

Software Went Out With No Record of Who Took It

As of mid-2024, Tellabs ran file transfer on an in-house system it had built itself, and software distribution ran through it with no accountability at all. Tellabs could not tell who had downloaded which software versions. For a manufacturer whose product is half software, that was a standing cost: a release went out to the installed base, and Tellabs learned nothing. It had no way to connect a version to the customers who had taken it, and no way to reach a downloader when an update or new release notes followed.

The gap survived because the obvious fix was worse. The standard way to make downloads accountable is to gate them behind accounts and make every customer log in for every file. Tellabs’ engineering leadership explicitly did not want that. The point of knowing who took a file was for the customer’s benefit, so Tellabs could tell them when an update or new release notes existed, and a login wall would tax exactly the people the record was meant to serve.

The requirement was distribution that stayed as easy as a public download but left a real record behind it. The link had to work in any browser with no account and nothing to install. The record also had to land in the systems where Tellabs’ customer data already lived, not in a transfer tool off to the side. Tellabs selected Files.com to be that distribution layer.

A Branded Link in Front, an Event Feed Behind

Tellabs put Files.com in front of software distribution using Files.com share links under Tellabs’ own domain. On the customer’s side, nothing is asked of them: they follow a link on a Tellabs address, and the file downloads in the browser, with no account to create and nothing to install.

Files.com records each download as an event and sends it through its external events endpoint into Nexus, Tellabs’ existing customer and vendor portal. Nexus is backed by a data warehouse connected to Tellabs’ CRM and NetSuite ERP, so the file-level activity arrives in the system where Tellabs already manages customer context. Tellabs did not have to build a new portal or move its customer data anywhere. It instrumented the distribution channel and fed the systems it already had.

Every Release Now Leaves a Record

Each release published through the Files.com channel now produces a continuing record of download activity in Nexus while customers keep the same no-login browser path. Where software distribution once told Tellabs nothing, the record now accrues with every release.

The Record Comes From the Channel, Not the Customer

Files.com supplies the record as a byproduct of moving the file, and Tellabs’ own portal keeps that activity next to its existing customer data. Today, a customer pulls a Tellabs release the way they would pull any public file, with a click in a browser, and Tellabs receives the download event.

The download did not get harder. It stopped being invisible.