```json
{
    "title": "ERPNext WhatsApp Integration: Automating Customer Notifications via WhatsApp and SMS",
    "url": "https://aavatto.com/blog/erpnext-whatsapp-integration-sms-notifications/",
    "datePublished": "2026-10-15",
    "dateModified": "2026-10-19",
    "language": "en-US",
    "description": "How ERPNext WhatsApp integration and SMS notifications actually work — native setup, third-party apps, and what each one costs you in effort.",
    "author": "Aavatto",
    "publisher": "Aavatto - Frappe & ERPNext Experts | Custom Development, Implementation & Support"
}
```

# ERPNext WhatsApp Integration: Automating Customer Notifications via WhatsApp and SMS

ERPNext WhatsApp integration connects ERPNext to Meta's WhatsApp Business Cloud API — either through native Notification and WhatsApp Message doctypes or a marketplace app — so events like a confirmed order, an overdue payment, or a dispatched shipment trigger a WhatsApp message automatically, without anyone on your team sending it by hand.

SMS integration works the same way in principle but through a different, older mechanism (the SMS Settings doctype), and the two aren't interchangeable choices — they suit different situations, which is the part most guides on this topic skip past.

## What "WhatsApp and SMS integration" actually means in ERPNext

Two separate things get lumped under this phrase, and mixing them up is where most setup confusion starts.

WhatsApp messaging in ERPNext runs through Notification records — the same automation doctype used for email alerts — configured to fire on a document event (a Sales Order submitted, a Payment Entry created, a Delivery Note marked as shipped) and send via a WhatsApp channel instead of, or alongside, email. Behind that channel sits Meta's WhatsApp Business Cloud API, which means before any of this works, you need a verified Meta Business account, a registered WhatsApp Business phone number, and API credentials connected to ERPNext.

SMS runs through the older, simpler SMS Settings doctype, where you plug in a gateway provider's API URL and credentials (Twilio, MSG91, and most regional SMS aggregators are common choices), and ERPNext posts to that gateway the same way it would call any external API.

## How ERPNext WhatsApp integration actually works

The mechanism is straightforward once it's connected: a Notification rule watches for a document event, checks its condition (for example, only fire when a Sales Order's status changes to "Confirmed"), and sends a WhatsApp message using a template you've defined inside ERPNext.

The part that catches most teams off guard isn't the ERPNext configuration — it's Meta's own rules for the WhatsApp Business Platform. Any message your business initiates (not replying to a customer who messaged first) has to use a pre-approved template, and Meta's review of new templates can take anywhere from a few hours to a few days. Free-form, un-templated messages are only allowed within a 24-hour window after a customer messages you first — useful for support conversations, not for a scheduled dispatch notice sent three days later. Plan your template list and get it into Meta's review queue before you plan your go-live date, not after.

For businesses that want richer, two-way conversations — a customer replying to check order status, a simple chatbot flow, agents responding from a shared inbox — the native Notification setup isn't really built for that; that's where a dedicated WhatsApp Business app or a custom build against the Cloud API earns its cost. For pushing out one-way transactional updates, native is usually the right starting point.

If you're already comparing this against other ways ERPNext connects to outside systems, it sits inside the same [ERPNext integrations landscape](/blog/erpnext-integrations-payment-gateways-marketplaces-shipping/) as payment gateways and marketplace connectors — some paths are native configuration, others need custom API work, and the deciding factors are similar.

## Setting up ERPNext SMS notifications as a fallback channel

SMS doesn't carry the template-approval overhead WhatsApp does, which is exactly why it's still worth keeping configured even after WhatsApp is live: it reaches a phone with no smartphone, no app, and no data connection required, and it fails less mysteriously when it fails at all.

The tradeoff is cost and richness. SMS is billed per message with no free tier comparable to WhatsApp's service-window messages, carries no read receipts or media, and — for businesses sending to Indian phone numbers — requires DLT (Distributed Ledger Technology) registration with the telecom regulator for both your sender ID and your message templates before a gateway will deliver anything. That registration process is a real lead-time item, not a same-day setup, and it's worth starting in parallel with your WhatsApp template approvals rather than after.

## WhatsApp vs. SMS: which one for which message

FactorWhatsAppSMSSetup dependencyMeta Business verification + template approvalGateway account + (India) DLT registrationBest forOrder confirmations, dispatch updates, rich formatting, linksTime-critical or low-connectivity alerts, OTPsCost patternPer-conversation category pricing, varies by countryPer-message, no free service windowReliability without smartphone/dataNoYesRead confirmationYes (delivery/read status)No

Most businesses running both end up using WhatsApp as the primary channel for anything customer-facing and richer, with SMS as the fallback for OTPs, urgent alerts, or customers who haven't opted into WhatsApp messages at all.

If your team is still deciding whether this is worth building now or later, that's usually a five-minute conversation once we know what's triggering the notifications you actually need — talk to us about your integration and we'll tell you honestly whether it's a native configuration job or a custom build.

## Common notification triggers worth automating first

Teams that get the most out of this tend to start with a short list rather than automating everything at once:

Sales Order confirmation, sent the moment a quotation converts

Payment received acknowledgment, tied to Payment Entry submission

Delivery/dispatch notice, tied to Delivery Note or shipment status

Overdue payment reminder, on a scheduled check against Sales Invoice due dates

Internal alerts — low stock, approval pending — sent to staff rather than customers

Starting narrow makes it easier to catch template-approval issues or gateway misconfigurations on one or two message types before scaling to a dozen.

## Frequently Asked Questions

[Does ERPNext have WhatsApp integration built in, or do I need a separate app?](#collapse-7421)

ERPNext supports WhatsApp natively through its Notification and WhatsApp Message doctypes, connected to Meta's WhatsApp Business Cloud API. Marketplace apps exist too, mostly adding conversational features (two-way chat, agent inboxes) the native setup doesn't cover.

[How long does WhatsApp Business API approval take?](#collapse-7422)

Meta's review of new message templates typically ranges from a few hours to a few days, and can take longer if a template is rejected and needs resubmission. Build this lead time into your go-live plan rather than treating it as instant.

[Can I send WhatsApp messages without a pre-approved template?](#collapse-7423)

Only within the 24-hour window after a customer messages you first. Any message your business initiates outside that window needs a pre-approved template.

[Do I need DLT registration to send SMS from ERPNext in India?](#collapse-7424)

Yes — TRAI's DLT framework requires registering your sender ID and message templates before a gateway will deliver commercial or transactional SMS to Indian numbers, and that registration has its own lead time separate from ERPNext configuration.

[Is WhatsApp or SMS cheaper for notifications?](#collapse-7425)

It depends on volume and message type — WhatsApp's per-conversation pricing can be more efficient for richer, higher-value messages, while SMS is priced per message with no equivalent free service window. Neither is universally cheaper; it's worth costing out against your actual message volume.
				Getting notifications flowing usually isn't the hard part — deciding which channel, which triggers, and whether native configuration covers your case or you need custom logic is. Talk to us about your integration and we'll help you scope it against what you're actually trying to automate, not a generic checklist.