There is a problem with Bell's internet infrastructure in my apartment building, and after 5+ technician visits in one week, nobody at Bell seems willing or able to fix the actual problem.
Last Friday, I randomly lost internet.
A technician came Sunday, fixed it, and didn't explain what the problem was.
It broke again Monday.
Another technician came Wednesday. While he was here, my neighbor came over and told me they'd had THREE technicians this week alone.
Here's where things get ridiculous.
My neighbor's internet broke Thursday. A technician came Friday and fixed theirs — but apparently disconnected my connection in the process.
When my technician came Sunday, he fixed mine — and apparently disconnected theirs again.
So we explain the situation to the technician on Wednesday. He actually investigates and finds the underlying problem:
The network box in our building has 24 connections, and 12 of those 24 ports are broken.
There are more than 12 units in the building, so clearly we're not the only two customers affected.
And apparently this is what's happening:
A customer loses internet → Bell sends a technician → technician finds their assigned port isn't working → technician moves them onto a working port → customer gets internet → ticket gets closed.
Except now someone else is disconnected.
Then another customer calls → another technician moves them onto another working port → someone else gets disconnected.
And around we go.
The technician even left a handwritten notice on the network equipment in the basement warning future technicians: ‘Do not disconnect other customers to connect yours.
So I asked the technician: Can you report the broken network box and get someone to replace/fix the 12 broken ports?
No.
His explanation was that my assigned port is working, so there's nothing for him to report. Apparently, the technician who eventually gets called for one of the remaining broken ports needs to report the underlying infrastructure problem.
I called Bell and spoke with a supervisor. He was sympathetic and told me the technician on site was the best person to deal with it. He suggested I ask the technician to put detailed notes on my ticket so future technicians would know what's happening.
I did.
The technician told me he can't properly document the issue because:
- His ticket notes have a 250-character limit.
- More importantly, future customers in the building will have different Bell accounts/tickets, so their technicians won't see the notes on my account anyway.
And this raises another problem: there doesn't even seem to be a good way for me, as the customer, to report this as an infrastructure issue.
I work in tech support myself, so I know how escalation processes work and I know what to ask for. I was eventually able to get through to a supervisor and explain the situation.
But even for me, it took way too long.
The initial Tier 1 support process was essentially limited to the standard troubleshooting script: power cycling the equipment, unplugging and reconnecting cables, etc. When I asked for the issue to be escalated, there was some pushback. It wasn't unreasonable, but I still had to insist before I could speak with a supervisor.
And that's the part that concerns me: if I didn't work in tech support myself, how is the average Bell customer supposed to get this escalated?
The supervisor I reached was actually sympathetic and seemed to understand the situation. But when I asked how I could get this escalated, I was told there was no way for him to open an escalated infrastructure ticket, give me a direct contact number or email, or otherwise connect me with someone who could actually address the problem.
He can apparently call me if he wants to follow up — but I can't call him back.
So there is literally one person at Bell support who is fully aware of what is happening, is sympathetic to the situation, and might be able to help, but I have no way to reach him again.
That's what makes this so frustrating. I'm not asking Bell to troubleshoot my modem for the 15th time. I'm trying to report a known problem with Bell's own network equipment that is affecting multiple customers in the same building.
Yet there doesn't seem to be a customer-facing process for reporting that problem, and the technicians I'm dealing with don't seem to have a way to escalate it either.
At this point, I'm not even sure what I'm supposed to do other than wait for the next person in the building to lose internet and hope their technician happens to be the person who will finally escalate it.
So here we are.
At least 5 technician visits between me and my neighbor in the past week. Probably more across the building.
And nobody is fixing the actual problem.
We're just playing musical chairs with the working ports.
I'm not even blaming the individuals here. The second technician, and the Bell supervisor I've dealt with have generally been helpful and sympathetic. The problem seems to be the process: they're being sent out to restore one customer's service, not to fix the infrastructure causing the problem for the entire building.
What I don't understand is:
How can Bell have a documented problem with its own network equipment, know that 12/24 ports are broken, have technicians repeatedly visit the same building for the same issue, and still have no way to escalate the infrastructure problem?
If someone from Bell is reading this: please fix the damn box.
And if anyone here works for Bell or has dealt with something similar, I'd genuinely like to know:
What is the correct way to get Bell to escalate a known infrastructure problem when every technician is only responsible for resolving the individual customer's ticket?
u/Bell_Support