Twilio + SalesCrew
Not available yet. Twilio will carry SMS, phone numbers and calling in the local-services pack, and this page says what is planned rather than implying it works.
- Roadmap, not shipped
- Consent and STOP planned in
- Outbound calls run through Vapi today
The short answer
- Twilio is not connected to SalesCrew today. Two-way SMS, phone numbers with inbound routing, voicemail transcription and a browser softphone are all roadmap items in the local-services pack.
- What exists now: outbound voice calls through Vapi with the call logged onto the record, and email cadences from a mailbox pool. If you need SMS this month, SalesCrew is not the tool for it.
- When SMS does arrive it is planned with consent, STOP handling and 10DLC registration as part of the feature rather than as a warning in a help article, because a texting product without those is a liability.
Mechanism
Every row here is roadmap. That is the point of the table.
| What | Mechanism | Direction | Objects | Status |
|---|---|---|---|---|
| Two-way SMS | Twilio Programmable Messaging | Two-way | Threads, messages, consent records | On the roadmap |
| Phone numbers and inbound routing | Twilio numbers with hours, whisper and voicemail | Inbound | Calls, voicemails | On the roadmap |
| Voicemail transcription in the thread list | Twilio plus transcription | Inbound | Calls, threads | On the roadmap |
| Softphone in the browser | Twilio Voice JS with recording and dispositions | Two-way | Calls, dispositions | On the roadmap |
| Missed-call text-back | Inbound call event triggering an SMS | Outbound | Messages, leads | On the roadmap |
| 10DLC registration support | Part of the SMS feature | : | Consent records | On the roadmap |
| Outbound voice today | Vapi, with call_start and call_log | Outbound | Calls | Available |
Mechanisms read from the SalesCrew integration table, September 2026. Twilio's own site is the authority on per-message, per-minute and 10DLC registration fees.
What to do in the meantime
If SMS is the reason you are looking at a CRM, buy something that has it today. That is a straighter answer than a promise with no date attached, and a product page that hedges about voice while selling a subscription is how people end up disappointed in month two.
If SMS is a nice-to-have beside a pipeline, an inbox and cadences that work now, the practical path is to run email and the LinkedIn queue in SalesCrew and keep texting wherever you text today. Nothing in the design assumes a single channel, and a contact record does not care which tool sent the message.
One piece of preparation is worth doing early regardless. If you plan to text businesses or consumers in the United States, 10DLC registration through your carrier takes time and needs a real company identity behind it. Starting that process before the feature ships costs nothing and removes a wait later.
Questions
- When will Twilio SMS ship?
- There is no date. Roadmap items are stated as intentions without dates, and the changelog is where a feature becomes real. If a date matters to your decision, treat this as not shipping.
- Can I connect my own Twilio account now?
- No. There is no Twilio connection in the app today, so a key would have nowhere to go.
- What can SalesCrew do with a phone today?
- Place outbound calls through Vapi and log the outcome onto the record. It cannot answer an inbound call and it cannot send a text.
- Does the Local tier include SMS?
- The Local tier at $499 a month is defined around the phone and SMS pack, and it ships when that pack ships. Buying it today for a capability that is not live would be the wrong decision.
- Will consent be enforced?
- That is the plan: consent records, STOP handling, a DNC scrub at audience freeze and a consent gate before a call starts. Consent itself is still yours to collect, and this is not legal advice.
Start with what works today
Pipeline, inbox, cadences and the MCP server, with the phone pack written on the roadmap rather than in the pitch.