Fix the Not a Valid SMS-Capable From Number Error

If you see The From phone number is not a valid SMS-capable phone number, the number you are trying to send from cannot deliver SMS for the destination, account, or campaign you have configured. This guide walks through every common cause and the fix.

Quick fix checklist

• Confirm the From number belongs to this sub-account or location and is SMS-capable.
• Use E.164 format in the From field, e.g. +15551234567.
• For US 10DLC, attach the number to an approved A2P campaign through the Messaging Service.
• If using a Short Code, the To and From must be in the same country.
• If using an Alphanumeric Sender ID, confirm the destination country supports it.
• If you manage numbers in Twilio Console, verify the number is on this Master account, not another one.

If the error started after a recent move or configuration change, re-check ownership (agency vs sub-account), campaign assignments, and any Messaging Service changes.

Common Causes & Fixes

1. The number is not SMS-capable

Some phone numbers are voice-only or do not support SMS in certain countries.

• Sparkforge Phone: Go to Settings → Phone Numbers, open the number, and confirm Messaging is enabled.
• Twilio: In Console, open the number and verify that Capabilities include SMS.

Fix: Use a different SMS-capable number, or purchase one that supports messaging.

2. The number is not valid for your account or destination

The From must be a number owned by your account and valid for the target country.

• Short Codes must be in the same country as the destination.
• Hosted, trial, or other-account numbers are not valid until fully owned and SMS-enabled here.

Fix: Send from a number on this account that supports the destination country.

3. A2P 10DLC (US) is missing or wrong

US local 10DLC numbers must be tied to an approved A2P campaign.

• Sparkforge Phone: Confirm the number is linked to your approved Brand and Campaign.
• Twilio: Attach the number to the Messaging Service tied to the approved campaign.

Fix: Complete A2P registration, link the number, and retry after approval.

4. Formatting or sender type

• E.164 required: Use + and country code.
• Alphanumeric Sender ID: Only supported in specific countries — not for US/CA person-to-person messaging.

Fix: Correct the From format, or pick a sender type the destination country supports.

5. Number was recently moved

If the number was moved between sub-accounts or providers, the From selector or saved automations may still point at the old number.

Fix: Re-select the active number in Conversations, Campaigns, Workflows, and Messaging settings.

Special cases

• Toll-Free (US/CA): Requires Toll-Free Verification for reliable delivery. Unverified messages may fail or get filtered.
• International: Some countries block A2P from long codes. Use Alphanumeric Sender ID where supported, or an approved sender type per country rules.
• Different Master Twilio account: If the number lives under a different Master account, it cannot send from this one. Move it first or send from a number on this account.