PD Azure SMS gives clients a Text messages page with recent recorded messages and a summary of their text-message preferences. The page helps a client check what was recorded before asking about a missing notification; it is not an Azure delivery-tracking portal.

Find the client page

In the Blesta client area, open My Tools and choose the Text messages entry listed under the module’s name. The client must be signed in to see their own information. The recent-message view is limited; the administrator’s History screen is the appropriate place for a fuller investigation.

The page shows recent message text, dates and recorded status, plus the preferences in force. A Sent status means the provider returned success for the attempt. For Azure, a successful initial recipient result does not establish delivery to the phone. A Test / Debug record can also show success without sending an SMS.

Change preferences in one place

Use the page’s profile link to change preferences. The choices appear as client-profile tick boxes; visible fields also appear during signup. Each label includes its explanation. A category the host marks Not offered is absent; a missing category is not evidence that the client agreed to receive it.

The client page summarises the choices rather than maintaining a second independent preferences form. After saving a profile change, check the resulting state there. These preferences govern automatic client messages; manual staff sends and staff-facing alerts have different routing.

If the page is missing or unavailable

Check Let clients choose which texts they receive and the offered categories in the administrator panel. Disabling the choices or offering no visible categories can hide navigation or show an unavailable message. Do not assume that this setting pauses all service SMS.

When several PD SMS modules are installed, a shared client-facing surface can represent them, with PD SMS Manager taking precedence when present. Do not add duplicate menu links just because the page is not labelled solely Azure SMS. Your hosting team should compare the shared-surface owner, offered categories, relevant administrator History and the affected theme. Do not add duplicate menu links or change stored records to diagnose it.

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.