Broadband providers do not lose subscribers because the network is bad. They lose them in the gap between the day an address becomes serviceable and the day somebody is actually installed and billing — and that gap is almost always a data problem, not a fiber problem.
Most providers already know where they are building. What they do not have is one place where an address, its serviceability status, the interest somebody registered against it, the work orders it takes to light it up and the bill that follows all live together. So that knowledge sits in a construction spreadsheet, a marketing list, a dispatch board and a billing system that do not agree with each other — and the people doing the work spend their day reconciling instead of selling and installing.
We make the address a first-class record in Salesforce and hang everything else off it. Serviceable, under construction, near-net, not yet planned — plus whether you are overbuilding an incumbent — stops being a question somebody answers by walking over to the network team.
We do not start with software. We start with the path an address takes from planned to paying, and we close the handoffs where subscribers and revenue leak out.
Beyond phase one
Drawn from fiber and fixed-wireless delivery work. None of it was on the original requirements list.
Every provider accumulates people who asked for service at an address that was not live yet. In most shops, turning an area up means a dispatcher works a months-old list by phone to find out who still wants it. Hold the interest against the address instead and the backlog converts itself the day the area goes serviceable.
Serviceable, under construction, near-net, not yet planned. If the website, the rep on the phone and the marketing team can each give a different answer to the same address, you will eventually sell service you cannot install. Make the address the record and the status the field, and the question has one answer everywhere.
A fiber install is almost never one job. The drop and the in-home work are different crews on different days, often different contracts. Track them as a single job and complete stops meaning complete, which is how billing starts late and a customer waits twice.
A hundred subscribers calling about one cut is a hundred tickets that nobody can roll up. Make the event the record and link the affected subscribers to it, and support answers the question the customer is actually asking while you can still see what the incident cost you in churn.
Whether you are the only option at an address or the second one changes the offer, the churn risk and the install economics. Almost nobody carries it as data. It belongs on the address alongside serviceability, because it is the field that makes a campaign list worth something.
Inventory, billing and construction each have their own tooling and should keep it. Below, what we do at each connection.
Where serviceability actually lives: what is built, what is planned, what is lit.
VETRO IQGeo 3-GIS
Subscriber plans, proration and the invoice a customer will argue with you about.
Revenue Cloud (CPQ) NetSuite Sonar
Standardized addresses and the map layer every other system quietly depends on.
Esri ArcGIS Google Maps Platform Smarty
Crews, trucks, drops and in-home work orders against a live schedule.
Salesforce Field Service Samsara ServiceMax
Campaigns that can tell a serviceable address from one that is still a promise.
Account Engagement (Pardot) Marketing Cloud HubSpot
Outages, truck rolls and escalations in one place rather than three queues.
Service Cloud Jira Service Management Zendesk
Tell us where addresses, pre-sales, installs and invoices stop agreeing with each other. That conversation is usually enough to show what is worth fixing first.
