Twilio bills you directly
Messages, numbers and registrations such as A2P 10DLC are billed to your Twilio account at your Twilio rates. ConnectSMS doesn't add, include or remove those charges.
Twilio integration
Your Twilio account. Your numbers. Your usage.
ConnectSMS connects Salesforce to the Twilio account you already have. Your team texts from Salesforce, Twilio carries the messages and bills your account directly, and ConnectSMS adds no message-plan limits.
- No credit card required
- Listed on Salesforce AgentExchange
- Then $120 per user per year
- Runs on your own Twilio account
How do you connect Twilio to Salesforce? Install ConnectSMS, open ConnectSMS Setup and enter your Twilio Account SID and Auth Token, which ConnectSMS verifies with Twilio before saving. Sync your numbers from their Messaging Services, then point those services at a webhook on a public Salesforce Site so replies and delivery updates come back. Salesforce calls Twilio's API directly, with no ConnectSMS servers in between.
Twilio connectionConnectSMS uses your own Twilio account, so Twilio bills that account directly.
Connected to Twilio
Verify again
ConnectSMS uses the saved Account SID and Auth Token for this Twilio account.
Connection status
- Account name
- WorkBridge Solutions
- Account status
- active
- Account SID
AC…1a2b- Auth Token
- Saved
- Default country code
- +1
- Last verified
- Oct 12, 2026, 09:14 AM
Update connection
Account SID
Auth Token••••••••Change
*Default country calling code+1
Save and verify
Recreated from the ConnectSMS interface with sample data.
No message or country limits
ConnectSMS has no message quotas, plan tiers, user caps or country restrictions. Admins can set an optional daily safeguard, and Twilio's own account limits and Geo Permissions still apply.
No servers in between
Built on the Salesforce Platform. Salesforce talks to Twilio's API directly, and Twilio calls back to a Site in your own org.
How it works
How Salesforce and Twilio connect.
Two direct connections: Salesforce calls Twilio to send, and Twilio calls a webhook on your Salesforce Site to report replies, opt-outs and delivery updates.
Two direct connections, nothing in the middle
- Sending: ConnectSMS saves each message in Salesforce, checks access, opt-outs and policies, then calls Twilio's API from the exact business number chosen
- Receiving: Twilio posts replies, STOP and START keywords and delivery updates to the ConnectSMS webhook on your public Salesforce Site
- Every webhook call is checked against Twilio's signature and your Account SID before ConnectSMS acts on it
- The only outside endpoints ConnectSMS calls are Twilio's
Your Salesforce org
People, Flow, Apex and agentsRecords, inbox, outreach and automation
ConnectSMSRecords every message and checks access, opt-outs and policies
Public Salesforce SiteWebhook for replies, opt-outs and delivery updates
Your Twilio account
Account SID and Auth TokenVerified with Twilio before saving
Messaging ServicesYour business numbers and A2P 10DLC campaigns
Twilio billingMessages, numbers and registrations, billed to you
No ConnectSMS servers in between: Salesforce calls Twilio's API directly, and Twilio calls back to a Site in your own org.
Sending
- Saved in Salesforce
- Access and opt-out checks
- Salesforce calls Twilio
- Carrier
- Customer's phone
Replies and opt-outs
- Customer replies
- Messaging Service
- Webhook on your Site
- Signature checked
- Record and inbox
Delivery updates
- Carrier reports status
- Twilio status callback
- Same signed webhook
- Status on the message
Connect Twilio
From Twilio credentials to the first text, in ConnectSMS Setup.
These are the Twilio parts of the eight-step setup checklist. The checklist shows what's done and what still needs attention.
Twilio connection
Connect your account
Paste the Account SID and Auth Token from the Twilio Console and choose Save and verify. ConnectSMS checks them with Twilio first. If Twilio says no, nothing is saved and your earlier connection keeps working.
Technical detail
The Account SID starts with AC followed by 32 letters and numbers. The Auth Token is stored in a protected setting only ConnectSMS can read, and it is never shown again or sent back to your browser.
You also set a default country calling code, such as +1, for phone numbers saved without one. Verify again re-checks the saved connection and shows the account name and status.
Business numbers
Sync your numbers
Choose Sync from Twilio to import the numbers in your Messaging Services. Sync adds and updates numbers and flags any that Twilio no longer returns. It never deletes them.
Technical detail
Each number must belong to exactly one Messaging Service. From ConnectSMS Setup you can Create Messaging Service, Add to a service and Remove from service. To buy numbers or delete a service, use the Twilio Console.
ConnectSMS sends from full phone numbers only. Short codes and sender names are skipped during sync.
Inbound webhook
Receive replies and delivery updates
Choose a public Salesforce Site, assign ConnectSMS Webhook Guest to its guest user, then choose Configure webhook on selected services. ConnectSMS points those Messaging Services at the site.
Technical detail
The webhook address ends in /services/apexrest/csms/twilio/webhook on your site's domain. A basic Salesforce Site is enough.
Configuring replaces any inbound or status callback URL already set on those services, so another system that used them stops receiving those webhooks.
Signature check
Enforce signatures, then turn on sending
Signature checking has three modes: Enforce, Monitor and Off. Sending can only be turned on with Enforce, so forged replies and delivery updates are rejected.
Technical detail
Enforce rejects every request without a valid Twilio signature. Monitor accepts and records requests with a missing or wrong signature, for short troubleshooting only. Off is for development orgs.
Webhook requests must also match the Account SID of your saved connection.
Numbers and Messaging Services
Your numbers, organized the way Twilio organizes them.
A Messaging Service groups numbers in Twilio and holds their shared settings, such as the inbound webhook and the A2P 10DLC campaign. ConnectSMS shows each business number with its service, status and capabilities.
- Works with Twilio numbers from any country
- Always sends from the exact number chosen, never a substitute
- Shows whether each number is ready to send and supports MMS
- Deactivate a number in ConnectSMS without touching it in Twilio
- Decide who can send from each number, per person or public group
US numbers need registration. A US 10DLC number must be in the Messaging Service linked to its approved A2P 10DLC campaign, or be a verified toll-free number. You register in Twilio, and Twilio charges the fees. If a 10DLC number moves to a service without an approved campaign, carriers block its messages (Twilio error 30034).
Business numbersThe Twilio phone numbers people send from. Each number belongs to exactly one Messaging Service.
Sync from Twilio
| Number | Messaging Service | Status | MMS | Automation |
|---|---|---|---|---|
| +1 (415) 555-0199Support line | Support messaging | Ready | Not available | |
| +1 (415) 555-0142Sales line | Sales messaging | Ready | Not available | |
| +1 (415) 555-0123Service line | Service updates | Ready | — | Automation default Available |
Recreated from the ConnectSMS interface with sample data.
Inbound webhook
Replies come back to Salesforce, signed by Twilio.
Twilio reports incoming texts, STOP and START keywords and delivery updates by calling a webhook on a public Salesforce Site in your org.
- The Site's guest user gets ConnectSMS Webhook Guest, which allows the webhook and nothing else. It gives no access to your records
- Every call is checked against Twilio's signature, and requests must match your Account SID
- Setup shows when the last reply and delivery update arrived, and lists anything that needs fixing
- Delivery updates only ever move a message forward, for example from Sent to Delivered
Inbound webhookReceive incoming messages, opt-outs and delivery updates by calling a public Salesforce Site.
Inbound messaging looks healthy
ConnectSMS found no problems with the webhook. Replies, opt-outs and delivery updates can reach Salesforce.
Latest activity
- Last incoming message
- Today, 2:16 PM
- Last delivery update
- Today, 2:15 PM
- Signature check
- Enforce (recommended)
Recreated from the ConnectSMS interface with sample data.
Billing and usage
Twilio bills you. ConnectSMS shows the usage.
Every message goes out on your Twilio account at your Twilio rates. There's no message bundle to buy from ConnectSMS and no plan limit to outgrow.
- Operations shows the last 30 days of outbound usage as reported by Twilio: messages and segments
- Segments are counted before you send, in the preview and in the outreach review
- An optional daily safeguard catches mistakes such as runaway automation. It's off until an admin sets it
- Invoices, number rental and registration fees stay in your Twilio Console
Last 30 days
842 messages using 917 segments.
Latest activity
- Last dispatcher run
- Today, 2:15 PM
- Last incoming message
- Today, 2:16 PM
- Last delivery update
- Today, 2:15 PM
Recreated from the ConnectSMS interface with sample data.
Automation numbers
Choose which numbers automation may use.
Flow, Apex, REST and agent requests follow the same number rules as people, with two admin controls made for automation.
Available to automation
Mark a number available, and integration and agent users with the ConnectSMS Automation permission set can send from it without a per-number Send grant.
Automation default sender
Pick one number for Flow and API requests that don't name a sender. Without a default, those requests fail with a clear reason instead of guessing.
Same rules as people
Automated messages still respect opt-outs, quiet hours and the daily safeguard, and Twilio charges apply to each one.
Checklist
What you need to connect Twilio to Salesforce.
- A Twilio account. A dedicated subaccount for each Salesforce production org is good practice
- At least one Twilio phone number in a Messaging Service
- For US numbers, an approved A2P 10DLC campaign linked to the service, or a verified toll-free number
- Your Account SID and Auth Token, from Account Info on the Twilio Console home page
- A public Salesforce Site for replies and delivery updates, with ConnectSMS Webhook Guest on its guest user
- A Salesforce admin with the ConnectSMS Admin permission set to work through the setup checklist
- Background jobs turned on in ConnectSMS Setup, for scheduled messages, outreach and delivery checks
- People who text: the ConnectSMS User permission set plus Send access to a business number
FAQ
Twilio and Salesforce: common questions
How does Twilio integrate with Salesforce?
ConnectSMS calls Twilio's API directly from Salesforce with your Account SID and Auth Token, which it verifies with Twilio before saving. Replies, opt-outs and delivery updates come back through a webhook on a Salesforce Site, and ConnectSMS checks Twilio's signature on every call. There is no ConnectSMS server in between.
Can I use my existing Twilio account?
Yes. ConnectSMS uses your own Twilio account and numbers, Twilio bills that account directly, and ConnectSMS adds no message-plan limits. Each number needs to be in a Twilio Messaging Service, and US numbers need an approved A2P 10DLC campaign or verified toll-free status.
Can I text numbers in other countries?
Yes. ConnectSMS has no country restrictions for text messages: you can send from Twilio numbers in any country and text any country your Twilio account is allowed to reach. Allow those countries in Twilio's Messaging Geographic Permissions, and check Twilio's pricing and sender rules for each one. Picture messages (MMS) are the one exception: attachments go only to US, Canadian and Australian numbers, the countries where Twilio documents MMS delivery.
Does ConnectSMS limit how many messages I can send?
ConnectSMS doesn't impose message-plan limits or quotas; Twilio bills your account for what you send. Admins can set an optional daily safeguard, and Twilio and the carriers apply their own sending rules.
Do my Twilio numbers need to be in a Messaging Service?
Yes. ConnectSMS sends only from numbers that belong to a Twilio Messaging Service, and each number can be in exactly one. You can create a Messaging Service and add or remove numbers from ConnectSMS Setup, or do it in the Twilio Console and then choose Sync from Twilio.
What happens to my Twilio Auth Token?
ConnectSMS checks the Account SID and Auth Token with Twilio before saving anything, then keeps the token in a protected setting that only ConnectSMS can read. It is never shown again, never sent back to the browser and never written to logs. To rotate it, choose Change and paste the new token.
Can ConnectSMS send from short codes or alphanumeric sender IDs?
No. ConnectSMS sends from full phone numbers in your Twilio account. Short codes and sender names are skipped when numbers are synced from Twilio.
Can Flow or an integration send from any of our numbers?
No. A Flow, API or agent request can send from numbers the running user has Send access to. Integration and agent users with the ConnectSMS Automation permission set can also send from numbers an admin marks Available to automation. One number can be the automation default, used when a request doesn't name a sender.
Keep exploring
Administration
The setup checklist, number access, policies and operations.
Two-way SMS
How replies, opt-outs and delivery updates reach Salesforce.
Security and reliability
Signed webhooks, protected credentials and no blind resends.
Try it now: every feature, free for 14 days
Put every customer text where your team already works.
Install ConnectSMS from AgentExchange, connect your Twilio account and give your team the numbers they should text from.
- No credit card required
- Listed on Salesforce AgentExchange
- Then $120 per user per year
- Runs on your own Twilio account
ConnectSMS is published by WorkBridge Solutions. Twilio bills your Twilio account directly for messaging, including during the trial.