Use an existing Twilio number
Connect a supported number already provisioned in your Twilio account. Your team replies from Intercom, and messages go out through Twilio using the connected sender.
Need a sender or destination outside Intercom's native SMS options? Connect an eligible Twilio number with Octopods and handle customer texts in Intercom Inbox.
Octopods connects SMS-capable numbers from your Twilio account to Intercom. That gives you another route when Intercom's native country or number options do not fit. Availability depends on the sender, destination and registration requirements. Confirm both sending and receiving for your exact setup before launching two-way support.
Sender & recipient
SMS capability
Local requirements
Check inbound and outbound SMS support
Your team’s existing inbox
Connect a supported number already provisioned in your Twilio account. Your team replies from Intercom, and messages go out through Twilio using the connected sender.
Choose an SMS-capable phone number available in the Octopods setup. Check its inbound and outbound capabilities, destination rules and registration status before using it for customer conversations.
Inbound texts arrive as Intercom conversations. Your team can use its Intercom handling process to assign and answer them instead of monitoring a separate SMS inbox.
Intercom's native option may already cover your needs. Use the country and number requirement to guide the choice.
Scroll across to compare every column
| What matters to your team | Intercom native SMS | Twilio via Octopods |
|---|---|---|
| Documented number options | US toll-free; Canada local; UK and Australia local mobile | Eligible SMS-capable phone numbers available in the Octopods setup |
| Destination coverage | Native numbers send within their own country | Subject to Twilio sender and destination rules |
| Where replies arrive | Intercom Inbox | Intercom Inbox |
| Existing Twilio account | Not the connection model | Connect using your Twilio credentials |
| Costs to review | Intercom subscription and native SMS charges | Intercom, Octopods and Twilio charges |
Intercom's documented native coverage was checked on 10 September 2026. Provider availability and registration requirements can change.
An international support setup needs to work in both directions. Choose a small test that reflects the numbers, countries and message content your customers will actually use.
Confirm that the number can receive replies. Alphanumeric sender IDs are outbound-only and are unsuitable when customers need to text you back.
Review Twilio's guidelines for the recipient's country. A number's location alone does not establish which international routes or reply behaviours are available.
Send from a representative customer phone, answer in Intercom and verify the return message. Test your usual language and message length, then inspect delivery and billing.
Identify your sender and customer destinations. Check Twilio’s geographic permissions and complete applicable sender registration or verification before production use.
Add a Twilio channel in Octopods, enter your live Account SID and Auth Token, and select an available phone number. Octopods configures its incoming-message webhooks and Messaging Service connection.
Text the connected number, find the conversation in Intercom and reply. Confirm receipt on the customer's phone before directing traffic to it.
Use a funded Twilio account and a sender approved for the intended traffic. US local business texting requires the applicable brand and campaign registration in Twilio.
Have access to your Intercom workspace and administrator permissions in Octopods. Keep the connected Twilio credentials current.
Set a clear opt-in and opt-out process. Confirm the destination-specific requirements and how your team will handle replies before sending.
Have a setup that needs a closer look?
Talk it through with our teamBring your sender type and customer countries. We'll help you assess the right Twilio connection for Intercom.