Porting a business number to an AI answering service versus forwarding it: what changes hands

What is the actual difference between porting a number and forwarding it?

Porting moves a telephone number's home record from one carrier to another. Before the port, your old carrier is the number's authoritative holder in the network. After it, your new carrier is. The number itself does not change, but the underlying registration does, and once it completes, your old carrier has no technical claim on that number at all. It is gone from their systems.

Forwarding does none of that. Your old carrier still owns the number's registration. You have simply told that carrier's switch to send incoming calls to a different destination, whether that is a second phone, a VoIP trunk, or an AI answering service's own number. The original registration never moves. If you stop paying the old carrier, or the old carrier stops existing, the forward stops working and the number is silent, even though nothing about the AI service itself has changed.

The practical marker is who you would have to call to make the number stop working entirely. With forwarding, that is always your original carrier, no matter how many layers of redirection sit on top. With a completed port, it is whoever you ported to, and your original carrier is no longer in the chain at all.

Who owns a phone number in Canada?

No one owns a telephone number the way they own a domain name or a piece of equipment. The CRTC treats it as a resource assigned to a customer that the customer has a right to keep as they change providers. Telecom Decision CRTC 2005-72 states plainly that "number portability enables customers to keep the same telephone number when changing service providers" [portabilityDefinition]. That is a right you exercise, not a title you hold.

The practical effect is that a business does not have stronger rights over its own number than a residential customer does. Nothing in the CRTC's decisions carves out a separate, sturdier guarantee for a commercial line, which is easy to assume when a number has fifteen years of signage, invoices and Google reviews built around it. The obligation the CRTC places on carriers is framed around customers generally, and a business relies on the same floor everyone else does.

Wireline portability, the kind that applies to a traditional landline, has been mandatory since the Commission's 1997 decision. As the 2005 ruling records it, "the Commission has required wireline carriers to implement local number portability (LNP) since it issued Local Competition, Telecom Decision CRTC 97-8, 1 May 1997" [lnpMandatedSince1997]. A landline number a Langley plumber has held since the late nineties has therefore been portable for essentially its entire working life, whether or not he ever tried.

What does the CRTC's portability rule guarantee you?

It guarantees a mechanism and a timeline, not a service level to the customer directly. The regulated interval for a standalone landline-to-landline port is two business days, according to the Commission's determination in the cited order [portIntervalTwoDays]. That interval carries over when the port crosses from landline to mobile or the reverse, including through a reseller, since the Commission set "the appropriate service interval for simple intermodal (wireless-to-wireline and wireline-to-wireless) porting, including simple ports involving wireless resellers or mobile virtual network operators, is to be the same as the local exchange carrier-to-local exchange carrier (LEC-to-LEC) service interval for stand-alone porting, which is currently two business days" [portIntervalIntermodal].

Mobile-to-mobile ports run on a much faster clock. The same decision sets it at "2.5 business hours" for wireless-to-wireless porting [portIntervalWireless]. That gap is why an owner who has switched cell carriers in an afternoon expects the same speed when moving a business landline into a new phone system, and is surprised when the answer is measured in days rather than hours.

The interval is a floor set for how carriers must behave toward each other, not a promise made directly to the customer, and a rejected port resets the clock rather than merely pausing it. Treat two business days as the minimum exposure window for a clean port, not a guaranteed completion time.

Why can a number sometimes not be ported at all?

Every Canadian number, whether landline or mobile, is tied to a rate centre, meaning a specific physical telephone exchange. The 2005 decision explains it this way: "wireless carriers use North American Numbering Plan (NANP) geographic-based numbers that are associated with a specific rate centre that uniquely locates a telephone exchange. With NANP numbers, all calls to a number associated with an exchange are deemed to have terminated at the rate centre of the exchange" [rateCentreGeography].

That geographic tie is the reason a number sometimes cannot follow a business the way an owner expects. A Kelowna med spa moving its clinic to West Kelowna is changing location within a region the carriers involved may treat as the same rate centre, and the port goes through without incident. A business relocating across a bigger boundary, say from Penticton to a different exchange entirely, is asking a different question than "can I change providers," and the CRTC's portability decisions do not answer it. Whether the number survives that move depends on the specific carriers on both ends, not on a regulatory right you can invoke.

What can go wrong in the middle of a port?

A port is not one action, it is a request that a new carrier has to prove and an old carrier can refuse. The gaining provider typically has to demonstrate the request is legitimate before anything moves. Twilio's porting documentation describes a standard onboarding flow in which customers upload utility bills showing proof of ownership for phone numbers to be ported [portProofOfOwnership], and a bill that does not match the account name or address on file is a common, mundane reason a port stalls before it starts.

The carrier being left also has a say. The same documentation notes that a request fails when "at least one number in the port-in request has been rejected by the losing carrier" [portRejectedByLosingCarrier], and the rejection arrives as a reason code rather than a phone call explaining what to fix. Outstanding balances, a mismatched business name, or a number that is not active on that account are the usual culprits.

A third failure has nothing to do with either carrier's willingness. The paperwork authorizing the port, the letter of authorization, expires if nobody signs it in time. Twilio's documentation gives the applicant "30 days to sign" [portLoaExpiry], and a port that quietly dies because an owner never opened the email is indistinguishable, from the outside, from one that was refused. All three failure modes look the same to the business: the number just did not move, and no one called to say why.

Porting versus forwarding, side by side

Porting moves the number's legal home to a new carrier. Forwarding leaves the number's legal home where it was and adds an instruction on top of it.

A port severs the old carrier from the number entirely once it completes. A forward keeps the old carrier permanently in the chain, because the forward is a setting on their switch, not a transfer.

A port is governed by a CRTC service interval, two business days for a standard landline or intermodal move [portIntervalTwoDays] [portIntervalIntermodal], which means the old carrier has a deadline. A forward is governed by nothing regulatory at all, so the old carrier sets the terms, the price, and can withdraw it.

A port needs proof of ownership and a signed authorization before it happens [portProofOfOwnership] [portLoaExpiry]. A forward needs nothing but a login to the old account, which means whoever controls that account controls whether the forward keeps working.

A port, once complete, makes the old vendor irrelevant to the number's future. A forward keeps the old vendor's continued existence, billing status and goodwill a permanent precondition of the number working at all.

An AI answering service that is just receiving forwarded calls can be turned off in an afternoon with zero effect on the number, because the number was never theirs to begin with. An AI answering service that has taken a port holds the number the way any carrier does, and leaving them means running the same two-day porting process again, this time in the other direction, with all the same ways it can stall.

How do you leave an AI vendor and take the number with you, cleanly?

Start by finding out, in writing, which of the two arrangements you have. Ask the vendor directly whether the number was ported into their system or is being forwarded to it, and ask for the name of the carrier the number is currently registered under. If they cannot answer that second question specifically, that is itself informative.

If it is a forward, the number was never theirs. Cancelling the AI service and pointing the forward back to a phone, or to a different vendor, is a change made entirely on the old carrier's side, and it can typically happen the same day.

If it was ported to the AI vendor, plan for the standard porting timeline in reverse: gather a recent bill or account statement from the current holder that matches the account name, since a mismatch is the single most common reason a port stalls [portProofOfOwnership], initiate the port to the new carrier or vendor, and expect and sign the letter of authorization promptly, since it lapses after 30 days if ignored [portLoaExpiry]. Budget the regulated two business days as a floor, not a guarantee, and confirm the new destination is receiving calls correctly before telling customers or updating signage.

What should you check in the contract before you agree to either one?

Ask the vendor to state, in the agreement itself rather than in a sales call, whether the number will be ported or forwarded. A verbal assurance that "you'll always have your number" is true of both arrangements and settles nothing.

If porting is proposed, ask what happens to the number if the vendor shuts down, is acquired, or simply stops answering support tickets. Nothing in the CRTC's porting decisions covers this scenario, because it addresses a customer's right to leave a carrier, not a carrier's obligations when it ceases operating. That answer exists only in the vendor's own terms of service, and it has to be read there before signing rather than assumed from the regulation.

Ask, specifically, how a port-out request is handled on their end: what proof they require, what their internal turnaround time is beyond the CRTC floor, and whether there is a fee. None of that is regulated, and a vendor with a clean answering service can still have a slow or costly exit process buried in a schedule at the back of the contract.

A workable exit checklist

Before signing anything, get in writing which arrangement is being offered, forwarding or porting, and the name of the carrier that will hold the number afterward.

On day one of an exit: request written confirmation of whether the number is currently ported to the vendor or merely forwarded to their system, and get the exact carrier name the number sits with today.

On day one to two: if forwarding, log into the original carrier's account and repoint the forward, or cancel it, directly. Confirm the change with a test call within the hour.

On day one to two, in parallel, if it was ported: gather a current bill or account statement matching the account name, and submit the port request to the new destination.

Within 30 days of submitting: watch for the letter of authorization and sign it promptly, since it lapses after 30 days unattended [portLoaExpiry].

Business day two after signing: this is the CRTC's standard interval for a completed landline or intermodal port [portIntervalTwoDays] [portIntervalIntermodal]. If the port has not completed, ask the new carrier for the rejection reason rather than assuming the delay is routine, since a rejected port restarts the clock rather than pausing it.

Once live: test the number from an outside line, update voicemail or greeting messages, and only then update signage, Google Business listings and invoices that reference the number.

What if the port stalls or gets rejected, and there is no clean answer available?

A stalled port is not a dead end, but it is not self-resolving either. Ask the new carrier for the specific rejection reason rather than the general status, since "rejected by the losing carrier" [portRejectedByLosingCarrier] covers everything from an outstanding balance to a mismatched business name, and each has a different fix. A name mismatch is usually solved by pulling a bill that matches the account rather than a summary or a marketing email.

If the letter of authorization lapsed unnoticed, the fix is simply to resubmit and sign it inside the new 30-day window [portLoaExpiry], rather than treating the lapse as a refusal.

If a vendor holding a ported number has gone unresponsive or shut down, the CRTC's decisions do not describe a guaranteed recovery path for that specific situation, because they govern a customer choosing to leave a functioning carrier, not a carrier that has disappeared. Recovering the number in that case depends on whatever the defunct vendor's own contract or wind-down process says, which is why that clause is worth reading before signing rather than after.