Perfex CRM is good at storing customer data and quietly bad at making sure customers actually hear from you. Invoices sit unpaid because the reminder never went out, support tickets get resolved and never followed up, and the messages that do leave the building are rewritten from scratch each time, in whatever tone the sender was in that day. This article is about fixing that with Perfex CRM SMS notifications, plus email and WhatsApp, driven by templates, recipient groups, and scheduled delivery instead of somebody's memory.
Full disclosure: we build and sell the module discussed below, Custom SMS & Email Notifications for Perfex CRM. It has 688 sales on CodeCanyon and a 4.40/5 rating from 20 verified CodeCanyon reviews. Everything in this post sticks to what the module documents, and there is a section near the end on when it is the wrong tool for the job.
Why messaging belongs inside the CRM
The usual failure mode looks like this: someone exports contacts to a CSV, uploads it to a third-party blast tool, and within a month the list is stale, the opt-out state lives in two places, and nobody can say which customer got which message. Sending from inside Perfex avoids the split brain. The CRM already knows who your customers and leads are, which of their contacts are active, and which company each contact belongs to, so a message composed there can pull those fields directly and keep your team off blast tools that never see your CRM data.
The second reason is accountability. When a customer says "we never received a reminder," you want a message log with real counts, not a shrug. Communication that lives in the CRM leaves the same audit trail as everything else you do there.
How Perfex CRM SMS notifications work with this module
The module adds one compose screen that covers three channels:
- SMS through Clickatell, MSG91, or Twilio
- Email, with dynamic subjects and merge fields
- WhatsApp through the official Twilio WhatsApp Business API
You pick recipients manually, by selecting a saved recipient group, or by searching the customers and leads list dynamically instead of scrolling it. Every contact attached to the selected customer or lead receives the notification, and an active-contact setting narrows that to only a customer's active contacts. When WhatsApp is enabled, those messages route through Twilio rather than the built-in Perfex SMS gateway, and a dedicated WhatsApp settings page includes a test sender so you can confirm everything works before going live. An optional delivery badges setting surfaces WhatsApp delivery status on your messages.
Two smaller details matter more in practice than they sound. A delivery preview shows exactly how a message will look before it goes out, including the subject label and HTML rendering for email. And a live SMS counter tracks character count and message segments as you type, across both GSM and Unicode encoding. If one stray emoji has ever flipped a campaign to Unicode and multiplied your segment count, you know why that counter exists.
Templates, merge fields, and scheduling
Templates are where consistency comes from. You build a library of email and SMS templates, organize them into categories, and mark each one either private to you or shared with all staff. Merge fields, including {contact_firstname}, {contact_lastname}, and {client_company}, populate both email subjects and message bodies automatically, so "Hi {contact_firstname}" becomes a real per-contact greeting without anyone editing the text.
Scheduling is the automation half. Set a future date and time and the module delivers the message for you. Every scheduled send sits in a dedicated list where you can preview it, edit it, or send it now on demand. Message history logs every message with sent, failed, and scheduled counts and exports to CSV, and send actions, scheduled ones included, are recorded in the Perfex activity log.
Three playbooks you can copy
One framing note first, because it matters: this module's automation primitive is the scheduled send. Each playbook below hangs off a real CRM moment, an invoice going out, a task wrapping up, a ticket closing, but a person creates the send and the scheduler delivers it. That is workflow automation, not an event trigger engine, and the distinction comes up again in the limits section.
1. Invoice reminders
Create a "Billing" template category with a matched pair: an email template with a dynamic subject like "Payment reminder for {client_company}" and a short SMS version for the customers who never open email. When an invoice goes out, schedule the reminder in the same sitting, dated a few days before the due date. If the customer pays early, the scheduled list lets you preview and edit the pending send before it fires. At month end, review the failed count in message history and export the CSV so finance has a record of who was reminded and when.
2. Task and project updates
Set up a shared "Project updates" category so every staff member sends the same wording, and use the module's permissions to restrict sending to the staff who should be messaging clients at all. When a milestone or task wraps up, the assignee searches for the customer from the compose screen, picks the template, and sends. Email attachments are supported, so a report or deliverable can ride along with the update instead of arriving in a separate thread.
3. Ticket follow-ups
Resolution time is when customers judge you, and the day-after follow-up is where most teams go silent. After closing a ticket, schedule a short check-in for the next morning: "Hi {contact_firstname}, we resolved your request yesterday. Reply here if anything still looks off." Active-contact targeting keeps the send limited to the customer's active contacts, and where customers prefer WhatsApp you can send the check-in there and let the delivery badges show its delivery status.
Key facts
| Fact | Detail |
|---|---|
| Current version | 2.3.6, updated 2026-05-01 |
| Channels | SMS, email, WhatsApp |
| SMS gateways | Clickatell, MSG91, Twilio |
| Official Twilio WhatsApp Business API only | |
| Compatibility | Latest Perfex CRM, PHP 7.4 or higher; no coding required |
| Track record | 688 sales on CodeCanyon, 4.40/5 from 20 verified CodeCanyon reviews |
When this module is the wrong choice
The documentation covers composing, templating, recipient groups, scheduling, and logging. It does not document firing messages automatically the instant a CRM event happens, so if your requirement is "text every customer the moment an invoice is created, with zero human involvement," this is not that product, and we would rather say so here than in a support thread. Recipient groups are static lists you create, not dynamic segments that recompute themselves. Delivery costs sit with your SMS or WhatsApp provider account, not with the module. And the WhatsApp channel specifically requires the official Twilio WhatsApp Business API, so a team without Twilio is limited to SMS and email. If everything you send is a plain transactional email, the stock Perfex email system may already cover you.
Links
If you have questions about a playbook, a gateway, or whether this fits your Perfex setup, ask in the comments and we will answer.
Top comments (0)