PD SMS Manager can notify a client after a successful account sign-in in Blesta. This is an account-activity notification, not an SMS code required before signing in.

Prepare the recipient and message

Check the effective mobile number and country on a controlled test client. Open SMS Manager → Client Preferences, review Account Texts, and apply the intended profile choices. The event’s category determines its preference check; putting a template into another library category does not bypass that check.

Create an enabled template under Templates. Keep the template simple, for example `Hi {first_name}, there was a sign-in to your account at {company_name}. If this was unexpected, please contact support.` Avoid invoice or ticket fields: a sign-in event does not supply their context. Use the merge-field reference, and keep the text limited to the information the recipient needs. Do not include passwords or sensitive service access details in the message.

Add the trigger

1. Open PD Modules → SMS Manager → Triggers → New trigger.
2. Under When this happens, choose Sign-in to their account.
3. Under Send this template, choose the intended enabled template.
4. Under Send via, choose an explicit gateway. Use Test / Debug Log only for a controlled rehearsal.
5. Choose Create trigger, then review the row’s event, template, gateway and On/Off state.

The notification follows a successful client sign-in. It does not block the session or add a pre-login challenge. Blesta’s sign-in notification uses its successful login event; it is not a third authentication method added to Blesta.

Account Texts starts hidden in the module’s default preferences. Offer that category deliberately and review the client’s choice. A trigger saved while Account Texts is Not offered will not notify the client. Check that the original customer sign-in was associated with a client account. A saved enabled trigger alone does not prove that the event had a recipient.

Verify the outcome

Review History for the actual recipient, rendered text and gateway. If queueing is enabled, normal cron operation and quiet hours can delay the attempt. A category marked Not offered, a client preference, a disabled template or missing mobile number can prevent sending even when a trigger exists.

Do not repeat a real customer event to force another notification. Check whether another enabled trigger already handles the same event before adding a duplicate. For the selected gateway, a Sent result records the initial gateway outcome; later phone delivery needs its own evidence. An Unknown timeout needs reconciliation before any repeat message.

Several SMS modules on one installation

PD SMS Manager takes precedence as the manager of shared client-profile fields when several PD SMS modules are enabled. Follow any Client Preferences message identifying the managing module. Review each sending module’s own category rules, phone source and gateway routing separately; the shared profile summary does not prove every enabled module’s sending configuration.

Interpret the selected gateway

A real gateway’s initial success is separate from later phone delivery. For Custom HTTP Webhook, Sent means its configured HTTP success rule matched; it is not an imported delivery report. A Test / Debug Log only record can succeed without sending a text. Keep the selected gateway and any provider message reference with the action time when investigating a result.

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