Establishing secure connection…Loading editor…Preparing document…

Number Porting Request

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

NUMBER PORTING REQUEST

WHEREAS, Requesting Party: (hereinafter "Requesting Party") requests transfer (porting) of one or more telephone numbers to Receiving Provider: ; and

WHEREAS, Requesting Party certifies it is the authorized account holder or authorized agent for the account identified below and authorizes the release of account information necessary to complete the porting request; and

WHEREAS, Receiving Provider agrees to coordinate the porting process with the current service provider and to use commercially reasonable efforts to minimize service interruption in accordance with the terms set forth in this Number Porting Request.

Porting Details

Account Name on Donor Provider Account:

Numbers to Be Ported

Enter each number to be ported below. Include service type and the account identifier associated with each number where required.

Telephone Number:   Service Type:

Telephone Number:   Service Type:

Telephone Number:   Service Type:

If more than three numbers, attach an additional signed list with the same fields and initial here:

Receiving Provider Contact

Desired Porting Schedule

Desired Port Date:   Preferred Window Start:   End:

Authorization and Certification

By signing below, Requesting Party certifies that it is the authorized account holder or authorized agent of the account identified in this request and grants Receiving Provider and its agents permission to request and obtain any information from the current provider that is necessary to effectuate the porting of the listed telephone numbers. Requesting Party authorizes the release of billing, service and call-detail information to the extent reasonably necessary to complete the porting transaction.

Requesting Party acknowledges that porting may result in service interruption, loss of features, or temporary unavailability of emergency services and agrees that Receiving Provider and its agents shall not be liable for incidental or consequential damages arising from porting unless caused by Receiving Provider's gross negligence or willful misconduct. Requesting Party further agrees to indemnify and hold harmless Receiving Provider for claims arising from false or misleading information provided in this request.

Scope of Work

Payment Terms

Porting Fee Amount: $

Late Payment Fee:

Term and Termination

Agreement Effective Date:   Termination Date (if any):

Either party may terminate this Agreement for material breach if such breach is not cured within the notice period set forth above. Termination does not relieve Requesting Party of any obligations arising prior to the effective date of termination, including payment obligations.

Confidentiality

Each party agrees that it will not disclose Confidential Information of the other party except to its employees, agents, or contractors who have a need to know and who are bound by confidentiality obligations at least as restrictive as those set forth herein. Confidential Information excludes information that is publicly available through no breach of this Agreement, independently developed without use of the other party's Confidential Information, or rightfully obtained from a third party without restriction.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state or jurisdiction specified by Receiving Provider for dispute resolution:

Entire Agreement

This Number Porting Request, together with any attachments or addenda signed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or communications, whether oral or written. Any amendment must be in writing and signed by authorized representatives of both parties.

Certifications and Declarations

By checking the boxes below and signing this form, Requesting Party declares under penalty of perjury that the information provided is true and correct, that the numbers listed are to be ported and are not subject to pending transfers or disputes that would prevent porting, and that Requesting Party authorizes the transfer.

Additional Instructions / Notes

Requesting Party — Printed Name

Printed Name:

By:

Date:

Receiving Provider — Printed Name

Printed Name:

By:

Date:

Enter text✕

What a Number Porting Request Is and When It’s Used

A Number Porting Request is a formal authorization submitted by a subscriber or authorized agent to transfer one or more telephone numbers from an existing (losing) carrier to a new (gaining) carrier. The form captures account details, the specific numbers to move, verification credentials, preferred port dates, and the subscriber’s authorization to permit the transfer and associated billing changes.

Why a Clear Request Matters

A correctly completed Number Porting Request reduces service interruptions, prevents billing errors, and documents consumer consent. It creates an auditable record useful for carrier verification, dispute resolution, and regulatory compliance while preserving continuity of voice and data services.

Why a Clear Request Matters

Who Typically Prepares and Receives This Request

Each party has a defined role: the subscriber authorizes, the gaining carrier submits, and the losing carrier validates before the cutover is scheduled.

  • Account administrators and business owners who control billing and service contracts for the telephone numbers.
  • Managed service providers and MSP telecom teams handling multi-site or multi-number migrations.
  • Gaining and losing carrier provisioning or porting departments that validate and execute the transfer.

Step-by-Step: Submitting a Number Porting Request

Follow these steps in order to minimize delays and ensure carriers can validate the request quickly.

  • 01
    Gather Documents: Collect account statements, bill copy, and any porting PINs.
  • 02
    Complete Form: Fill every required field and sign authorization.
  • 03
    Submit to Gaining Carrier: Send the request with attachments per the carrier’s submission method.
  • 04
    Confirm and Schedule: Coordinate a cutover date and confirm losing carrier acceptance.

How Number Porting Works Between Carriers

Porting is a coordinated exchange of authorization and validation messages between the gaining and losing carriers, followed by a scheduled cutover that transfers service records and billing.

  • Gaining Carrier Submission: Gaining carrier sends a port request to the losing carrier.
  • Validation Check: Losing carrier verifies account details and PIN consistency.
  • Scheduling: Carriers agree a cutover date and time window.
  • Completion Notice: Both carriers confirm completion and notify the subscriber.

Configuring an Online Porting Workflow

Map the key fields and verification steps when creating a digital workflow to capture accurate data and preserve an audit trail.

Field Online Setting
Account Number Masked numeric field with validation
Porting PIN Secure text field, encrypted at rest
Numbers List Repeating line item with format enforcement
Signature Qualified eSignature field with timestamp

Platform and File Requirements for Digital Submission

Retain the digitally signed packet and audit trail to support disputes, compliance reviews, and internal records.

  • Accepted Formats: PDF, DOCX, or scanned image
  • Authentication: Email or SMS code for signer verification
  • Integrations: CRM and ticketing system connectors

Essential Elements to Include in a Professional Request

A complete Number Porting Request combines identity data, explicit authorization, and technical details so carriers can validate and process the transfer with minimal manual follow-up.

Subscriber Authorization

A signed authorization statement that allows the gaining carrier to request the port and instructs the losing carrier to release the number.

Account Credentials

Losing carrier account number and any porting PIN or password used for account-level verification.

Number Inventory

A precise list of telephone numbers to port, each on its own line, using consistent formatting for routing systems.

Service Details

Specification of service type (e.g., mobile, landline, toll-free) and any facility or DID assignments relevant to routing.

Preferred Port Date

A requested cutover date and time window, with alternative options for scheduling flexibility.

Contact Information

Authorized requester name, title, email, and phone for provisioning and troubleshooting during the port.

Required Verification Data at a Glance

Account Name: Exact legal name
Account Number: Carrier account ID
Service Address: Street, city, state, ZIP
Numbers to Port: List of telephone numbers
Porting PIN: Numeric or alphanumeric code
Signer Contact: Name, phone, email

Common Preparation Pitfalls to Avoid

  • Providing an account name that differs from the carrier record, which triggers verification rejections and delays.
  • Submitting numbers in inconsistent formats or concatenated lists that carriers cannot parse automatically.
  • Omitting the porting PIN or using an expired PIN, which typically causes an immediate denial.
  • Failing to include a signed authorization or using initials instead of an authorized signature, resulting in requester rejection.

Risks and Consequences of an Incorrect Request

Service Interruption: Temporary loss of voice/data service
Billing Errors: Duplicate or misdirected charges
Unauthorized Porting: Risk of port-out fraud if credentials exposed
Regulatory Notices: Carrier or regulator investigation
Customer Impact: Missed calls and operational disruption
Dispute Resolution: Time-consuming reclamation process

Typical Timelines and Processing Expectations

Processing times vary by service type and carrier; plan for verification steps and scheduling windows when setting a target cutover date.

Wireless Porting:

Often completes within 1 business day

Landline Porting:

Commonly requires 2–7 business days

Toll-Free Numbers:

May need additional routing updates and up to several weeks

Validation Response:

Losing carrier typically responds within carrier SLAs

Resubmission Window:

Allow 24–48 hours to correct rejected requests

Practical Tips for Faster, Safer Porting

Adopt consistent formats, secure credential handling, and pre-checks before submission to reduce back-and-forth with carriers.

Use Exact Account Data
Match the account name, number, and address to the losing carrier’s records to avoid verification rejections.
Provide Clear Number Lists
One number per line in a standard US format prevents parsing errors during automated intake.
Secure Credentials
Transmit porting PINs and account IDs using encrypted channels and limit access to authorized staff.
Keep an Audit Trail
Retain signed requests, email confirmations, and carrier responses for dispute resolution and compliance.

How to Amend or Revise a Submitted Request

If you need to update a porting request after submission, follow these coordinated steps to avoid duplicate attempts or race conditions.

01

Contact Gaining Carrier:

Alert to pending change and provide revised details.
02

Pause Processing:

Request a hold on the porting workflow if possible.
03

Submit Revised Request:

Include original reference number and redline of changes.
04

Confirm with Losing Carrier:

Ensure losing carrier acknowledges the revised authorization.
05

Reschedule Cutover:

Agree a new date that fits both carriers.
06

Document Changes:

Archive both original and revised authorizations with timestamps.

Real-World Scenarios That Illustrate Common Porting Paths

Two illustrative examples show how a complete request prevents delays and preserves service during migration.

Small Business Migration

A retail chain ready to consolidate phone service used a single signed authorization with exact account numbers

  • the gaining carrier validated matching PINs quickly
  • the cutover occurred overnight with minimal downtime and clear audit records for billing reconciliation.

Clinic Toll-Free Transfer

A healthcare clinic needed a toll-free number moved and included HIPAA contact and signed authorization

  • additional documentation proved ownership of the toll-free record
  • carriers scheduled a coordinated port and preserved voicemail continuity for patient communications.

eSignature Provider Comparison for Submitting Porting Requests

Comparison of common eSignature providers to consider when digitizing a Number Porting Request; signNow is listed first for consistency in vendor comparisons.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Frequently Asked Questions and Troubleshooting

Answers to common questions about rejected ports, missing PINs, and dispute steps to restore numbers or correct records.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users