Skip to content

SMS_FROM_NUMBER_INVALID

Category: sms  ·  Severity: warning  ·  Channel: SMS

This template sets a per-template from_number override, but the value does not normalize to a valid E.164 phone number.

What it means

An SMS template can optionally override the sending number with a from_number field. Synapse validates that value against the same phone-number normalizer used across the platform (backed by the phonenumbers library). If the override is present but does not resolve to a valid E.164 number, this finding fires.

Note

A NULL / empty from_number is valid and does not trigger this finding. When you leave from_number unset, the Twilio Messaging Service selects the sender for you. This finding only fires when you set an override to an invalid value.

Why it matters

At send time, the Messaging Service can only dispatch from a valid sender. An invalid from_number override is a misconfiguration that would cause the send to fail or fall back unexpectedly. Catching it before you go live avoids a failed batch.

How to fix it

  1. Set from_number to a valid E.164 number — the international format with a leading + and country code, for example +15551234567.
  2. Or clear the override entirely so the Twilio Messaging Service selects the sender.

Finding context

The offending value is redacted in the finding context — only the last two characters are shown — so no full phone number is exposed in Inspect output:

json
{
"from_number_redacted": "*...*67"
}