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.

Create reusable message bodies in Azure SMS → Templates so invoice, support and service notifications use consistent wording. Choose merge fields that the event can actually supply, and check the rendered result before relying on a template.

Add a template

1. Open PD Modules → Azure SMS → Templates and choose New template.
2. Enter a descriptive Name, such as Invoice received notification.
3. Select the intended Category.
4. Write the Message, using the on-screen Merge fields you can use reference.
5. Choose Create template. When editing an existing template, choose Save changes.

For example, an invoice-event message can use Hi {first_name}, invoice {invoice_id} for {invoice_total} has been received. Thank you from {company_name}. Use invoice fields with an invoice event, service fields with a service event, and ticket fields with a ticket event. A token’s presence in the reference does not mean every workflow supplies its value.

Check personalised output

Review the displayed preview as an illustration, then rehearse the actual event through a Test / Debug Log only gateway in a controlled test workflow. Sample preview data cannot establish what a particular customer event will contain. Unknown or unavailable fields can become empty text, leaving an incomplete sentence.

If you choose a template on Send SMS, it fills the composer with the template body. Review the actual Message field and replace placeholders with the intended wording before a manual send; do not assume that choosing a client resolves every merge field in this composer.

Connect automation deliberately

Creating a template does not create an automatic notification. Triggers separately connect an event, an enabled template and a gateway. The client’s event category, preference and sending queue also affect automatic messages.

Measure the final text with Count segments where available. Personalised names, amounts or subjects can change the length from the sample, so a template preview is not a fixed billing estimate.

Check the Azure context

Azure receives the rendered text and the sender configured on the selected gateway. Creating a template does not register that sender or change its destination capabilities. Keep the Connection string out of message text, template examples and support evidence.

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