DEV Community

Jordan Tate
Jordan Tate

Posted on Fully Autonomous

Bring your own Twilio number: the case for owning your phone number, not renting it from your CRM

Your sales number is printed on trucks, business cards and a few hundred Google listings. Customers have it saved in their phones. Then you switch CRMs, and you learn the number was never in your account. It sat in your old vendor's.

Disclosure: I work at a CRM company that connects to Twilio for texting.

This post covers what porting rules protect, what they leave to contracts, why 10DLC registration is harder to move, and a setup where the CRM is a client of your phone account, not its owner. Every fact links to its source.

What the porting rules guarantee

The FCC's consumer guide is short. If you change providers and stay in the same geographic area, you keep your number, and porting "can be done between wireline, IP and wireless providers." It also says:

  • Simple ports take one business day. That is an FCC rule. A simple port generally means one line and no complex switching changes. Between wireless providers, the phone may work within a few hours. Wireline to wireless may still take a few days.
  • Debt is not a veto. Once you request service from a new company, the old one cannot refuse to port, even if you owe a balance or a termination fee.
  • Fees can exist. Companies may charge to port, and the guide suggests asking for a waiver.
  • Don't cancel first. Start service with the new company before you end the old one.
  • Moving towns can break it. A new geographic area may mean you can't keep the number.

All of that is about you and a carrier. The guide does not cover a number that sits in a software vendor's carrier account. In that case, your contract with the vendor and the vendor's own process decide what happens. That is my reading, not legal advice.

When the number lives in someone else's account

Start with Twilio itself. Even in your own Twilio account, the owner of record a new carrier sees is Twilio. Twilio's port-away guide tells you to enter "Twilio, Inc." as the business name on the old account (Twilio). What you control is the account around the number:

  • The new carrier asks for the last 8 characters of your Account SID.
  • US local numbers need a port-out PIN, which you request from porting@twilio.com.
  • Twilio emails you to confirm the port is legit. The recipient must have the admin or billing role.
  • If your details don't match Twilio's records, the port is rejected.
  • Numbers must stay active until the port finishes. Release one early and the port fails.

Now put a vendor in the middle. If the CRM bought the number inside its own Twilio account, the SID, the PIN request and the confirmation email all belong to the vendor. You need their help to leave.

Some vendors document that process. Here is what I could find:

  • HubSpot. Its knowledge base says porting a number in "makes HubSpot the owner of that phone number." Porting out is supported. Your new provider asks HubSpot's carrier, Twilio, for the CSR, PIN or account details, and that can take up to five business days.
  • HighLevel. Numbers can move from its LC Phone service into your own Twilio account, coordinated by HighLevel Support. It quotes about 1 to 2 business days once it has all the details. Call recordings and voicemails do not move with the number (HighLevel).
  • Close. Its help center says ported numbers can't be deleted from Close, and to contact support to port one out. Deleting a rented number releases it from your account (Close).

I did not find published port-out pages for other CRMs, so I'm not listing them. If a vendor has no such page, ask for its port-out steps in writing before you sign.

One more case. Twilio's preferred setup for software vendors puts each customer in its own subaccount under the vendor's main account (Twilio ISV guide). Twilio's docs also say that if the main account is ever suspended, its subaccounts are suspended too. Closing a subaccount releases all of its phone numbers, and closed subaccounts are deleted after 30 days by default (Twilio). Your number's fate is tied to the vendor's billing standing and offboarding script.

10DLC registration is the harder thing to move

Under A2P 10DLC, a brand is the business that sends, and Twilio says each brand "belongs to a single Customer Profile" (Twilio ISV guide). Campaigns attach to that brand, and numbers attach to campaigns.

What carries over to a new platform:

  • Campaigns don't span vendors. Twilio states it is not possible to use a single campaign across multiple vendors (Twilio).
  • Migration exists, but not for most of us. TCR's CNP Migration Tool can move campaigns between providers without re-registration. It is for Campaign Service Providers who register directly with TCR. Twilio says direct customers can't register with TCR; they register through Twilio's Trust Hub (Twilio).
  • Moving the number doesn't move the registration. HighLevel's migration guide says A2P status is tied to the account or sub-account, not only the number. It tells you to verify or redo registration at the destination (HighLevel).

Re-registering costs money and calendar time. At Twilio every campaign pays a $15 vetting fee that is not refunded, brands pay $4.50 to register, and a standard campaign can sit in vetting for up to 5 business days (Twilio). The full fee breakdown by provider is in this 10DLC registration guide.

Opt-outs are the quiet risk. Twilio warns that restructuring into subaccounts resets the opt-out records it manages, because those settings live at the account level. Its fix: keep an up-to-date opt-out list before you restructure (Twilio ISV guide). If your STOP records live only in a vendor's account, ask how you would get them out.

What to keep in your own name

  • The provider account itself, with you as the admin and billing user
  • The phone numbers, bought or ported into that account
  • The A2P brand and campaigns, registered under your legal name and EIN
  • Your own opt-out list, exported or mirrored on every STOP
  • The short-link domain your texts use
  • The webhook endpoint that receives inbound messages

The architecture

Flip the usual setup. Your provider account is the hub, and the CRM is one client of it.

  1. Your own account. Twilio, or another provider. You hold the main credentials.
  2. Scoped keys for the CRM. Twilio's API keys can be revoked whenever you like, and Standard keys can't touch the Accounts or Keys resources. Restricted keys narrow access further (Twilio). Give each tool its own key. Leaving a vendor then means revoking one key.
  3. Subaccounts if you want separation. Under your main account they keep each brand's or team's usage and numbers apart (Twilio). Here you are the main account, so the suspension and closure rules work for you.
  4. Inbound webhooks to your endpoint. Twilio signs each request with an X-Twilio-Signature header, built with HMAC-SHA1 using your account auth token as the key (Twilio). Store the message, then forward it to the CRM.
  5. Your own short-link domain. Twilio's link shortening uses your own branded domain, and you must own that domain (Twilio). Links keep working after a CRM change.

Here is a small inbound handler in Node with Express. It checks the signature, writes the message to your own store first, mirrors opt-outs, then hands off to the CRM.

const express = require('express');
const twilio = require('twilio');
const { MessagingResponse } = twilio.twiml;

const app = express();
app.use(express.urlencoded({ extended: false }));

const AUTH_TOKEN = process.env.TWILIO_AUTH_TOKEN;
// Must match the URL set in Twilio exactly
const WEBHOOK_URL = 'https://hooks.example.com/sms';

// Twilio's default English opt-out keywords for long codes
const OPT_OUT = new Set([
  'STOP', 'UNSUBSCRIBE', 'END', 'QUIT',
  'STOPALL', 'REVOKE', 'OPTOUT', 'CANCEL',
]);

app.post('/sms', async (req, res) => {
  const signature = req.get('X-Twilio-Signature') || '';
  if (!twilio.validateRequest(AUTH_TOKEN, signature, WEBHOOK_URL, req.body)) {
    return res.status(403).send('Invalid signature');
  }

  const { MessageSid, From, To, Body = '' } = req.body;

  // 1. Your record first
  await db.messages.insert({ sid: MessageSid, from: From, to: To, body: Body });

  // 2. Opt-outs into a list you own
  if (OPT_OUT.has(Body.trim().toUpperCase())) {
    await db.optOuts.upsert({ phone: From, at: new Date() });
  }

  // 3. Then the CRM
  forwardToCrm(req.body).catch(console.error);

  // Empty TwiML: no auto-reply
  res.type('text/xml').send(new MessagingResponse().toString());
});

app.listen(3000);
Enter fullscreen mode Exit fullscreen mode

db and forwardToCrm are placeholders. The keywords come from Twilio's Advanced Opt-Out docs, which also note Twilio handles them on long codes by default; the local copy is for you. Use the SDK's validator, not your own, since webhook parameters can change without notice (Twilio).

Before you sign up for any CRM with texting

  • [ ] Whose provider account holds the numbers: yours or the vendor's?
  • [ ] Can you connect your own Twilio (or other provider) account with an API key?
  • [ ] Is there a published, written port-out process? How many business days?
  • [ ] Who receives the port-out confirmation and PIN?
  • [ ] Is the A2P brand registered under your legal name and EIN, and can you see its IDs?
  • [ ] If you leave, does the registration move, or do you re-register and pay vetting again?
  • [ ] Can you export your opt-out list at any time?
  • [ ] Do inbound webhooks go to a URL you control, or only into the vendor?
  • [ ] Do texts use a short-link domain you own?
  • [ ] Do call recordings and voicemails export before you leave?
  • [ ] What happens to your numbers if the vendor closes or suspends your account?

If the answers are "yours" across the board, switching CRMs later costs you an afternoon of rewiring keys and webhooks, not a new phone number.

For what it's worth, the CRM I work on, Conduyt, works this way: it connects to your own Twilio or Project Blue account, so the numbers stay in your name.

Jordan Tate is VP of Customer Relations at Conduyt, a flat-price CRM for small sales teams. This post was drafted with AI assistance.

Top comments (0)