PD SMS Manager for Blesta

PD SMS Manager

Send SMS to your clients from Blesta — notifications, alerts and campaigns

★★★★★5.0 · our rating, not customer reviews

Made and supported by Projektif Digital Ltd. Runs inside PD Modules, the panel every module installs into.

Messaging & SMS BETA

PD SMS Manager adds text messages to Blesta as a proper notification channel. Your clients get a text when an invoice is created or paid, when a service is activated or suspended and when staff reply to a ticket. You and your team get a text when a new order arrives. You can also message a filtered group of clients in one go. Every message goes through your own SMS provider account, and you pay that provider directly at its own rates.

It is built for hosting companies who know that a missed email is a late payment or an avoidable ticket, and who want the one channel people actually read at the moments that matter. Its biggest difference from a single-provider SMS module is that you are never tied to one carrier: you connect as many gateways as you like and choose which one carries each kind of message.

Why hosts choose PD SMS Manager

One module, every provider you might use. Amazon SNS, Azure Communication Services, Twilio, Vonage, Clickatell and any gateway with an HTTP API are all supported in one place, plus a Test gateway that sends nothing. Add several at once and mark one as the default. A single-provider module means a rebuild if you change supplier or need a second route. Here, you add a gateway and carry on.

Send each kind of message down the right route. Every trigger and every campaign can name its own gateway, or use the default. Put payment texts on a dependable transactional route, and promotions on a cheaper one. If a provider has an outage, point a trigger at another gateway without touching anything else.

Pay your provider, not us. No message credits are sold and nothing is marked up. Your provider's own rate is the cost of every text, and the segment counter shows what a message will cost before you send it.

Reach people at the moments that matter. Triggers send automatically for invoice created, invoice paid, service activated, service suspended or unsuspended and staff ticket replies.

Stay on the right side of consent. Clients choose which kinds of text they receive, promotional texts are agreement-only by default, and an opt-out made while a message waits in the queue is honoured.

How it works

  1. Connect a gateway. Open PD Modules, then SMS Manager, then Gateways, and add your provider with its credentials. Test connection checks them without sending anything. Send test SMS delivers a real message to a number you give.
  2. Set the basics. Choose a default sender ID and whether to send through the queue. Numbers come from the phone on the client's contact.
  3. Turn on the messages you want. Pick templates and map them to events, or send by hand.
  4. Watch it work. The dashboard shows what went out today and this month, and History records every message with its gateway and status.
The dashboard: texts sent today and this month, failures and queue depth, with the default gateway and sending queue at a glance
The dashboard: texts sent today and this month, failures and queue depth, with the default gateway and sending queue at a glance

What you get in Blesta

Sending

  • Send a one-off message to a client picked by name, email or client ID using the number on file, or to any number you type
  • Count segments shows how many SMS segments the message uses before you send, counted the way providers bill: 160 characters for GSM-7, 70 for Unicode, with emoji and extension characters counted correctly
  • Drop a saved template into the message on the Send screen and in the campaign builder
  • A texting panel on the client's profile, showing the number we would use, whether it is usable, their preferences and the last text, with a box to text them there and then
  • Numbers are converted to international format automatically, adding the country code from the client's country

Templates and triggers

  • A library of templates grouped by category, each switched on or off
  • Merge fields for first name, client name, company, invoice number, total and due date, product, domain, ticket subject and ticket number; an empty field is left blank, never shown as raw braces
  • Triggers for invoice created, invoice paid, service activated, service suspended or unsuspended and staff ticket reply
  • Each trigger can use its own gateway and respects the sending queue
Templates: reusable messages with the client, invoice and service details filled in for you
Templates: reusable messages with the client, invoice and service details filled in for you

Campaigns

  • Target clients by status and client group, and send now or schedule
  • Preview audience and cost shows exactly how many clients a campaign reaches and how many segments it will cost
  • Only clients who agreed to marketing texts are included, and progress shows sent and failed against the total
  • Cancel a campaign and the unsent messages are dropped

Staff alerts

  • Each administrator sets their own mobile number and the events that text them: new order, paid invoice, new ticket and cancellation requests
  • Alerts and manual sends are never held by quiet hours. Alerts that depend on a failure are not offered on Blesta, because Blesta raises no such event

Running it day to day

  • A sending queue that Blesta's cron drains in batches, with retries for messages the provider rejects and optional quiet hours in your company's timezone
  • History with search and filters for status, gateway and date; open any message to see its full text, the provider's reference and any error, and resend it in one click
  • Honest statuses: sent, failed, or unknown when a provider did not answer in time. No message is shown as delivered when it may not have been
  • A Health report that says whether a gateway is ready, what failed this month and whether the queue is draining
  • Test gateway: record messages in History without sending them, to try templates and triggers without spending credit
History: every text with its gateway and status, searchable and filterable by gateway and status
History: every text with its gateway and status, searchable and filterable by gateway and status

What your customers get

  • A Text messages page in their client area listing recent texts and what they have agreed to, with a link to change it
  • Tick boxes on their own profile and on the signup form, each label carrying its explanation
  • Choices that stick. After a client saves their profile the boxes show what they chose, and an opt-out still stands when they next save for any other reason
  • Simple, honest choices. A customer who unticks a category is not texted in it, even for messages already waiting

The pages render in Blesta's client portal theme, and their wording can be changed in a file that survives updates.

The customer's Text messages page: which kinds of text they receive, and the messages they have been sent
The customer's Text messages page: which kinds of text they receive, and the messages they have been sent

Security built in

  • Provider credentials are stored encrypted and never shown again after saving
  • A disabled gateway never sends, even if a trigger names it
  • Number and message go only to the provider you connected. Nothing about your clients comes to us

One product, every feature

PD SMS Manager is one paid module with everything included: all gateways, triggers, campaigns, staff alerts and client preferences. There are no tiers. It installs into PD Modules in one click and uninstalls cleanly.

If your subscription ever lapses, your data is kept. After a 14-day grace period admin features lock, then customer-facing features stop, and automatic texts and campaigns pause until you renew, when the queue resumes and nothing is lost.

Requirements

  • Blesta 6 or later on PHP 8.2 or later, with the ionCube Loader and cron running
  • An account with at least one SMS provider
  • PD Modules, the free control panel every PD module installs into

Questions

Which SMS provider does it use?

Yours. Connect the gateway you already have and pay them at their rates — we are not reselling messages, so there is no markup between you and your provider.

What can trigger a message automatically?

The billing and service events that need a phone rather than an inbox: a new invoice, a payment received, a service activated or suspended, a reply to a support ticket. Each trigger is switched on individually, so you send only what you mean to.

Can I message customers about something other than billing?

Yes. Campaigns send to a filtered list — your active customers, or one client group — so maintenance notices and similar announcements do not need a spreadsheet.

Do customers get a say in what they receive?

Yes. Each client manages their text-message preferences on their own Account Details page, beside their email preferences, and every automatic trigger honours them. You choose which preferences are offered and whether each starts on or has to be agreed to — promotional messages are agreement-only, as prior consent requires. Messages you send by hand are unaffected.

Will messages include the customer's details?

Yes. Templates can include name, invoice number, amount, due date and service details, so a message reads as though it was written for that person rather than broadcast.

Can I be alerted rather than the customer?

Yes. Admin alerts go to your own number for the events you care about, which is the difference between finding out about a failed setup or a cancellation request now and finding out tomorrow.

What happens if a message fails to send?

The failure is recorded against the message with what the gateway reported, and it is visible in the module's activity rather than disappearing. Customers can also see on their Text messages page whether each message was sent.

What do I need on my server?

PHP 8.2+ and a working WHMCS cron — the cron is what sends queued and triggered messages. Your gateway is reached over its standard HTTPS API.

Can clients use text messages for two-factor authentication?

Yes. The module adds a text-message second-factor method to WHMCS for clients and for your own staff, using the same SMS gateway as everything else — no separate service and no per-user fee. You choose the code length and how long a code stays valid. Your customers see it as “Text Message” in their security settings.

What if a client is locked out of their account?

They can use the backup code WHMCS gives them when they switch it on. Failing that, you turn two-factor off for that person under Clients → Manage Users, and they sign in with their password and set it up again. It affects only that person, not others sharing the account.

What happens if my subscription lapses?

Nothing of yours is touched, and nothing is deleted. The module steps down in stages instead: a 14-day grace period where everything still works and you get a renewal reminder, then admin management locks while your customers carry on being served, and only after that do the customer-facing features stop — behind a neutral "temporarily unavailable, please contact support" message that never mentions licensing to your customer. Anything the module provisioned keeps running in your own account throughout, and your data and settings stay exactly where they are. Renewing restores everything immediately.

What data leaves my server?

To send a text, the recipient's number and the message go to the SMS provider you connected — your own account with them, under your own agreement with that provider; nothing about your clients comes to us. Apart from the texts themselves, which your SMS provider carries, your customers' data stays in your WHMCS. To confirm your licence, the platform sends us four things and nothing else: your licence key, the domain, your server's own IP address and the directory it is installed in — the four values recorded against your licence in your client area. Alongside that we see which module and version you run and whether its licence is healthy, so we can ship compatible updates. We never receive your clients' personal data, your credentials, or the contents of your WHMCS. Crash reports are off unless you turn them on, and a diagnostic report is only ever sent when you send one, after showing you a preview you can edit.

How do I get help?

Open a ticket from your client area, or use Get help inside the PD Modules panel, which attaches a diagnostic report — you see a preview of exactly what it contains, and can exclude any part of it, before anything is sent. Support is included with an active subscription; bug reports are welcome whatever your licence state.

What’s new in 0.3.74

  • A client who refused every kind of text is no longer ticked for another kind by a second SMS module installed beside this one: only the module that manages client text preferences creates or changes them.
  • Amazon SNS: new Origination number field. A text to a UK number with no Sender ID and no origination number is refused with the reason instead of being recorded as sent, and the panel says "Accepted by Amazon SNS" because delivery is shown only in SNS's delivery logs.

Get your website online with PD Hosting

UK hosting, domains and support from a real team. From a first site to a full server.

Terms and Conditions  ·  Privacy Policy

PD Hosting is the trading name of Projektif Digital Ltd, registered in England and Wales, company number 12482555.

PD Hosting
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.