Create a PD Twilio SMS campaign to text an audience selected by client status and group. All campaigns use the Marketing Texts preference, even if the body describes maintenance or another service notice. Choose an event trigger instead when that is the intended workflow.

Preview the intended audience

1. Open PD Modules → Twilio SMS → SMS Campaigns → New campaign.
2. Enter Campaign name and choose Client status and Client group.
3. Choose an explicit Send via gateway.
4. Enter Message, using client merge fields such as `{first_name}` or `{company_name}` where useful.
5. Choose Preview audience & cost and review the result before any launch.

The audience includes matching clients who allow marketing texts and have a usable mobile number. A group containing many accounts can therefore produce a much smaller preview. An empty audience is not a reason to override preferences or replace missing numbers with guessed values.

Campaigns render basic client fields. Invoice, service and ticket fields are event-specific; a campaign does not gain those contexts by selecting a template that contains them. Check the wording after personalisation in a controlled Log only rehearsal.

Choose immediate queueing or a schedule

Send now starts queued work; it is not an immediate delivery promise to every phone. Schedule uses Or schedule for (optional). Check the saved Scheduled value on the campaign’s View screen, and verify the installation’s time basis before a time-sensitive launch. The scheduling field is not a per-recipient local-time delivery setting. A quiet-hours timezone is a separate setting and does not establish the interpretation of this scheduling field.

The audience and personalised text are prepared when the campaign is launched. Do not expect a scheduled campaign automatically to include clients added later. Category preferences are checked again as queued work is sent, so a client’s later opt-out can prevent their message.

Review progress carefully

Normal cron operation, batch limits, due time, retries and quiet hours affect progress. Preview segments are an estimate rather than a final currency quote; personalised values can change message length. The list’s Sent / total display is a progress view, not a phone-delivery receipt. Open View and inspect Sent and Failed separately, then correlate History with Twilio delivery evidence if needed.

Do not relaunch an apparently slow campaign before checking the original. Your hosting team should compare the saved schedule, due time, quiet hours, cron and original History attempts.

Several SMS modules on one installation

When several PD SMS modules are enabled, a single module manages the shared client-profile fields. PD SMS Manager takes precedence when present. Follow any Client Preferences message identifying that module and make shared profile-setting changes there. Check PD Twilio SMS’s own category rules, phone source and gateway routing separately; a shared profile summary does not prove every enabled module’s sending configuration.

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