Koodo Community

Community

Solved

Just joined. number porting question


Userlevel 1
Hi, I just joined yesterday. I am porting a landline number from Teksavvy to my new Koodo account. the Koodo rep at the booth had no idea how to do it. He couldn't find Teksavvy as a provider on his computer. He ended up calling the Koodo support. I still don't know when it is going to happen. does anyone have any ideas? Also I really hope it happens cause I need the number. It's been with me for 11 years.

17 replies

Userlevel 7
Hey Fred,

It will definitely happen, CRTC requires all phone numbers to be portable from one carrier to another. The only thing is that typically landline numbers do take a bit more time for the port to occur. If you don't hear back in a few days, give Koodo support a call using *611 from your phone.
Userlevel 7
Badge +4
Did they end up requesting a port?

If not, you can do this yourself via Self Serve:


Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

They said they did. Should I do it online too or would that confuse support?
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

No need to do it twice. I'll check with Koodo if your port has been requested.
Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

Oh man I really appreciate it. Do you need my temp number or anything?
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

Not at this moment (I can't look into it personally), and it's not advisable to share contact information in a public forum. Is the email you used for the Community the same as you have on your Koodo account?
Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

yes same email
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

There was an error with your port request (request failed) and it has been escalated to the next department. Estimated time to resolve the issue is 3-5 days. I have no information about why the request failed.
Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

The landline is going to get disconnected next Tuesday. I hope it is done by then. I did call Teksavvy. They said numbers get ported away from them all the time. They said there should be no issues porting this number over.
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

When Koodo ports your number, this disconnects your current line. If you have requested a cancellation from Teksavvy, please cancel that request. If you have them cancel, you will not be able to retrieve that number.

If this is the case, it may be the reason why your port request failed.
Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

No I don't think this is why. I have DSL on the same line as a wet loop. I have requested for it to become a dry loop. I don't think this should affect the porting. Next Tuesday is 5 business days from yesterday the line is still active so there should be ample time for porting.

Just contacted Koodo support unfortunately they can't tell me when the porting is going to happen. Teksavvy CS is telling me there has been no request for the porting yet and it is up to Koodo to put a request in.
Userlevel 7
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

Ivan is giving you solid advise. Call teksavvy and cancel your cancel request. Otherwise you do risk loosing that number.
Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

If it is not ported over by Monday I will cancel it for now.
Userlevel 6
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

Just curious, as I've heard this term before, what is a "wet loop" in regards to your DSL?
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

@Jru
It actually does not exist. People use the term as the opposite of a 'dry' loop, which is a DSL internet connection without an associated telephone service. Remember, early days of ADSL were run on the POTS backbone, and the telco had to make special changes at the exchange office to accommodate folks who wanted DSL without having a telephone on the same pair.

Userlevel 1
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

The number got ported over to Koodo this morning. So it took 3 business days.
The crazy thing is that my ADSL didn't drop so Teksavvy automatically switched me to a dry loop.
Kudos to both Koodo and Teksavvy.
Thanks
Userlevel 7
Badge +4
Ivan wrote:

Did they end up requesting a port?

If not, you can do this yourself via Self Serve:

[img]https:...

Glad to hear it worked out. We're always here to help should you need it.

Reply