For a real Azure send, first confirm the existing resource and sender against the current eligibility and service-change guide. Configuration changes do not remove Azure’s onboarding restrictions.

Use Send SMS for a deliberate message to one client or a directly entered number. A manual send is immediate and bypasses the automatic-message preferences and quiet-hours window, so check the recipient and timing yourself.

Prepare the message

1. Open PD Modules → Azure SMS → Send SMS.
2. Search for the intended client using the client picker. Leave Phone number blank to use their configured number, or enter the exact intended destination in international format.
3. Select the gateway explicitly under Send via. Choose Test / Debug Log only for a rehearsal, or the intended Azure Communication Services gateway for a real message.
4. Enter Message. A selected template fills the composer; check its text and replace any placeholders before sending.
5. Choose Count segments, then review the recipient, wording and gateway again.

Send once and inspect the outcome

Choose Send SMS only when ready for the selected gateway to act. An Azure SMS send can incur provider charges. The normal queue setting does not postpone this manual action until the next cron run.

The gateway checks the recipient result returned by Azure. A Sent record indicates a successful initial result; it does not establish that the phone received the message. Open History for the attempt and Azure message reference. A request for delivery reports does not make later delivery results appear in module History.

Send from the client profile instead

The client’s administrator profile also has a Text messages panel showing the effective number, preferences and recent history. Review those details before composing there. The preference summary is valuable context, but manual messages are not automatically blocked by the client’s automatic-message choices.

If a send times out, inspect the Unknown result before repeating it: Azure may already have accepted the request. Do not press Send repeatedly to investigate a slow response. Your hosting team should compare the original History record with any available Azure delivery evidence.

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