Xect AI is location intelligence for network operators: every serviceable address carries live status, neighbor activation and hub health, from service-area polygon to street level, so sales, care and network teams read the same map.
Serviceability sits in GIS, customers in billing, calls and tickets in their own tools. Fragmented records limit a shared view of location performance. Xect AI combines serviceability, customer activity, and operational indicators by address and network area, giving planning, sales, and service teams a common view to investigate performance and prioritize follow-up.
Service-area and hub polygons, addresses, drop status and type, optical network terminal (ONT) activation, and ready-for-service (RFS) date — the physical truth.
Active customers, neighbor status, calls, trouble tickets, outages and speed tests land on each address as they happen.
Hub metrics for the last 24 hours, normalized per 100 active customers, describe current hub condition. The Location Score per address is a separate prediction, the same score used on the Customer Propensity Model page.
Fallout to network, prospects to sales, hub context to care and the Live Operations Map.
Each agent owns one step in the map-to-action path above and hands off cleanly to the next.
Keeps polygons and addresses current
Pulls service-area and hub polygons from GIS and normalizes every address against the local reference file. Drop, ONT and RFS-date attributes update as construction and activation events land.
Computes the last 24 hours per 100
Rolls up active customers, calls and new and open tickets for each hub over a rolling 24-hour window, then normalizes every count per 100 active customers. Thresholds vary by hub type, so a small hub and a large hub are graded on the same curve.
Finds the built hub that isn't selling or isn't working
Flags connections that are live but not yet activated, and installs that missed the RFS date, then opens a network or sales task instead of waiting for the quarterly review to notice.
Turns the map into a route
Builds the door-to-door list from neighbor activation and prospect score, applies consent and do-not-knock rules, then writes canvass results back to the map.
Drop, ONT, neighbor status, hub troubles per 100 active customers, RFS date, address checks, penetration, Location Score.
Calls, tickets and their rates per 100 active customers, for any hub, without a report request.
Connections with power but no customer activation show up as a cluster, not a line item.
Canvass where the neighbor already activated and the address checked availability online last week.
Fragmented records limit a shared view of location performance. One address, one record, one view.
When a new hub reaches RFS, the map shows which streets activated and which connections lost service.
See the industry pageWhen a node's tickets per 100 climb, the map points to the street before the truck roll pattern does.
Talk to us about cable & MSOWhen a feeder's outage calls cluster, the map shows the affected premises and the meter status.
Talk to us about utilitiesWhen new connections lag a completed main, the map shows the unconnected addresses.
Talk to us about water & gasWhen take-rate stalls in one district, the map shows the addresses that checked availability and never ordered.
Talk to us about municipal broadbandOwns hub performance after RFS, and needs fallout, tickets and penetration on one map instead of three reports.
Owns the door-to-door motion, and needs the ranked route drawn from the same dots as the rest of the business.
Owns queue quality, and needs hub state in the rep's banner before the customer explains it.
Owns the build handoff, and needs to know which activated connections never turned into customers.
Book a 30-minute demo and see your service area, your hubs and your last 24 hours on one map.