Do you send SMS through Twilio?

While the information on this page typically applies to anybody who sends SMS messages, we can only guarantee that it applies to users who manage their SMS senders and billing through Customer.io. Your mileage might vary if you obtain phone numbers and manage billing through Twilio.

# Getting a phone number

Before you can get a phone number and send SMS messages, you’ll need to register as a sender, which includes several steps—including making sure that your privacy policy and terms and conditions are updated to reflect your SMS-use case.

We’ll help you register as a sender, but it can take 1-2 weeks for carriers to review and approve or deny your request. You need to do the following things before we submit your request to Twilio and respective carriers—so you can register for phone numbers and start sending SMS as quickly as possible. Having these things in place *before* you contact us helps you avoid delays and get approved to send SMS faster.

 [Update your privacy policy](/journeys/your-privacy-policy/)

 [Update your terms and conditions](/journeys/your-privacy-policy/#terms-and-conditions)

 [Provide clear opt-in and opt-out instructions](/journeys/opt-in-and-out-flow/)

 [Write example messages representing your campaigns](/journeys/sms-brand-campaign/)

 [Contact Customer.io to register as an SMS sender](/journeys/messages-and-webhooks/twilio-sms/registration/phone-number-types/)

.sms-checklist{margin:1.5rem 0;padding:1.5rem;border:1px solid #e2e8f0;border-radius:8px;background-color:#fafafa}.sms-checklist\_\_item{margin-bottom:1rem}.sms-checklist\_\_item:last-child{margin-bottom:0}.sms-checklist\_\_label{display:flex;align-items:center;cursor:pointer;font-size:1rem;line-height:1.5}.sms-checklist\_\_label--final{opacity:.5;cursor:not-allowed}.sms-checklist\_\_checkbox{margin-right:.75rem;width:1.125rem;height:1.125rem;cursor:pointer}.sms-checklist\_\_checkbox:disabled{cursor:not-allowed}.sms-checklist\_\_text{flex:1}.sms-checklist\_\_text--disabled{color:#9ca3af}.sms-checklist\_\_link{color:#2563eb;text-decoration:none;font-weight:500}.sms-checklist\_\_link:hover{text-decoration:underline}.sms-checklist\_\_link--disabled{color:#9ca3af;cursor:not-allowed;pointer-events:none}.sms-checklist\_\_external-icon{display:inline-block;margin-left:.375rem;vertical-align:middle;opacity:.7;fill:currentColor}.sms-checklist\_\_item--final.enabled .sms-checklist\_\_label--final{opacity:1;cursor:pointer}.sms-checklist\_\_item--final.enabled .sms-checklist\_\_text--disabled{color:inherit}.sms-checklist\_\_item--final.enabled .sms-checklist\_\_link--disabled{color:#2563eb;cursor:pointer;pointer-events:auto}.sms-checklist\_\_link--disabled .sms-checklist\_\_external-icon{opacity:.5}.sms-checklist\_\_item--final.enabled .sms-checklist\_\_link--disabled .sms-checklist\_\_external-icon{opacity:.7}(function(){const e="sms-registration-checklist";function t(){const t=document.querySelectorAll(".sms-checklist\_\_checkbox"),n=document.getElementById("request-phone-number-checkbox"),s=document.querySelector(".sms-checklist\_\_item--final");function i(){try{const n=localStorage.getItem(e);if(n){const e=JSON.parse(n);t.forEach(t=>{const n=t.dataset.checklistItem;e\[n\]&&(t.checked=!0)}),o()}}catch(e){console.warn("Failed to load SMS checklist state:",e)}}function a(){try{const n={};t.forEach(e=>{const t=e.dataset.checklistItem;n\[t\]=e.checked}),localStorage.setItem(e,JSON.stringify(n))}catch(e){console.warn("Failed to save SMS checklist state:",e)}}function r(){const e=Array.from(t).filter(e=>e.dataset.checklistItem!=="request-phone-number");return e.every(e=>e.checked)}function o(){const e=r();e?(n.disabled=!1,s.classList.add("enabled")):(n.disabled=!0,n.checked=!1,s.classList.remove("enabled"))}t.forEach(e=>{e.addEventListener("change",function(){a(),o()})}),i()}document.readyState==="loading"?document.addEventListener("DOMContentLoaded",t):t()})()

## You might work directly with Twilio[](#you-might-work-directly-with-twilio)

We’re currently working on a native solution for SMS, so you can do *everything* in Customer.io. But that solution is only available to select users right now.

While the information here is generally true for anybody who sends SMS messages, this section is primarily for users who aren’t already registered with Twilio to send SMS messages through Customer.io and have an SMS-use case that we can support natively. If you want to send SMS through Customer.io, and you meet our eligibility criteria, you can [sign up today!](https://customerio.typeform.com/to/uOk5YbsP)

### Are you eligible to manage SMS phone numbers in Customer.io?[](#customerio-sms-eligibility)

While we’re working on our native SMS solution, we only support users meeting the following criteria today. If you meet our criteria, you can [sign up](https://customerio.typeform.com/to/uOk5YbsP) to manage your SMS phone numbers and billing in Customer.io.

If you don’t meet this criteria, you can still send SMS through Customer.io! You’ll just set up an account directly through Twilio and manage your phone numbers there.

You’re eligible for our native SMS solution if:

*   Your business is based in the US or Canada.
*   You only send messages to people in the US or Canada.
*   You don’t require advanced analytics like revenue attribution or sending queues.

## How long will it take for me to be approved?[](#how-long-will-it-take-for-me-to-be-approved)

When you request a phone number and register as a sender, you need to be approved by both Twilio and cellular carriers. This can take a while; we typically see approval responses in 1-2 weeks—though it can take longer if Twilio and carriers request changes to your privacy policy and terms and conditions.

As regulatory requirements change and penalties for non-compliance increase, Twilio and carriers have become more strict in their approval process! Following the guidance in this section can help you avoid delays and get your number approved faster. More importantly: it’ll help you avoid penalties for non-compliance.