The SMS adapter accepts an explicit from-number. When present it pins the send to that line; otherwise it falls back to the Messaging Service, and finally to the binding's default number. Compliance is unaffected because a number carries its campaign association through its service membership, not through how the send is addressed.
Also called: send from my number · different number every time · thread coherence · messaging service pool
- 1The caller supplies the sending user's assigned number.
- 2The adapter normalises it to E.164 and sets it as the From.
- 3With no pinned number, the Messaging Service SID is used instead.
- 4Both the modern phoneNumber and the legacy from config keys are accepted so a hand-made binding still works.
The comment lays out the failure: 'Sending via MessagingServiceSid lets Twilio choose any number in the pool, which is right for broadcast and wrong for a conversation: the customer sees a different sender than the one they have been talking to, and their reply lands with whoever owns that number instead of the rep handling them. Naming the number keeps the thread coherent.'
- Pool-based sending broke conversation continuity and misrouted replies.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →