Before enabling real sends, confirm the existing resource and sender against the current Azure SMS eligibility guide. Saving a trigger or campaign does not remove Azure’s onboarding restrictions.

Use Admin Alert Center for staff-facing events, separately from client notification triggers. Each administrator has their own mobile number, event choices and Enabled setting. Staff alerts use the default SMS gateway and are immediate.

Configure the intended staff member

1. Open PD Modules → Azure SMS → Admin Alert Center.
2. Find the intended administrator and choose Configure.
3. Enter Mobile number in international format.
4. Select the intended Text me when events.
5. Set Enabled as intended and choose Save.

Review the saved row for its number, event count and On/Off state. Do not assume that configuring one administrator subscribes the whole team, or that a client’s notification preference controls staff alerts.

Choose events the platform raises

On Blesta, use the available new-order, paid-invoice, new-support-ticket and cancellation events. Blesta does not report the provisioning or registrar failure events needed for those alerts. If an older screen exposes such a choice, do not rely on it as failure monitoring.

An SMS alert is a signal to inspect the original order, invoice, ticket or service. It does not repair a failed action, establish delivery to the staff phone or prove that a customer-facing notification also ran.

Check routing and timing

Staff alerts bypass the sending queue, quiet hours and client automatic-message preferences. Check the default gateway before enabling them. For a controlled rehearsal, remember that changing the default can also affect other workflows that use Default routing; do not switch a live installation casually.

Inspect History for the original alert and the provider result. With Azure, acceptance is separate from phone delivery. To stop a staff member’s alerts, clear Enabled and save; Remove deletes that staff alert configuration.

Distinguish the recorded result from delivery

The gateway checks Azure’s per-recipient send result. A Sent record reflects initial success, not later delivery to the phone. Enabling Request delivery reports requests Azure-side reporting; it does not set up Event Grid subscriptions or update module History with later results. Keep the Azure message reference for an investigation instead of treating a campaign progress total or green result as a delivery receipt.

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