An outage is a map problem before it is a PR problem
Subscribers do not open a ticket — they post “no signal” under your last ad, in their own language, from a specific district. Scano collects those posts across nine networks, groups them into the outage they actually describe, tells you which region is lighting up, and puts every one of them in a queue with an owner.
Personalised demo · Live on your own topics · One queue across nine networks
Minutes
from first complaint to an alert with a region on it
9
networks in one queue, with owners and deadlines
24/7
monitoring, so a 2 a.m. outage is not found at 9 a.m.
From “something is wrong” to “answered”
Detect it, group it, route it — then measure how long the answer took.
Theme setupliveTracknova"nova refill"@novahqNever matchnova scotiasupernovachevy novaExclusions are where the noise actually dies.Automation ruleruns on arrivalIFtext contains "refund"ANDsentiment = negativeTHENtag: billingassign: Customer Care1 284mentions filed automatically this weeksample dataSourcesSocial · 9 networksNews & webBlogs & forumsor paste your own list
Themes, not a pile of keywords
Posts about the same outage arrive in four languages and a dozen spellings. Scano groups them into one theme, so the spike you see is the incident rather than the search term.
Themes built from your own keyword sets, with stemming per language
Volume and sentiment tracked per theme, against its own baseline
New sub-topics surfaced as subscribers invent new words for the problem
Inbox128 open9 networksMWXOrder stuck for 3 daysx.com · 9:04 AMnewPSWhere's my receipt?instagram · 8:51 AMassignedJRRefill station workedtelegram · 8:22 AMresolvedALCard declined twiceyoutube · 8:05 AMnewMWXMarcus Webbx.com · direct messageSLA 2hOrder hasn't moved in three days andsupport keeps saying it shipped.9:04 AMMarcus — checked it: carrier scan failed,new label is out, arriving Thursday.9:21 AM · Dana, Customer Caretemplate: shipping delayresolved in 17 minWorking-hours SLA17 minmedian first response81% answered inside target · sample data
One queue for nine networks
Every complaint, comment and DM lands in the same inbox with a status, an owner and a working-hours deadline — including the comment threads under your own posts.
Assignments, statuses and internal notes per conversation
Approved reply templates in the languages you actually answer in
Response-time measured, with breaches flagged before they are noticed
Dashboard+ Add widgetMentions this month5 998+187%vs. last monthMentions vs. categoryEditInfoDuplicateDeleteShare of voice by sourcex.comyoutube.cominstagram.comnews & webMentions by stateCalifornia92%Texas74%New York61%Florida43%Top topicsShippingPriceRefillsSupportsample data
The dashboard the network team will believe
Complaint volume next to sentiment, split by region and by topic, so a coverage argument and a billing argument never get averaged into one flat line.
Region and city breakdowns from the posts themselves
Aspect-level sentiment: coverage, speed, price, support
Scheduled exports for the weekly operations review
What we watch for an operator
Configured around your brand, your tariffs and the districts you serve.
Outage and “no signal” posts, grouped by region and by district
Tariff changes, billing disputes and auto-renewal complaints
Speed and quality arguments, including screenshots of speed tests
Retail store and call-centre service mentions
Regulator, ministry and consumer-body statements
Competitor tariff launches and the reaction to them
What it replaces
The three habits that make an outage look worse than it was.
Finding out from a journalist that a district has been down since morning.
Four browser tabs, one per network, refreshed by hand.
A response-time number nobody can reproduce from the data.