Skip to main content

Bandwidth Toll-Free Verification guide

Updated over a week ago

This guide is designed to streamline the Toll-Free Verification (TFV) process for Bandwidth customers by helping minimize errors and delays. Before submitting a Toll-Free Campaign Brief, please gather all the information listed below and double-check that all of the Toll-Free Numbers (TFNs) associated with your TFV request are located in the correct Bandwidth App account and enabled for Messaging. For further details and FAQs, please see our Toll-Free Verification Handbook.

Bandwidth Customer details

Information about you, the Bandwidth Customer. This is required to properly document your request and keep you updated on its status.

  • Business name (also known as ISV or reseller)

  • Bandwidth App account number (the numeric ID of the account where the TFN is located)

  • Email address (for status updates, if submitting via the Toll-Free Campaign Brief)

Message Sender details

Information about the Message Sender (the end business using the TFN). This is required to comply with Toll-Free Verification requirements.

  • Legal Company Name and Doing Business As (DBA), if they’re different

  • Primary Company Address or Corporate Headquarters

  • Entity Type

  • Business Registration Number (see this article for BRN requirements)

  • Business Registration Type (Employee Identification Number (EIN) in the US, Canadian Business Number (CBN) in Canada, or Companies House in the UK)

  • Business Registration Country (the ISO 3166-1 Alpha-2 country code)

  • URL/website (or any type of online presence, such as review pages, social media, etc.)

  • Privacy Policy link (currently optional, but will be reviewed if included)

  • Terms and Conditions link (currently optional, but will be reviewed if included)

Business Contact details

Information about the Business Contact (at the end business, not the ISV/reseller). This is required to ensure proper association with the campaign and won’t be used to contact the end business during the verification process.

  • First and last name

  • Phone number

  • Email address (either the prefix or the domain should match the company name)

Campaign details

Information about the messaging on the TFN. This is required to validate the campaign's legitimacy.

  • Estimated monthly message volume

  • Amount of numbers you need to verify (explain the use case if using 5 or more TFNs)

  • TFN(s) associated with the request

  • Category that best fits your use case/content (if you have a mixed-use case, please note the changes affecting the opt-in requirements)

  • Detailed description of your use case/content and customer

  • Opt-in collection method (Online, Text to Join, Point of Sale, Other)

  • Opt-in image URL (must link to an image of a webform, paper form, screenshot of the proof of opt-in (if it’s collected verbally), or marketing of a keyword). Compliant opt-in must be separate from other agreements and services, and include:

    • Message sender branding

    • HELP & STOP verbiage

    • Disclosures with message frequency and that data rates may apply

    • Types of messages, to align with selected use case(s)

    • Privacy Policy and Terms & Conditions

  • Supporting information on how the opt-in is collected

  • Examples of production messages the Message Sender intends to send (provide 1-3 variations of the message content)

    • If you have a mixed use case, provide examples of the expected traffic.

TFV submission rejections

After submitting your TFV request, please monitor the generated ticket for status updates, which may include internal errors (e.g., incorrect account number or TFN not enabled for messaging) and/or downstream rejection reasons.

Did this answer your question?