# Troubleshooting number port rejections

Canonical: https://warmtransfer.net/knowledge/number-port-rejections

Last verified: 2026-10-01

United States carriers must complete a simple wireline-to-wireline or simple intermodal port request within 1 business day unless a longer period is requested[^36]. When port requests fail validation, losing carriers reject the order until missing, inaccurate, or restricted account details are resolved[^41][^5].

## How it works

The Federal Communications Commission (FCC) defines a simple port as an order that involves no unbundled network elements, covers an account with only a single line, has no complex switch translations (such as Centrex, ISDN, advanced intelligent network, remote call forwarding, or multiple services on the loop), and involves no reseller[^35]. Under the porting-interval rule, intermodal ports include wireline-to-wireless, wireless-to-wireline, and ports involving interconnected Voice over Internet Protocol (VoIP) service[^20].

For the porting interval, Monday to Friday are mandatory business days and 8 a.m. to 5 p.m. are the minimum business hours, excluding the current provider's company-defined holidays[^1]. A simple port is eligible for activation at midnight the same day only if the current provider receives an accurate and complete Local Service Request (LSR) between 8 a.m. and 1 p.m. local time[^21]. FCC 10-85 adopted the North American Numbering Council's (NANC) recommended Local Number Portability (LNP) provisioning flows and required the industry to adhere to them[^22]. A Firm Order Commitment (FOC) is the losing carrier's confirmation that the number will be ported, together with the date it will release the number[^14].

Under 47 CFR 52.36, 14 standard data fields are listed for a simple port order, including the ported telephone number, account number, ZIP code, company code, new network service provider, desired due date, and purchase order number[^17]. FCC 10-85 requires providers to use these 14 standard fields, and only those 14 fields, to accomplish a simple port[^24]. The FCC has held that the porting-out provider may not require more information from the porting-in provider than is reasonable to validate the port request and accomplish the port[^23]. To validate a simple port, the FCC clarified that providers may require no more than 4 fields:
- The 10-digit telephone number[^16]
- The customer account number[^16]
- The 5-digit ZIP code[^16]
- A passcode if applicable[^16]

In a simple port order, the passcode field is optional unless the end user requested and was assigned a passcode[^25].

FCC 10-85 provides that a requested customer service record (CSR) must be returned within 24 clock hours unless otherwise negotiated, excluding weekends and the current provider's holidays[^12]. In addition, FCC 10-85 states that carrier-assigned passcodes may not be required in order to obtain a CSR[^11].

WarmTransfer's reading of the sources is that multi-day lead times imposed by cloud platforms on port-ins, such as a 7-day minimum, are platform policies layered on top of the FCC's 1-business-day simple-port interval rather than the regulatory interval itself[^26].

## Common rejection causes and carrier locks

In the field, losing carriers reject port orders whose business name, authorized name, or address differs even slightly from the CSR, and they usually expect the service address rather than the billing address[^13]. Telnyx notes that the billing telephone number (BTN) or account telephone number (ATN) is typically not printed on a bill copy except for wireless or toll-free ports, and advises requesting a CSR from the carrier to find it[^46]. Telnyx also identifies submitting numbers from multiple accounts in 1 request, as well as a reseller's end customer submitting their own BTN instead of the reseller's BTN, as causes of BTN/ATN mismatch rejections[^47].

A preferred carrier freeze under 47 CFR 64.1190 prevents a change in the subscriber's preferred carrier selection unless the subscriber gives the carrier holding the freeze express consent[^3]. Preferred carrier freeze procedures must clearly distinguish among services such as local exchange, intraLATA toll, and interLATA toll, allowing a freeze to apply to local exchange service[^2]. A carrier offering preferred carrier freezes must accept a subscriber's written or electronically signed authorization to lift the freeze, and must also accept oral authorization with a mechanism for the submitting carrier to initiate a 3-way conference call[^4].

For mobile numbers, the federal port-out fraud protections in 47 CFR 52.37 apply to commercial mobile radio service (CMRS) providers, including wireless resellers, but not to wireline or VoIP providers[^32]. 47 CFR 52.37(b) requires wireless providers to use secure methods to authenticate a customer before effectuating a port-out request[^33]. The FCC's 2023 SIM swap and port-out fraud rules require wireless providers to immediately notify customers whenever a SIM change or port-out request is made on their accounts[^31]. In DA 24-649, the Wireline Competition Bureau waived compliance with the SIM swap and port-out fraud rules that were not subject to Office of Management and Budget (OMB) review until OMB completes its review, ensuring all the rules take effect on 1 date[^34]. As reproduced on 2026-10-01, paragraphs (c) through (e) and (g) of 47 CFR 52.37 show as reserved[^27], and 47 CFR 52.37(h) states that the section contains information-collection requirements where compliance is not required until that paragraph is removed or assigned a compliance date[^28]. WarmTransfer's reading of the sources is that because the codified 52.37 still shows reserved paragraphs and a compliance-pending note, this packet cannot establish that a federal port-out lock obligation is enforceable as of 2026-10-01, and carrier locks seen in the field may be voluntary carrier features[^30].

A Verizon Number Lock prevents a mobile number from being moved, requiring the customer to turn it off (such as via *611 or in My Verizon) before porting out[^52]. A Verizon Number Transfer PIN expires after 7 days and is used alongside the Verizon account number to authorize the port to the new provider[^53].

## Platform differences

| Platform | Rejection reasons and configuration rules | Port modification and lock handling |
| --- | --- | --- |
| Microsoft Teams | Rejections occur if the BTN mismatches or if an account freeze remains[^39]. An account PIN is required for every mobile number[^38]. The status Exception denotes rejection by the losing carrier, typically for incorrect PIN or ZIP code[^41]. The US and Canada wizard groups numbers by account, provider, and type, requiring 1 request per group[^43]. In a full port, all numbers on the BTN port and the account closes[^42]. | Microsoft distinguishes an account PIN from a BTN freeze PIN, which permits an authorized user to unfreeze an account[^37]. In a partial port including the BTN, designating an unported replacement BTN is optional[^44]. Canceled orders reuse no prior documents or validations[^40]. If rejected, admins are directed to update their existing case with the Phone Number Service Center (TNS Service Desk)[^45]. |
| Cisco Calling Plan | Top rejection causes include a pending LSR at the losing provider (such as an address change or port-out)[^6]. Numbers on the same account must port together; porting the main billing number requires designating an unported replacement BTN[^10]. Inaccurate or incomplete data causes rejection, which may reset the SLA timeline depending on the country[^8]. | Freezes or restrictions at the losing carrier must be removed prior to port submission[^9]. Customers clear rejections with the losing carrier, then update and resubmit the order in Control Hub[^5]. Date changes before FOC occur in Control Hub; post-FOC changes require a support case, and changes within 24 hours of the port date carry high risk[^7]. |
| Zoom Phone | Rejections occur when alarm monitoring services remain on any numbers, requiring those services to be moved or stopped first[^54]. Zoom requires a bill copy dated within the last 45 days, though certain regions mandate 30 days or 3 months[^56]. | Only the current provider can remove an account lock or freeze, requiring direct customer contact[^57]. Rescheduling an activation requires withdrawing the order and submitting a new one, restarting the process[^58]. Toll-free port dates typically cannot change after FOC is issued[^59]. Requests cancel automatically after 15 business days without a customer response[^55]. |
| Genesys Cloud | Carrier freezes cause rejections and can take 1 to 3 weeks to remove depending on the provider[^19]. | All ports are treated as partial ports by default[^18]. |
| Twilio | Losing carriers reject orders with error 22158 when the target date falls on a public holiday or maintenance window, requiring resubmission with a new date[^48]. The PortIn API exposes per-number rejection_reason, rejection_reason_code, and not_portability_reason_code fields[^49]. | The PortIn API requires the target port-in date to be at least 7 days in the future for US ports without guarantee[^50]. A PortIn request must reference at least 1 uploaded document of type Utility Bill[^51]. |

## See also

See also [Number porting and LNP workflows](https://warmtransfer.net/knowledge/number-porting).
See also [Porting numbers to Microsoft Teams](https://warmtransfer.net/knowledge/teams-number-porting).
See also [Toll-free numbering and RespOrg](https://warmtransfer.net/knowledge/toll-free-numbering).
See also [Business texting and 10DLC registration](https://warmtransfer.net/knowledge/business-texting-10dlc).
See also [E.164 numbering and dial string normalization](https://warmtransfer.net/knowledge/e164-numbering).
See also [International phone number requirements](https://warmtransfer.net/knowledge/international-number-requirements).
See also [Troubleshooting international call failures](https://warmtransfer.net/knowledge/international-dialing-failures).
See also [STIR SHAKEN attestation framework](https://warmtransfer.net/knowledge/stir-shaken-framework).
See also [Robocall mitigation and RMD obligations](https://warmtransfer.net/knowledge/robocall-mitigation).
See also [Branded calling and CNAM delivery](https://warmtransfer.net/knowledge/branded-calling-cnam).
See also [Call blocking and analytics labeling remediation](https://warmtransfer.net/knowledge/call-blocking-labeling).
See also [Wrong or missing caller ID on outbound calls](https://warmtransfer.net/knowledge/caller-id-presentation-problems).
See also [RCS Business Messaging](https://warmtransfer.net/knowledge/rcs-business-messaging).
See also [Responding to a suspected toll fraud incident](https://warmtransfer.net/knowledge/toll-fraud-incident-response).
See also [Telecom taxes and regulatory fees on UCaaS bills](https://warmtransfer.net/knowledge/telecom-taxes-fees).

## Applicability

Applies to: Microsoft Teams Calling Plans, Cisco Calling Plan, Zoom Phone, Genesys Cloud, Telnyx Number Porting, Twilio Phone Numbers, Bandwidth, and Verizon Wireless. Deployments: multi-tenant and carrier. Sources checked 2026-10-01. The Teams port wizard rules apply to US and Canadian port-in workflows[^39][^37][^43], with mobile account PIN requirements applying across all regions[^38]. Genesys Cloud partial-port defaults and carrier unfreeze timelines cover the US and Canada[^18][^19]. Twilio 7-day target lead times apply specifically to US ports[^50].

## What remains uncertain

A Federal Register notice announcing OMB approval and compliance date for SIM swap and port-out rules is not covered by the sources below. The regulatory text regarding port-out notification and locks is not covered by the sources below. Whether SMS and 10DLC enabled numbers block or delay ports is not covered by the sources below. Microsoft port-order-overview planning page lead times and rejection guidance are not covered by the sources below. UK Ofcom General Condition B3 porting and European Union porting rejections are not covered by the sources below. Toll-free porting and RespOrg change rejections are not covered by the sources below. Contact center port-in rejection handling procedures are not covered by the sources below. Port-out PIN and lock features for wireless accounts are not covered by the sources below.

## Sources

[^1]: For the porting interval, Monday to Friday are mandatory business days and 8 a.m. to 5 p.m. are the minimum business hours, excluding the current provider's company-defined holidays. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(a). Checked 2026-10-01.
[^2]: Preferred carrier freeze procedures must clearly distinguish among services such as local exchange, intraLATA toll and interLATA toll, so a freeze can apply to local exchange service. Source: [47 CFR § 64.1190 - Preferred carrier freezes](https://www.law.cornell.edu/cfr/text/47/64.1190), 47 CFR 64.1190(c). Checked 2026-10-01.
[^3]: A preferred carrier freeze under 47 CFR 64.1190 prevents a change in the subscriber's preferred carrier selection unless the subscriber gives the carrier holding the freeze express consent. Source: [47 CFR § 64.1190 - Preferred carrier freezes](https://www.law.cornell.edu/cfr/text/47/64.1190), 47 CFR 64.1190(a). Checked 2026-10-01.
[^4]: A carrier that offers preferred carrier freezes must accept a subscriber's written or electronically signed authorization to lift the freeze, and must also accept oral authorization with a way for the submitting carrier to set up a three-way conference call. Source: [47 CFR § 64.1190 - Preferred carrier freezes](https://www.law.cornell.edu/cfr/text/47/64.1190), 47 CFR 64.1190(e). Checked 2026-10-01.
[^5]: After a Cisco Calling Plan port is rejected, the customer works with the losing carrier to clear the reason, then updates the rejected order in Control Hub and resubmits it. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), Rejection handling / resubmission section. Checked 2026-10-01.
[^6]: Cisco lists a pending LSR on the account at the old service provider, such as a port-out or address change, among the top reasons losing carriers reject Cisco Calling Plan port-ins. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), Top rejection reasons section. Checked 2026-10-01.
[^7]: For Cisco Calling Plan, port date changes before FOC can be made in Control Hub, but changes after FOC need a support case, and changes within 24 hours of the port date are high risk. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), Port date changes / FOC section. Checked 2026-10-01.
[^8]: Cisco states that inaccurate or incomplete port information causes rejection, and that a rejection can reset the porting SLA timeline depending on the country. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), Porting guidelines / rejection section. Checked 2026-10-01.
[^9]: Cisco instructs customers to remove any account freezes or restrictions at the losing carrier before starting a Cisco Calling Plan port. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), Pre-port checklist / account freezes. Checked 2026-10-01.
[^10]: Cisco requires numbers on the same account to port at the same time, and when the main billing number ports, a non-ported number is designated as the replacement BTN. Source: [Cisco Calling Plan number porting guidelines and policies](https://help.webex.com/en-us/article/01sijg/Cisco-Calling-Plan-number-porting-guidelines-and-policies), BTN / partial port guidance. Checked 2026-10-01.
[^11]: FCC 10-85 states that carrier-assigned passcodes may not be required in order to obtain a CSR. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 21. Checked 2026-10-01.
[^12]: FCC 10-85 provides that a requested customer service record (CSR) be returned within 24 clock hours unless otherwise negotiated, excluding weekends and the current provider's holidays. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 19. Checked 2026-10-01.
[^13]: In the field, losing carriers reject port orders whose business name, authorized name or address differs even slightly from the CSR, and they usually expect the service address rather than the billing address (field report). Source: [7 Most Common Reasons Your Port Order is Rejected](https://www.bandwidth.com/blog/7-most-common-reasons-your-port-order-is-rejected/), Reasons 1-3. Checked 2026-10-01.
[^14]: A Firm Order Commitment (FOC) is the losing carrier's confirmation that the number will be ported, together with the date it will release the number. Source: [Firm Order Commitment (FOC) and How It Impacts Porting](https://www.bandwidth.com/glossary/firm-order-commitment-foc/), Glossary definition. Checked 2026-10-01.
[^15]: Under the flows adopted in FCC 10-85, the current provider must return an FOC or reject within 4 hours when the requested due date is 1 to 2 business days after the LSR, and within 24 hours for later due dates or non-simple ports. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 27 (timing chart). Checked 2026-10-01.
[^16]: The FCC clarified that providers may require no more than four fields to validate a simple port: the 10-digit telephone number, the customer account number, the 5-digit ZIP code and a passcode if applicable. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order and Further Notice of Proposed Rulemaking (FCC 09-41)](https://docs.fcc.gov/public/attachments/FCC-09-41A1.txt), FCC 09-41, para. 8 and n.32 (referring to the 2007 clarification). Checked 2026-10-01.
[^17]: 47 CFR 52.36 lists 14 standard data fields for a simple port order, including ported telephone number, account number, ZIP code, company code, new network service provider, desired due date and purchase order number. Source: [47 CFR § 52.36 - Standard data fields for simple port order processing](https://www.law.cornell.edu/cfr/text/47/52.36), 47 CFR 52.36(b). Checked 2026-10-01.
[^18]: Genesys Cloud treats every port as a partial port by default. Source: [Port numbers in US and Canada overview](https://help.genesys.cloud/articles/port-numbers-overview/), Common rejection causes > partial vs full port. Checked 2026-10-01.
[^19]: Genesys lists a carrier account freeze as a rejection cause and says removing it can take 1 to 3 weeks depending on the carrier. Source: [Port numbers in US and Canada overview](https://help.genesys.cloud/articles/port-numbers-overview/), Common rejection causes > account freeze. Checked 2026-10-01.
[^20]: Under the porting-interval rule, intermodal ports include wireline-to-wireless, wireless-to-wireline and ports involving interconnected VoIP service. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(e) definitions. Checked 2026-10-01.
[^21]: A simple port is eligible for activation at midnight the same day only if the current provider receives an accurate and complete LSR between 8 a.m. and 1 p.m. local time. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(a). Checked 2026-10-01.
[^22]: FCC 10-85 adopted the NANC's recommended LNP provisioning flows and required the industry to adhere to them. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 18. Checked 2026-10-01.
[^23]: The FCC has held that the porting-out provider may not require more information from the porting-in provider than is reasonable to validate the port request and accomplish the port. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 10 (citing prior Commission authority). Checked 2026-10-01.
[^24]: FCC 10-85 requires providers to use the 14 standard fields, and only those 14 fields, to accomplish a simple port. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order (FCC 10-85)](https://docs.fcc.gov/public/attachments/FCC-10-85A1.txt), FCC 10-85, para. 9. Checked 2026-10-01.
[^25]: In a simple port order the passcode field is optional unless the end user requested and was assigned a passcode. Source: [47 CFR § 52.36 - Standard data fields for simple port order processing](https://www.law.cornell.edu/cfr/text/47/52.36), 47 CFR 52.36(c). Checked 2026-10-01.
[^26]: The multi-day lead times that cloud platforms impose on port-ins (for example Twilio's 7-day minimum) are platform policy layered on the FCC's one-business-day simple-port interval; they are not the regulatory porting interval (inferred). Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(a) read with Twilio PortIn target_port_in_date. Checked 2026-10-01.
[^27]: As reproduced by LII on 2026-10-01, paragraphs (c) through (e) and (g) of 47 CFR 52.37 show as [Reserved]. Source: [47 CFR § 52.37 - Number portability requirements for wireless providers](https://www.law.cornell.edu/cfr/text/47/52.37), 47 CFR 52.37(c)-(e), (g). Checked 2026-10-01.
[^28]: 47 CFR 52.37(h) states that the section contains information-collection requirements and that compliance is not required until that paragraph is removed or given a compliance date. Source: [47 CFR § 52.37 - Number portability requirements for wireless providers](https://www.law.cornell.edu/cfr/text/47/52.37), 47 CFR 52.37(h). Checked 2026-10-01.
[^29]: FCC 23-95 requires wireless providers to offer customers, at no charge, an opt-in lock that blocks port-outs; the customer removes it by contacting the provider and authenticating. Source: [Protecting Consumers from SIM-Swap and Port-Out Fraud, Report and Order and FNPRM (FCC 23-95)](https://docs.fcc.gov/public/attachments/FCC-23-95A1.txt), FCC 23-95, port-out lock discussion (summarizer reported para. 61; unverified) and Appendix A 52.37 (not retrieved). Checked 2026-10-01.
[^30]: Because the codified 52.37 still shows reserved paragraphs and a compliance-pending note, this packet cannot establish that a federal port-out lock obligation is enforceable as of 2026-10-01; carrier locks seen in the field may be voluntary carrier features (inferred). Source: [47 CFR § 52.37 - Number portability requirements for wireless providers](https://www.law.cornell.edu/cfr/text/47/52.37), 47 CFR 52.37(c)-(e), (g), (h). Checked 2026-10-01.
[^31]: The FCC's 2023 SIM swap and port-out fraud rules require wireless providers to immediately notify customers whenever a SIM change or port-out request is made on their accounts. Source: [FCC Adopts Rules to Protect Consumers' Cell Phone Accounts (news release)](https://docs.fcc.gov/public/attachments/DOC-398483A1.txt), News release, rule summary paragraph. Checked 2026-10-01.
[^32]: The federal port-out fraud protections in 47 CFR 52.37 apply to CMRS (wireless) providers, including resellers of wireless service, and not to wireline or VoIP providers. Source: [47 CFR § 52.37 - Number portability requirements for wireless providers](https://www.law.cornell.edu/cfr/text/47/52.37), 47 CFR 52.37(a). Checked 2026-10-01.
[^33]: 47 CFR 52.37(b) requires wireless providers to use secure methods to authenticate a customer before effectuating a port-out request. Source: [47 CFR § 52.37 - Number portability requirements for wireless providers](https://www.law.cornell.edu/cfr/text/47/52.37), 47 CFR 52.37(b). Checked 2026-10-01.
[^34]: In DA 24-649 the Wireline Competition Bureau waived compliance with the SIM swap and port-out fraud rules that were not subject to OMB review until OMB completes its review, so that all the rules take effect on one date. Source: [Protecting Consumers from SIM-Swap and Port-Out Fraud, Order (DA 24-649)](https://docs.fcc.gov/public/attachments/DA-24-649A1.txt), DA 24-649, para. 12. Checked 2026-10-01.
[^35]: The FCC defines a simple port as one that involves no unbundled network elements, covers an account with only a single line, has no complex switch translations (such as Centrex, ISDN, AIN, remote call forwarding or multiple services on the loop) and involves no reseller. Source: [Local Number Portability Porting Interval and Validation Requirements, Report and Order and Further Notice of Proposed Rulemaking (FCC 09-41)](https://docs.fcc.gov/public/attachments/FCC-09-41A1.txt), FCC 09-41, para. 11 n.5 (per text edition; footnote number unverified against PDF). Checked 2026-10-01.
[^36]: US carriers must complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested. Source: [47 CFR § 52.35 - Porting Intervals](https://www.law.cornell.edu/cfr/text/47/52.35), 47 CFR 52.35(a). Checked 2026-10-01.
[^37]: Microsoft distinguishes the account PIN, which protects account management and records, from a BTN freeze PIN, which lets an authorized user unfreeze the account for maintenance such as porting. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Porting wizard - New (U.S. & Canada) > Account information. Checked 2026-10-01.
[^38]: The Teams port wizard requires the account PIN for every mobile number being ported. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Account information (new wizard); Add account information item 2 (all-regions wizard). Checked 2026-10-01.
[^39]: For Teams Calling Plan port-ins, the port request is rejected after submission if the BTN does not match the current provider's records or if the account has a freeze that was not removed. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Porting wizard - New (U.S. & Canada) > Billing telephone number (BTN). Checked 2026-10-01.
[^40]: When a Teams port order is Canceled, starting a new port order reuses no prior validations or documents. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > status table row Canceled. Checked 2026-10-01.
[^41]: In Teams admin center Order history, the port order status Exception means the carrier that currently owns the numbers rejected the order, typically for incorrect LOA information such as PIN or ZIP code, and Microsoft support corrects and resubmits it. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What's the status of your port orders? > status table row Exception. Checked 2026-10-01.
[^42]: In a Teams full port all numbers on the BTN, including the BTN, move to Microsoft, and the account with the current provider is closed. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Billing telephone number (BTN); Add account information > Port details Option 1. Checked 2026-10-01.
[^43]: The new Teams US and Canada port wizard groups numbers by account, service provider and type, and a separate port request must be submitted for each group. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Porting wizard - New (U.S. & Canada) > Phone numbers, item 2. Checked 2026-10-01.
[^44]: In a Teams partial port that includes the account's BTN, the admin may designate a number that is not being ported as the replacement BTN for the account that stays open; designating one is optional. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), Billing telephone number (BTN); Add account information > Port details Option 2. Checked 2026-10-01.
[^45]: If the current carrier rejects a Teams port request, Microsoft directs admins to the Phone Number Service Center (TNS Service Desk) and to update an existing case rather than open a new one. Source: [Transfer phone numbers to Microsoft Teams](https://learn.microsoft.com/en-us/microsoftteams/phone-number-calling-plans/transfer-phone-numbers-to-teams), What happens next. Checked 2026-10-01.
[^46]: Telnyx notes that the BTN/ATN is typically not printed on a bill copy except for wireless or toll-free ports, and advises requesting the CSR from the carrier to find it. Source: [BTN or ATN Mismatch Error](https://support.telnyx.com/en/articles/1130610-btn-or-atn-mismatch-error), How to fix. Checked 2026-10-01.
[^47]: Telnyx identifies submitting numbers from multiple accounts in one request, and a reseller's end customer submitting their own BTN instead of the reseller's, as causes of BTN/ATN mismatch rejections. Source: [BTN or ATN Mismatch Error](https://support.telnyx.com/en/articles/1130610-btn-or-atn-mismatch-error), What causes the error. Checked 2026-10-01.
[^48]: Twilio error 22158 means the losing carrier rejected the requested target port date, commonly because it falls on a public holiday or the carrier's maintenance window; the fix is to resubmit with another date. Source: [22158: Port In Error - Port Date Rejected](https://www.twilio.com/docs/api/errors/22158), Error 22158 > Possible causes; Possible solutions. Checked 2026-10-01.
[^49]: Twilio's PortIn API exposes per-number rejection_reason and rejection_reason_code fields when a carrier declines a number, plus not_portability_reason_code for numbers that cannot be ported. Source: [PortIn resource](https://www.twilio.com/docs/phone-numbers/port-in/port-in-request-api), PortIn resource > phone number properties. Checked 2026-10-01.
[^50]: Twilio's PortIn API requires the target port-in date to be at least 7 days in the future for US ports and does not guarantee the date, which depends on the losing carrier. Source: [PortIn resource](https://www.twilio.com/docs/phone-numbers/port-in/port-in-request-api), PortIn resource > target_port_in_date. Checked 2026-10-01.
[^51]: A Twilio PortIn request must reference at least one uploaded document of type Utility Bill. Source: [PortIn resource](https://www.twilio.com/docs/phone-numbers/port-in/port-in-request-api), PortIn resource > documents. Checked 2026-10-01.
[^52]: Verizon Number Lock prevents a mobile number from being moved, and the customer must turn it off (for example by dialing *611 or in My Verizon) before porting out. Source: [Move your mobile number to another carrier FAQs](https://www.verizon.com/support/port-out-faqs/), FAQ: Number Lock. Checked 2026-10-01.
[^53]: A Verizon Number Transfer PIN expires after 7 days and is used together with the Verizon account number to authorize the new carrier's port. Source: [Move your mobile number to another carrier FAQs](https://www.verizon.com/support/port-out-faqs/), FAQ: Number Transfer PIN. Checked 2026-10-01.
[^54]: Zoom warns that a port may be rejected if alarm monitoring services are on any of the numbers, until those services are moved or stopped. Source: [Best practices when porting numbers](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061279), Best practices when porting numbers. Checked 2026-10-01.
[^55]: Zoom automatically cancels a port request when the customer does not respond within 15 business days. Source: [Number Porting and Management Field Guide: Troubleshooting and FAQ](https://library.zoom.com/zoom-workplace/zoom-phone/number-porting-and-management-field-guide/troubleshooting-and-faq), Troubleshooting and FAQ > cancellation. Checked 2026-10-01.
[^56]: Zoom requires a bill copy dated within the last 45 days for port requests, and notes that some regions require 30 days or 3 months. Source: [Number Porting and Management Field Guide: Troubleshooting and FAQ](https://library.zoom.com/zoom-workplace/zoom-phone/number-porting-and-management-field-guide/troubleshooting-and-faq), Troubleshooting and FAQ > bill copy. Checked 2026-10-01.
[^57]: Zoom states that only the current provider can remove a lock or freeze on the account, so the customer must contact that provider directly. Source: [Number Porting and Management Field Guide: Troubleshooting and FAQ](https://library.zoom.com/zoom-workplace/zoom-phone/number-porting-and-management-field-guide/troubleshooting-and-faq), Troubleshooting and FAQ > account freeze. Checked 2026-10-01.
[^58]: Zoom says rescheduling a port activation means withdrawing the existing order and submitting a new one, which restarts the process. Source: [Number Porting and Management Field Guide: Troubleshooting and FAQ](https://library.zoom.com/zoom-workplace/zoom-phone/number-porting-and-management-field-guide/troubleshooting-and-faq), Troubleshooting and FAQ > rescheduling / FOC. Checked 2026-10-01.
[^59]: Zoom notes that toll-free port dates typically cannot be changed after the FOC is issued. Source: [Number Porting and Management Field Guide: Troubleshooting and FAQ](https://library.zoom.com/zoom-workplace/zoom-phone/number-porting-and-management-field-guide/troubleshooting-and-faq), Troubleshooting and FAQ > FOC / toll-free. Checked 2026-10-01.