Port in from Public Mobile not working

mr_wilson
Posts: 2 ✭
Hello forums, reaching out here after not having much luck with chat support.
Yesterday (Sept 9th) I tried to make the switch from Public to Fizz. During the activation process, I followed the prompts to port my existing number to Fizz.
First attempt was with my Public account#, which failed right away because it turns out my Public account was only active until Sept 8th. I then paid for another month of Public to reactivate my account and that account has been working fine since then.
My second attempt was using the IMEI number of a phone. I submitted the IMEI of an old phone since I had been using that one mainly with Public in the past. This was my own purchase device though, so I understand there can be issues when using IMEI of a device not purchase through a provider.
This second attempt has been in limbo ever since last night, over 12hrs ago, and I have not received any texts or notifications regarding this porting process. I contact Fizz chat support about this, and they suggested I contact Public to see what was going on in the Public system, so I did that as well. According to Public Mobile, they have told me that resubmitting the port request using the account number should sort this out, and that I needed to contact Fizz support to handle the resubmission.
Now I contact Fizz support again this morning, and all they can tell me is to continue to wait. According to them there is no way to resubmit the request under the first one, stuck in limbo, is dealt with.
I wanted to switch to Fizz since they have roaming support in Europe and I will be heading there in 3 days. Unfortunately I don't have much more time to wait for a response. I really need to sort this out ASAP.
Yesterday (Sept 9th) I tried to make the switch from Public to Fizz. During the activation process, I followed the prompts to port my existing number to Fizz.
First attempt was with my Public account#, which failed right away because it turns out my Public account was only active until Sept 8th. I then paid for another month of Public to reactivate my account and that account has been working fine since then.
My second attempt was using the IMEI number of a phone. I submitted the IMEI of an old phone since I had been using that one mainly with Public in the past. This was my own purchase device though, so I understand there can be issues when using IMEI of a device not purchase through a provider.
This second attempt has been in limbo ever since last night, over 12hrs ago, and I have not received any texts or notifications regarding this porting process. I contact Fizz chat support about this, and they suggested I contact Public to see what was going on in the Public system, so I did that as well. According to Public Mobile, they have told me that resubmitting the port request using the account number should sort this out, and that I needed to contact Fizz support to handle the resubmission.
Now I contact Fizz support again this morning, and all they can tell me is to continue to wait. According to them there is no way to resubmit the request under the first one, stuck in limbo, is dealt with.
I wanted to switch to Fizz since they have roaming support in Europe and I will be heading there in 3 days. Unfortunately I don't have much more time to wait for a response. I really need to sort this out ASAP.
0
Answers
-
Hello @mr_wilson ,
I am sorry to hear that.
I wanted to inform you that I have verified the account and I'm pleased to let you know that the transfer has been finalized successfully. Your plan is now active and ready for use.
I recommend that you kindly check and test the line to ensure everything is functioning smoothly. You can follow the instructions here: https://fizz.ca/en/faq/how-test-my-fizz-line
Should you encounter any issues or need further assistance, please feel free to contact our live agents here: https://fizz.ca/en/support
Thank you for your cooperation, and please don’t hesitate to reach out if you need any further support.
Have a good one,
Alexandra, Community Moderator0
This discussion has been closed.