Skip to main content

Setting up Twilio SMS for Intercom

Connect a Twilio SMS number to your Intercom workspace so inbound texts land in your Intercom inbox and replies go out over Twilio.

Written by Mohamed Elbadwihi

Connect a Twilio number to Octopods to send and receive SMS from your Intercom inbox. This also lets you route Twilio SMS replies to Intercom when your outbound texts go out from another tool. Twilio SMS supports long codes (local or mobile), toll-free numbers and alphanumeric sender IDs (outbound only). Short codes aren't supported. For an overview, visit Twilio SMS for Intercom.

Before you start

You need:

  • A Twilio account with an active SMS-capable phone number or alphanumeric sender.

  • Your Twilio Account SID and Auth Token (both found on the Twilio Console home page).

  • For numbers sending to the United States: a registered A2P 10DLC brand and campaign (covered below).

  • Admin access to the Octopods workspace.

Step 1: Start the Twilio channel setup

  1. Open the workspace you want to add Twilio to.

  2. Click the option to add a new channel and select Twilio under Popular Channels.

  3. The Twilio setup panel opens. The left side shows a “How it works” summary; the right side has the credentials form.

Step 2: Enter your Twilio credentials

In the form, fill in:

  • Twilio Account SID — starts with AC and is shown on the Twilio Console home page.

  • Twilio Auth Token — also on the Twilio Console home page. Click the eye icon in Twilio to reveal it, then copy it into Octopods.

Tip: Use the Live credentials, not the Test credentials — test credentials cannot send or receive real messages.

Step 3: Pick the sender

Choose how outbound messages will be sent:

  • Phone Number — pick from the list of phone numbers Octopods fetches from your Twilio account. Each entry is a real E.164-formatted number on the account (for example, +15551234567).

  • Add Alphanumeric Sender ID — a short alphanumeric string (up to 11 characters, letters and digits only). Alphanumeric senders can only send outbound messages; they cannot receive replies, so this option is not suitable if you need two-way conversations.

Short codes aren't supported. Use a long code (local or mobile), a toll-free number or an alphanumeric sender ID.

Step 4: Complete A2P 10DLC for US numbers

If your Twilio number is a US long code, US carriers require it to be registered under the A2P 10DLC framework (Application-to-Person messaging over 10-digit long code). Unregistered US traffic gets heavily filtered.

When you pick a US number, Octopods shows an A2P section with two options:

  • Register Brand in Twilio — opens the Twilio Console in a new tab, where you register your brand. Brand approval typically takes 1–2 weeks, and campaign approval another few days.

  • I’ll do this later — you can start using the channel right away for testing, but deliverability to US recipients will be poor until registration completes.

After your brand is registered, you can register your campaign in Octopods with the Register New Campaign form.

Important: If you skip registration, your outbound US traffic will be throttled or blocked by carriers. Finish your A2P 10DLC brand and campaign registration before you use the channel for production traffic.

For numbers sending only to non-US countries, A2P 10DLC does not apply and this step does not appear.

Step 5: Save and activate

  1. Click Activate Twilio Channel at the bottom of the setup panel.

  2. Octopods verifies your credentials against Twilio’s API. If anything is wrong (typo in the SID, revoked Auth Token, number not on the account) you’ll see an error — correct it and try again.

  3. On success, Octopods automatically registers the webhook URL on your Twilio number. You do not need to configure anything in the Twilio Console yourself.

  4. The channel appears in the channel list with an Active status.

Step 6: Send a test message

  1. From a personal phone, text a short message to the Twilio number you just connected.

  2. Open the Intercom Inbox for the connected workspace. A new conversation appears with your message.

  3. Reply to the conversation in Intercom.

  4. The reply arrives on your phone as an SMS from the Twilio number.

If either direction fails, deactivate the channel on its detail page and activate it again. There’s no separate reconnect button, and activating registers the webhook again. See Channel Statuses and Troubleshooting for more diagnosis steps.

Route Twilio SMS replies to Intercom when you send from another tool

Many teams send appointment reminders or notifications from another tool that uses Twilio. You can keep sending from that tool and still get customer replies in your Intercom inbox.

  1. Connect the same Twilio number to Octopods using Steps 1–5 above.

  2. Keep sending from your other tool as before. Its messages go straight through Twilio.

  3. When a customer replies, Twilio forwards the reply to Octopods, and it appears as a conversation in Intercom. Your team replies from there, and the reply goes out as an SMS from the same number.

Things to know:

  • Octopods takes over the number’s incoming webhook. When you activate the channel, Octopods replaces the number’s incoming-message URL and fallback URL in Twilio. If your other tool reads replies from that webhook (for example, “Reply C to cancel”), it stops receiving them. Check this before you connect the number.

  • Messaging Services. Numbers inside a Twilio Messaging Service work with Octopods. Pick an existing service, or Octopods creates one called “Octopods Messaging Service”. If the service handles incoming messages at service level, Octopods asks you to approve a Quick Configuration Update and moves that setting onto each number. You don’t need to change anything by hand.

  • The original reminder isn’t in the conversation. Messages your other tool sends through Twilio don’t pass through Octopods, so they never appear in Intercom. The Intercom conversation starts with the customer’s reply. If you want the reminder in the conversation too, send it through the Octopods SMS API with open_intercom_conversation set to true. See Send SMS Message.

Connect multiple Twilio numbers to Intercom

Each Twilio channel sends from the one sender you pick in Step 3. To connect several numbers, for example one per store or sales rep, add a Twilio channel for each number. All of them can deliver into the same Intercom workspace.

  • Each Twilio number is a separate paid channel. See Upgrading or Adding Channels.

  • An Octopods account can have up to 50 channel subscriptions.

  • You add numbers one at a time, one number per activation. There’s no bulk option.

How to tell which number a customer texted. Octopods saves the Twilio number that received the message in the Intercom contact attribute octopods_twilio_sms_account_phone. You can use it in assignment rules and Workflows to route conversations by number. It’s a contact attribute, so it holds the number the person texted most recently. Give each channel a clear name, such as the store or rep name, so your team can recognize it.

Keeping credentials up to date

  • Rotating your Twilio Auth Token inside the Twilio Console disconnects the Octopods channel. The token can’t be edited in place: after rotating, deactivate the channel on its detail page, then activate it again with the new token in the Twilio Auth Token field and click Activate Twilio Channel.

  • Reassigning a phone number to a different Twilio account breaks the webhook registration. Remove the channel from Octopods and add it again under the new account.


What’s next

Did this answer your question?