feature request: Support for alphanumeric sender ID in SMS connectors (e.g., Twilio)

[vaintrub]

What problem did you meet?

Currently, Logto’s SMS connector (e.g., Twilio) only supports sending messages using a phone number as the sender ("From"). This makes it impossible to use an alphanumeric sender ID such as "MYAPP" or "MyBrand" in regions where this method is legally allowed and widely used.

Many international markets (UK, EU, APAC, Middle East, LATAM) support SMS delivery with alphanumeric sender IDs, and providers like Twilio, MessageBird, Infobip, Sinch, and RouteMobile allow using them. Without a way to configure a sender ID in Logto, branded SMS messages cannot be used, which limits trust, deliverability, and compliance in countries where Sender ID is mandatory.

In other words, Logto always forces the SMS sender to be a phone number, even in regions where this is not required.

Describe what you'd like Logto to have

I would like Logto to add support for alphanumeric sender IDs in SMS connectors.

Requested enhancements:

1. Add an optional "Sender ID" input field in each SMS connector (e.g., Twilio).
2. If the field is populated, Logto should use that value for the "From" parameter when sending SMS:
   From: "MYBRAND"
3. Validate the field according to provider and carrier rules (A–Z, 0–9, up to 11 characters).
4. Show a warning that alphanumeric sender IDs are supported only in certain countries.
5. Maintain backward compatibility:
   • If the field is empty → continue using the phone number as before.

This feature would enable:

• Brand recognition and better user trust.
• Compliance with local regulations in markets that require Sender ID registration.
• Compatibility with providers (Twilio/Infobip/MessageBird/etc.) that already support Sender ID at the API level.

Adding this option would significantly improve Logto’s global SMS capabilities.