There were things that made the ISP I worked at special, one of them being that we pretty much defaulted to having customers hook up their own DSL, which meant spending a lot of call time helping people who have no idea what an RJ11 jack is install plugs and adapters.
I've also spent a lot of time on "the password I use for my email doesn't work on my Facebook" and "my USB printer doesn't work". People don't know who to call for tech support so they try their ISP. There was also the occasional "the internet is broken" whenever the user's home page had a different theme or design as well, those usually came in waves.
Once the modem and/or router is installed, most internet services Just Work. There are outages and bad modems and the occasional bad software update to deal with, but they're a relatively low call volume compared to what customers call about.
"Maam, if your business is that important, surely you as a responsible business owner have gone and purchased a business class internet service with 24/7 SLA. It says here, you are on our cheapest, residential VDSL service"
This leads to fun tech support calls if you use your own equipment where you're basically proving to the support underling that you know how to run your equipment for the first 20-30 minutes before they take your issue seriously (yes, the modem light is green, yes, I've already power-cycled, yes, I'm testing on a wired connection, etc)
For analyzing support burden, I think the relevant question here is why have you even had the experience of calling tech support for a non-working connection - and that falls squarely on the non-reliability of Comcast's network.
Called them to ask why, and they said it was a planned outage. When was it planned, I asked? 17 minutes ago.
I don't really want any outage credits.
https://www.xfinity.com/support/articles/disable-xfinity-wif...
Now I just use my own customer modem.
I usually speedrun this by telling them something like: I am hardwired to the modem and seeing T4s in the log.
> Please wait a moment while I check on some things on your account.
> Thank you for your patience. Can you please confirm for me that you see a green light on the top of the device? Can you tell me whether the light is blinking or is solid?
I think my conception of basic tech illiteracy among the general public is vastly wrong. I generally like to believe most people are competent enough to handle these sorts of things.
But really, internet (and digital TV) services are pervasive enough that they are no longer just for technologically inclined and resourceful people. All aspects of society are now using the internet, even the homeless, impoverished, disabled, and institutionalized.
Took another call from an irate dialup customer who demanded a refund - he didn't know he needed a computer to use the internet -- and had driven himself mad dialing up our modem bank with his telephone and waiting for the training tones to subside so he could begin to navigate the internet as he imagined it to work: press 1 for email, 2 for news, 3 for weather...
Despite the proliferation of smart phones and greater prevalence of home networks, I don't think the situation has changed much for a segment of the population once you get down to troubleshooting why something isn't working. The skills and the willingness to just try to fix the problem aren't there.
Back when I still had ISPs that provided the modem + router, every single issue I think I ever had fell into one of two categories: a modem and/or router power cycle fixed it, or it was a broader network issue that had nothing to do with me or my particular internet situation (this is omitting the most common third issue: terrible customer service problems, but that's a separate thing)
Also, as the other commenter pointed out, ISPs don't terminate their service at the edge of your premises. Basically all of them today will connect one of your devices to confirm installation.
Also I could save them a bunch of money getting rid of services they don't use, like moving their landlines to VOIP.
If you want a landline to call emergency services, I'd expect a real landline will have higher uptime than one that depends on your router.For example, if you subscribe to Verizon FiOS voice, the technician will disconnect your copper phone lines and connect them to VoIP termination on your ONT.
That's what I did for pocket as a kid in high school (in the mid-2000s).
You call an electrician or a handyman or somebody and tell them you have some low voltage work.
The ISP provides a cable box and modem to most homes in the same way that the electric company sticks a meter on your wall.
In the US, most do. This is a standard part of "in home installation" when first subscribing to service for all of the major providers in the US.
Example: https://forums.xfinity.com/conversations/customer-service/sc...
In San Jose, if you see evidence that your house's main drain has backed up and you have a cleanout within 5' of the sidewalk, you're better off calling the city first before calling a plumber -- the sewer department will snake the "lateral" pipe between the cleanout and the main sewer line under the street for free.
The one time we used this the response time was very quick (in line with the 30 minute response time they cite on their website).
With careful selection of the customer ONU/ONT, the incidence of support calls means that it can be weeks between customer issues on smaller networks. These days my biggest support headache is in house wireless coverage. It's also the one part of internet service that most people are unwilling to invest even small amounts of money to improve. The worst are the folks that install outdoor wireless security cameras without thinking ahead to putting them on a dedicated network to avoid driving up airtime usage and congesting the main wireless AP.
For fiber customer side issues are almost all wifi related, to the point that some operators will offer in home managed wireless options.
I used to provide support in an area where a provider had purchased a VDSL network in order to convert those customers to fiber. 20% of customers remained on VDSL for various reasons. 10% of customers had been moved to a dodgy hybrid fibre/last mile ethernet solution. and the remainder were all on fibre.
70% of support issues related to the VDSL customers. 20% the ethernet customers. and the remainder of issues were almost all wifi or power related.
They had a policy of charging customers 1000 bucks or so to convert them over to Fibre. Eventually they sold the business to a larger entity. 4 weeks of VDSL complaints, and the new owners gave everyone remaining on copper a free fibre upgrade.
Actually it was only technically VDSL. What they did was drop a fibre ntd into the old vdsl node, commission each port for a different customer, and then run a Ethernet / VDSL converter over the old lead in. The "upgrade" was just using the copper as a draw wire for the fibre cable. Nothing over 100 meters.
With fiber, the ISP can see that everything is good up to the GPON terminal. Probably the router too as most customers will just use the ISP provided one. So that leaves the ethernet interface / wifi card as the only thing that would fail and have to be ascertained over the phone, and with a local ISP its probably more cost effective to cut out all the abstractions and just have a tech stop by to check it out.
On the other side, customers have become a lot more used to self help. For example their email isn't even hosted with the ISP any more! I would think that most people would be aware that if a device works good close to the router, and not good far, the issue is wifi range. If they're still calling the ISP, you can direct them towards wifi extenders. Or if device A does not work but device B does, it's not a problem to call the ISP about. And so on.
Of course this is my idyllic view not having worked ISP tech support in a few decades...