What validates authorization?

A signed authorization that matches the account name and includes account number typically validates ownership. Carriers may also accept a formal letter on account letterhead or an online eSignature if it meets ESIGN requirements: intent, consent, attribution, and retention.

Can I eSign the agreement?

Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. §7001) and state UETA laws where adopted, provided the signature meets intent, consent, attribution, and record retention standards.

Is notarization ever required?

Some carriers or states may require notarized letters for certain high-risk ports or for specific account types. Check carrier policy and state notary rules before scheduling the port.

What if the port fails?

Follow the rollback procedures defined in the agreement and document the failure. Open a carrier dispute ticket and preserve logs and timestamps for investigation and potential financial remediation.

How long should I retain records?

Keep port agreements for the active term plus at least three years; retain telecom and tax-relevant records per IRS guidance (IRC §6501(a)) and extend retention where industry rules such as HIPAA apply.

Who can sign on behalf of a company?

An authorized signatory with authority on the provider account should sign. If authority is delegated, include a delegation statement or supporting documentation that carriers recognize.

Voice Port Agreement

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

Voice Port Agreement

This Voice Port Agreement ("Agreement") is entered into as of by and between:

Client Name: Client Address: Provider Name: Provider Address:

Recitals

WHEREAS, Provider is in the business of arranging and executing voice number porting, provisioning and related telecommunications services, including coordination with existing and new carriers and database provisioning; and

WHEREAS, Client desires to transfer and port certain telephone numbers and associated routing (collectively, "Numbers") to Provider or to a carrier designated by Provider, and Provider has the requisite experience and authority to perform such work; and

WHEREAS, the parties wish to set forth the terms and conditions governing Provider's performance of Voice Port services and Client's payment obligations.

Scope of Work

Provider shall perform the porting and associated services described below. Client authorizes Provider to act as Client's agent solely for the limited purpose of requesting, coordinating and completing Number porting and related provisioning tasks.

Porting Details and Services (describe Numbers, carriers, and tasks): Estimated Port Windows and Milestones:

Payment Terms

Client shall pay Provider for Services pursuant to the following terms.

Total Fee for Services (USD): Payment Schedule and Terms: Late Payment Fee: Invoicing Contact Name & Email/Phone:

Term and Termination

This Agreement commences on and continues until unless earlier terminated in accordance with this Agreement.

Termination Notice Period (days):

Either party may terminate for material breach if the breaching party fails to cure the breach within the notice period specified above from receipt of written notice. Provider may suspend Services immediately if Client fails to pay undisputed amounts when due; suspension shall not excuse Client's payment obligations.

Confidentiality

Each party shall maintain in confidence all non-public information received from the other party that is designated confidential or that reasonably should be understood to be confidential given the nature of the information ("Confidential Information"). Confidential Information excludes information that is (a) publicly known without breach of this Agreement; (b) rightfully received from a third party without restriction; (c) independently developed without use of the other party's Confidential Information; or (d) required to be disclosed by law, provided the disclosing party gives prompt written notice and cooperates in any lawful effort to limit disclosure. The receiving party shall use Confidential Information solely to perform its obligations under this Agreement and shall take commercially reasonable measures to protect such information.

Representations, Compliance and Authorization

Client represents and warrants that it is the authorized account holder for the Numbers or otherwise has the legal right to request porting, and agrees to provide all necessary letters of authorization, account information and releases required by existing carriers. Provider represents that it will perform Services consistent with industry standards and applicable carrier requirements.

Indemnification and Limitation of Liability

Each party shall defend, indemnify and hold harmless the other party from third-party claims arising out of that party's breach of this Agreement, willful misconduct or negligence. Except for breach of confidentiality obligations, indemnification obligations or liability for willful misconduct, neither party shall be liable to the other for incidental, consequential, punitive or special damages. The aggregate liability of each party for all claims arising under this Agreement shall not exceed the amounts actually paid by Client to Provider under this Agreement in the six (6) months preceding the claim.

Force Majeure

Neither party shall be liable for delay or failure to perform caused by events beyond its reasonable control, including acts of God, strikes, outages, carrier failures, governmental actions, or pandemics. The affected party shall promptly notify the other and use commercially reasonable efforts to resume performance.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to its conflict of laws principles. Exclusive jurisdiction for disputes will be in the state or federal courts within that state.

Entire Agreement; Amendments

This Agreement, including any exhibits, schedules and attachments executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, understandings and communications. No amendment shall be effective unless made in writing and signed by authorized representatives of both parties.

Notices

Client Notice Contact: Provider Notice Contact:

Miscellaneous

If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. The parties are independent contractors and nothing shall create an agency, partnership, joint venture or employment relationship except as expressly set forth herein.

Client:

By:

Date:

Provider:

By:

Date:

What the Voice Port Agreement Is and When it Applies

A Voice Port Agreement documents the transfer or activation of a telephone number or call routing from one provider or service to another and establishes responsibilities for porting, testing, and service continuity. It typically records the parties involved, the numbers or ranges to be ported, required authorization (customer signature or carrier letter), scheduling windows, and acceptance criteria for successful cutover. The agreement reduces confusion during migration, sets expectations for downtime, and creates a record for dispute resolution and billing allocation between carriers, service providers, and enterprise customers.

Why a Clear Voice Port Agreement Matters

A concise agreement minimizes service disruption, clarifies who authorizes the port, and protects parties from billing or liability disputes by documenting timelines, testing procedures, and fallback plans. It also creates a reproducible record useful for troubleshooting and regulatory compliance, including retention for tax and telecom audit purposes.

Who Typically Prepares and Signs a Voice Port Agreement

Identify the primary users and stakeholders who must be involved when creating and approving the agreement.

Network administrators and telecom managers responsible for port scheduling and validation.
Service providers or carriers who accept or execute the port request and confirm routing changes.
Authorized account holders or billing contacts who give written consent to transfer numbers.

These roles align operational, billing, and customer-authority responsibilities to ensure a controlled porting process with defined accountability.

Essential Data Elements to Include

Customer Name: Legal entity name

Account Number: Current provider account ID

Numbers to Port: Specific DN or DID ranges

Authorization: Signed consent or letter

Cutover Window: Proposed date/time block

Acceptance Tests: Pass/fail criteria

Step-by-Step: Completing a Voice Port Agreement

Follow these sequential steps to prepare a complete, enforceable Voice Port Agreement that reduces migration risk and meets carrier requirements.

01

Collect authorization: Obtain signed customer consent and current account details.
02

List numbers: Specify exact DIDs, blocks, or ranges to port.
03

Schedule port: Agree on a mutually acceptable cutover window.
04

Define tests: State acceptance criteria and rollback procedures.

Configuring Online Workflows for Voice Port Agreements

Set up a digital workflow to collect authorization, schedule ports, and automate notifications to stakeholders.

Field	Configuration
Authorization Capture	Require signer name, title, and eSignature
Number Upload	Allow CSV import for bulk DIDs
Scheduling	Use timezone-aware date/time picker
Notifications	Email alerts for confirmation and failures

How a Porting Request Moves Through the System

This overview clarifies the typical routing steps from request submission to post-cutover verification.

Request Submission: Sender uploads agreement and authorization to carrier or aggregator.
Validation: Losing carrier confirms account and ownership.
Scheduling: Carriers agree on a coordinated cutover window.
Execution & Test: Port is executed and parties run acceptance tests.

Digital Signing and eSubmission Requirements

Digital port agreements require reliable eSignature, secure attachments, and traceable audit trails to meet carrier and regulatory needs.

File Formats: PDF or DOCX
Authentication: Email or SMS code; stronger MFA for high-risk ports
Integrations: CRM and ticketing systems for automatic routing

Use platforms that produce timestamped audit trails, retain a signed copy, and support CSV import for bulk number lists to streamline processing.

Typical Timelines and Scheduling Expectations

Porting timelines vary by carrier and number type; plan for validation, scheduling, execution, and verification periods when arranging a port.

Validation Period:

1–5 business days for account and ownership checks

Scheduling Window:

1–3 weeks to coordinate cutover with involved carriers

Execution Time:

Often completed within hours on the scheduled date

Verification Window:

24–72 hours for acceptance testing post-cutover

Dispute Resolution:

Allow 7–30 days for carrier investigation if issues arise

Common Mistakes That Cause Port Delays

Incorrect or incomplete account numbers submitted to the losing carrier.
Mismatched legal names between authorization and carrier records.
Failure to list every individual DID or range precisely.
No agreed rollback plan for failed cutovers, causing extended outages.

Risks and Consequences of a Flawed Agreement

Service Disruption: Downtime and lost calls

Billing Disputes: Dual billing or incorrect charges

Regulatory Exposure: Potential complaints to telecom regulators

Contract Liability: Breach claims under service agreements

Delayed Revenue: Missed or deferred customer billings

Operational Cost: Additional technician time and expedited fees

eSignature Vendor Comparison for Executing a Voice Port Agreement

Compare basic plan features and compliance capabilities when choosing an eSignature provider to collect authorization and store signed port agreements.

	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 trial	No	No	No	No
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Practical Examples of Voice Port Agreements in Use

Two real-world scenarios showing how a Voice Port Agreement supports migration and dispute handling.

Enterprise Migration

A regional retailer migrated 1,200 DIDs using a single agreement to document cutover steps and testing

The carrier required signed authorization for each block
The standardized agreement sped validation and reduced billing disputes during the transition by creating a single source of truth.

Provider Consolidation

A healthcare clinic consolidated numbers across campuses and included HIPAA routing terms in the port agreement

Legal reviewed retention and logging requirements
The explicit acceptance tests and fallback plan prevented call loss during peak hours and supported post-migration compliance audits.

Best Practices for Accurate, Efficient Voice Porting

Adopt these practices to minimize risk, accelerate approvals, and keep stakeholders aligned throughout the porting lifecycle.

Confirm Account Authority

Verify the account holder name and billing contact directly with the losing carrier before submitting authorization to prevent ownership rejection.

Use Exact Number Lists

Provide explicit DIDs or contiguous ranges in machine-readable format (CSV) to reduce transcription errors during provisioning.

Define Acceptance Tests

Agree on measurable tests and success criteria in advance, and include rollback steps and responsible contacts.

Retain Documentation

Store signed agreements, emails, and logs with audit trails for dispute resolution and regulatory compliance.

Frequently Asked Questions About Voice Port Agreements

Answers to common operational and legal questions encountered during number porting and agreement execution.

Need help? Contact support

What validates authorization?
A signed authorization that matches the account name and includes account number typically validates ownership. Carriers may also accept a formal letter on account letterhead or an online eSignature if it meets ESIGN requirements: intent, consent, attribution, and retention.
Can I eSign the agreement?
Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. §7001) and state UETA laws where adopted, provided the signature meets intent, consent, attribution, and record retention standards.
Is notarization ever required?
Some carriers or states may require notarized letters for certain high-risk ports or for specific account types. Check carrier policy and state notary rules before scheduling the port.
What if the port fails?
Follow the rollback procedures defined in the agreement and document the failure. Open a carrier dispute ticket and preserve logs and timestamps for investigation and potential financial remediation.
How long should I retain records?
Keep port agreements for the active term plus at least three years; retain telecom and tax-relevant records per IRS guidance (IRC §6501(a)) and extend retention where industry rules such as HIPAA apply.
Who can sign on behalf of a company?
An authorized signatory with authority on the provider account should sign. If authority is delegated, include a delegation statement or supporting documentation that carriers recognize.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now