Introducing RoyceTalk SMS: Native Bulk and Transactional Messaging for ERPNext

Most businesses that send SMS from an ERP don’t really send it from the ERP. They export a customer list to a spreadsheet, upload it to a separate SMS gateway’s website, and hope the numbers are still current by the time the campaign goes out. RoyceTalk SMS removes that gap: it’s an app that installs directly into ERPNext and sends through RoyceTalk’s SMS gateway using the Customer, Lead, Employee, and Supplier records already sitting in your system.

Why this needed to be a native app, not another integration

A disconnected SMS tool has three problems that don’t show up until you’re relying on it. The recipient list is only as fresh as the last export, so it drifts out of date. Nobody enforces who actually agreed to receive marketing messages, so “bulk SMS” and “spam complaint” become the same risk. And every send is a manual step, which means it eventually gets forgotten on the one day it mattered most — payroll day, an overdue invoice, a delivery update.

Building this as a real ERPNext app instead of a side tool fixes all three: recipients are read live from actual records, consent is a field on the record itself rather than a spreadsheet nobody maintains, and sends can trigger directly off ERPNext events instead of a person remembering to do it.

What it actually does

• One-click customer notifications. A “Notify Customer” button on Sales Invoice and Sales Order opens a pre-filled message and sends in two clicks — no separate tool, logged automatically against the document.
• RoyceTalk SMS Campaign. Bulk marketing SMS to Customers and Leads, with a live preview of exactly how many people will receive it and what it will cost before you commit to sending.
• RoyceTalk Operational Broadcast. A separate tool for internal messages — shift changes, purchase order updates — to Employees and Suppliers. Kept deliberately apart from marketing sends, because internal operational messages and customer marketing shouldn’t share the same rules.
• Balance monitoring. An email alert to your admins before your RoyceTalk balance runs out, instead of finding out because sends started silently failing.
• A full delivery log. Every message sent through any of the above — status, cost, and RoyceTalk’s own message ID — in one place.

Consent rules built in, not bolted on

Marketing SMS to a Customer only ever goes out if that Contact has been explicitly marked as having agreed to receive it — off by default, no exceptions, no setting to bypass it. That’s a deliberate choice, not an oversight: a bulk-send tool that can’t tell the difference between “customer” and “consented customer” is a compliance problem waiting to happen, and we built the consent check into the query itself rather than trusting someone to remember it at send time.

Who this is for

If you’re running RoyceERP or any ERPNext instance and currently sending customer or staff SMS through a separate gateway’s website, this closes that gap — messages tied to the records you already maintain, sent from inside the system you already use.

How to install RoyceTalk SMS → · See RoyceERP → · Talk to us →