Use SMS Manager → Settings → Default Sender ID as a fallback for supported gateway sender fields. It is the outgoing identity, separate from the client phone-number source and from the choice of default gateway.

Check which gateways use it

The fallback can fill an empty Amazon SNS Sender ID, Clickatell From, or Custom HTTP Webhook From. A value already saved on that gateway takes precedence. In a custom request, the resulting From value is used by the {from} placeholder where you put it in the URL or body.

Twilio, Vonage and Azure gateway sender settings are configured in their own forms; do not expect this general fallback to replace a required number, Messaging Service or resource sender. Check the intended gateway’s form rather than treating every provider as one shared sender account.

Save the intended fallback

1. Open PD Modules → SMS Manager → Settings.
2. Enter Default Sender ID appropriate for the provider and destination you intend to use.
3. Save, then inspect each relevant gateway’s own sender field.
4. Review the workflow’s selected gateway before an intended send.

Entering a brand name does not register or authorise it with a provider. Use the identity available to the account carrying that traffic, with the provider’s current destination requirements. A sender suitable for one gateway or destination is not automatically suitable for another.

Diagnose an unexpected sender

Check the actual History gateway first. Then review that gateway’s saved sender, whether its supported field was blank, and the module fallback. For Custom HTTP, also check whether the request template actually includes {from} in the provider’s required parameter.

Changing Default Sender ID does not change the receiving client number, redirect a trigger to another gateway or recall an accepted message. If the sender is refused, preserve the original redacted provider error and verify the identity before repeating the send.

See the PD SMS Manager Blesta guide for related tasks, or explore PD SMS Manager.