Sent an unwanted phone back on Sept. * using buyer's remorse refusal with Canada Post...

GetHuman-valwrig's customer service issue with Bell Canada from November 2019

Help with my Bell Canada issue
The issue in GetHuman-valwrig's own words
Sent an unwanted phone back on Sept. * using buyer's remorse refusal with Canada Post. The device never reached Bell. Tracking shows the device refused and sent back but trail ends on Sept.**. Have spoken numerous times with Bell Mobility ,Loyalty retention and National channel Support. Am told I cannot have the unwanted line cancelled without charges. The line I do not want is ***-***-****. This line was given to me as a new activation in August **** when I called to upgrade. The phone did not arrive and when I called Loyalty Retention I was advised to use buyer remorse refusal and purchase a phone from my Bell store after phone sent back. I did purchase a phone upgrade at my Bell store after I sent the phone back. I feel I have spent much time with Bell and Canada Post trying to solve the problem . Perhaps I need outside help to plead my case. What do you think?

GetHuman-valwrig did not yet indicate what Bell Canada should do to make this right.

How GetHuman-valwrig fixed the problem

We are waiting for GetHuman-valwrig to fix the problem and share the solution with the rest of us customers.

Do you have a customer issue as well?
We can help you get Bell Canada's attention and get better help faster. Tap below to get started.
Having Bell Canada issues too?
Get tips from pros & other customers, and get it handled faster:
For better results, write at least 100 characters
This email address isn't valid

Bell Canada

Customer service issue
Reported by GetHuman-valwrig
Nov 19th, 2019 - a year ago
Fixed
Seen by 4 customers so far
Similar issue to 686 others
0 customers following this
Items needed
Name on account
Account number
Billing address
Account phone number
Last 4 of SSN
PIN on account

Timeline

GetHuman-valwrig started working on this issue
Nov 19th, 2019 1:29pm
GetHuman-valwrig confirmed the issue is fixed. Hooray!
Nov 20th, 2019 3:09pm