How to Configure Twilio Numbers for SMS in TrackDrive

Integrations

Overview

Note: steps performed inside Twilio's own interface
reflect that product as of June 2026 and may differ as
Twilio updates its UI.

Sending SMS from TrackDrive via Twilio requires
four pieces in place: a connected Twilio account,
a Number Pool flagged for SMS, Twilio DIDs
purchased through TrackDrive, and a Twilio A2P
Campaign with the DIDs registered. This article
walks each piece end to end.

Important: do not buy Twilio numbers directly from
the Twilio console. If you already have, TrackDrive
can import them, but buying from inside TrackDrive
lets TrackDrive configure the Twilio-side settings
as the numbers are purchased.

Step 1 (In Twilio): Gather Account SID and Auth

Token

From the Twilio console's top menu, open
Account > API keys and tokens. The Account SID
is visible on the page. Click the eyeball icon to
reveal the Auth Token. Both values are needed in
Step 2.

Step 2 (In TrackDrive): Connect the Twilio

Account

In TrackDrive, open Integrations > Manage
Integrations
from the sidebar, locate the
Twilio card, and click Install. Fill in:

  • Name: a free-form label. If multiple Twilio accounts will be connected (for example one per brand), include the Twilio Account Number in the label.
  • Default Provider: leave off. Keeping TrackDrive as the default provider prevents double inbound charges on Twilio DIDs.
  • Account SID: paste from Step 1.
  • Auth Token: paste from Step 1.

Click Connect Twilio Account. TrackDrive
validates the credentials by calling Twilio's API
and confirming the returned account SID matches
the value entered.

Step 3 (In TrackDrive): Create a Number Pool

for SMS

Open Setup System > Number Pools and click
New Number Pool. SMS-specific settings:

  • Tracking Type: Phone Number Tracking.
  • Name: descriptive, for example <offer> - <pool purpose> - Twilio.
  • Offer: required.
  • Traffic Source: usually blank so the pool can be shared across traffic sources.
  • Number Limit: set to 1; the pool is manually filled with specific area codes.
  • Token Hold Time: leave at 1. Not used for SMS sends.
  • Number Stockpile: leave at 1. Numbers are purchased via a bulk order in Step 4, not via stockpile.
  • Track Unique Visitors: leave at 1.
  • Always Credit Traffic Source: on only if the pool is specifically per-traffic-source.
  • Manage Extra Tokens: add call_type=sms so inbound calls on these DIDs are categorized as SMS for buyer routing.
  • Provider Configuration: select the Twilio account connected in Step 2.
  • Country: USA (Campaign Registry is US and Canada only).
  • Toll-Free Or Local?: Local. Toll-Free SMS approval is a separate Twilio process.
  • Area Code: blank; the CSV bulk order in Step 4 fills specific area codes.
  • Auto Rent Numbers: No.
  • Prefer to dial from matching area code?: Yes.
  • Use any area code in state?: Yes.
  • Area Code to Dial With: leave blank.

Save the pool.

Step 4 (In TrackDrive): Bulk Purchase Twilio

DIDs

The recommended bulk order targets exactly 49
numbers: one per state, in the capital city area
code, excluding Alaska and Hawaii.

Open Setup System > Numbers and click the
Bulk Number Orders tab, then the New Bulk
Order
button. Fill in:

  • Name: descriptive.
  • Telephone Provider: Twilio.
  • Description: optional detail.
  • Offer: select.
  • Number Pool: the pool from Step 3.
  • Traffic Source: blank unless the pool is per-source.
  • Fallback To Any Prefix In State/Province?: check. Specific capital area codes may not be available at purchase time.

Click Next Step, then use the CSV import flow
to load a 49-row CSV (one line per state, capital
area code format), and finally start the purchase.

If Alaska or Hawaii must be included, swap two
rows out for:

1,AK,1907,-9,Alaska
1,HI,1808,-10*,Hawaii

Step 5 (In Twilio): Onboard the SMS Campaign

In the Twilio console open Develop > Messaging >
Onboarding
.

Brand Registration requires a valid FEIN. The
company name must match the IRS registration
exactly. One brand per Twilio account; many
campaigns per brand.

Campaign Registration:

  • A2P Campaign use case: Customer Care fits most sales-followup flows. Some use cases auto-approve; others require manual review.
  • Messaging Service: choose Create new Messaging Service per campaign.
  • Campaign description: be detailed for both Campaign Registry and Twilio reviewers.
  • Sample messages: provide at least two. Example opener: [first_name], Thank you for submitting your quote for a free Medicare Insurance Quote. We will be calling you shortly from [trackdrive_number].
  • Message contents: declare any embedded links or phone numbers.
  • How end users consent: describe the consent mechanism and list the form sites that collect it.
  • Opt-in Keywords / Opt-in Message: only if SMS opt-in is supported on your forms.

Click Create, agree to the Campaign Registry
pass-through fees and the Twilio Vetting Fee, and
note the rate limits (MPS = Messages Per Second).

Step 6 (In Twilio): Register the DIDs to the

Campaign

After the fee-agreement and summary screens in
Step 5, click Continue. Check the DIDs
belonging to this campaign in the Twilio number
inventory and click Register to attach them
to the Messaging Service.

Step 7: Test an Outbound SMS

In TrackDrive, add a test Lead to the Offer that
the SMS pool is attached to. Edit the Lead and
use the manual SMS section to send a message to a
phone you control. If nothing arrives, check:

  • Pool's call_type=sms token is present on the number.
  • The DID is registered to the Messaging Service in Twilio.
  • Campaign status in Twilio is Approved.

If the configuration looks correct but SMS still
fails to deliver, contact TrackDrive support with
the Lead ID and the Twilio Campaign SID.

Contact TrackDrive

Questions?

We're here to help. Reach out and a Voice Marketing Cloud Specialist will get back to you.

Email support@trackdrive.com
Request A Demo

Request A Demo.

See how you can improve your marketing and the customer experience with the Voice Marketing Cloud.

Request a demo