Xect AI geocodes today's calls and open service tickets to their hub within seconds of landing, normalizes activity per 100 active customers, and tracks call reasons trending through the day. A hub crossing its configured threshold is flagged as a suspected outage before the NOC alarm; the Correlation Agent checks NOC alarms, modeled anomalies and maintenance records before confirming it.
Call volume is reviewed by queue the next morning; ticket clusters are noticed after the third truck goes out. Xect AI geocodes every call and ticket to its hub within seconds, normalizes per 100 active customers, and flags the hub that crosses its configured threshold as a suspected outage, for Care and Technical Support on the same screen.
Each call and ticket resolves to an address and its hub within seconds of landing; call reason attaches from the IVR or the transcript.
Calls per 100 and tickets per 100 active customers, per hub, rolling through the day; thresholds 17 and 1.1.
Hot hubs are checked against NOC alarms, modeled anomalies, planned maintenance and utility outages.
Outage customer actions, NOC ticket, care banner and IVR message run from one flow; calls are tracked until the hub cools.
Each agent owns one step from the first ring to the contained outage, and hands its output straight to the next.
Plots every call within seconds of it landing.
Resolves each inbound call and chat session to a service address and its hub the moment it lands, and attaches the call reason from the IVR menu or a live transcript pass.
Knows 17 per 100 from 17 calls.
Divides each hub's rolling call and ticket counts by its active customer base, so a small hub with a real spike looks exactly as urgent as it is, no more and no less.
Turns a hot hub into an answer.
Checks a hot hub against NOC alarms, modeled anomalies, planned maintenance and utility outage feeds before flagging it as a suspected outage or standing it down as a coincidence, then opens the flow that acts on that finding.
A hub crossing its configured threshold is flagged for investigation while the calls are still arriving.
Clusters show on the map as they form, not in Friday's export.
Billing, care, account, management review, changes and transfers to Technical Service, each on its own line.
Care calls and trouble tickets share hubs, thresholds and actions.
Customers already told you where to look. Xect AI plots it within seconds.
When a hub passes its configured calls threshold at 9:40, the suspected-outage flow starts before the alarm storm.
See the industry pageWhen outage calls cluster on one feeder, the map confirms the area before the crew is dispatched.
Talk to us about utilitiesWhen claim calls spike by ZIP after a storm, CAT teams see the footprint by the hour.
Talk to us about insuranceWhen portal and scheduling calls climb at one clinic, IT checks that site's integration first.
Talk to us about healthcareWhen "where is my package" calls cluster on one depot's routes, the depot is called before the customers are.
Talk to us about logisticsOwns the Care queue's service levels, and needs to see which hub is generating the volume before it shows up as a queue-wide backlog.
Owns network incident response, and needs the customer-visible signal, not just the device alarm, to confirm an outage is real.
Owns the truck-roll budget, and needs to see which tickets share a cause before dispatching a crew to each one separately.
Owns every hub in the region, and needs one ranked view of what is happening now against what happened last week.
What runs the moment a hub is confirmed hot: notifications, credits and the care banner.
The shared address and hub context this map runs on. Location Intelligence keeps that record current; this page is the live, in-the-moment response view built on top of it.
Book a 30-minute demo and watch today's calls and tickets land on your hubs, live.