Skip to main content
  • This topic is empty.
Viewing 0 reply threads
  • Author
    Posts
    • #1049

      For the last few weeks I have been building a WhatsApp integration for ERPNext. When I started, the idea was simple: link ERPNext to WhatsApp so the system could send a message. That was it.

      But the more I worked on it, the more obvious it became that a plain “message sender” was not what businesses actually need. People do not just want to fire off a single text. They want to reach the right customers, at the right time, with the right message, and they want all of it to happen inside ERPNext instead of in some separate tool. So the project grew into something bigger: a WhatsApp CRM and customer engagement platform built right into ERPNext.

      Here is where it stands today, where it is heading, and a few questions I would genuinely like the community’s help with.

      What the WhatsApp CRM Can Do Right Now

      The current version already covers the core of customer engagement and campaign management, all driven from inside ERPNext. Let me walk through each part.

      Keeping Your Contacts in Sync

      Everything starts with clean contact data. The integration pulls customer WhatsApp numbers straight from ERPNext, so you are always working from your real customer list rather than a copy that goes stale.

      It also tidies up the numbers for you. Phone numbers are stored in all sorts of formats — with country codes, without them, with spaces, dashes, brackets — and WhatsApp needs them in a consistent shape. The system normalises every number automatically, then matches it back to the correct ERPNext Customer. It also handles Prospect contacts, so people who are not customers yet are not left out of the loop.

      Running Campaigns Without Leaving ERPNext

      You can build a full WhatsApp campaign directly inside ERPNext. A few things this lets you do:

      • Reach out to customers who have gone quiet and not bought in a while.
      • Send messages to prospects you are still trying to win over.
      • Narrow your audience down by customer group, so the message only goes to the people it is meant for.
      • Personalise each message using variables, so it does not read like a mass blast.

      Personalisation is as simple as dropping a placeholder into the text. For example:

      Hello {{customer_name}},
      We have a special promotion available just for you.

      When the message goes out, the customer’s actual name takes the place of the variable. Small touch, big difference in how the message lands.

      Sending Safely With a Delivery Queue

      This is the part I am most pleased with. Instead of blasting messages straight from the screen — which can freeze the interface and cause problems on large lists — every campaign creates records in a WhatsApp Outbox queue. The messages are then sent in the background, one step at a time.

      The journey of a message looks like this:

      WhatsApp Campaign → WhatsApp Outbox → Background Processor → WhatsApp Gateway → WhatsApp

      In plain terms: you set up the campaign, the system lines up all the messages in a waiting list, a background worker quietly works through that list, and each message is handed off to WhatsApp. Because the heavy lifting happens behind the scenes, you can send to a large group of customers without the screen hanging or the send failing halfway through. It keeps things steady even when the volume is high.

      Scheduling Messages for Later

      You do not have to send everything the moment you hit the button. Campaigns can be scheduled for a future date and time, which is handy when you want a promotion to land on a particular morning or just before a sale starts.

      You can also set a delay between each message so they go out at a sensible, steady pace rather than all at once. The Outbox processes them in order, one after another, which keeps the sending pattern clean and predictable.

      Sending More Than Just Text

      Plain text is not always enough, so the integration currently supports three message types:

      • Text messages
      • PDF attachments
      • Images

      Any file you attach is stored inside ERPNext and then delivered through the WhatsApp Gateway, so your documents stay tied to the right records and nothing floats around outside the system.

      Where This Is Heading

      The long-term goal is not just a tool that sends WhatsApp messages. It is a full WhatsApp CRM and customer engagement platform for ERPNext — one that handles the everyday conversations a business has with its customers, automatically and from one place.

      Some of the features on the roadmap:

      • Invoice notifications — let customers know the moment an invoice is ready.
      • Payment reminders — gentle nudges for upcoming or overdue payments.
      • Delivery notifications — keep people informed about where their order is.
      • Customer follow-up automation — check in with customers without anyone having to remember to do it.
      • Loyalty point notifications — tell customers when they have earned or can redeem points.
      • Promotional campaigns — run offers and announcements at scale.
      • Product restock alerts — message interested customers the moment an item is back.
      • Lead nurturing workflows — stay in touch with prospects over time until they are ready to buy.
      • Customer support integration — handle support conversations through WhatsApp, linked to ERPNext.

      Why Build This in the First Place?

      The honest answer is that this is how a huge number of ERPNext users already talk to their customers. WhatsApp is where the daily back-and-forth happens — orders, questions, reminders, follow-ups.

      The problem is that all of this usually lives outside ERPNext. Someone copies a number, opens WhatsApp, types a message by hand, and then maybe makes a note about it somewhere. It is slow, it is easy to forget, and the record of what was said rarely makes it back into the system.

      This project is about closing that gap. The aim is to pull those everyday customer conversations into ERPNext, while keeping everything fast and reliable through the background queue so it holds up even as your customer list grows.

      I Would Love Your Feedback

      This is still very much a work in progress, and the direction it takes should be shaped by the people who would actually use it. So a few honest questions for the ERPNext community:

      • Would something like this be useful in your organisation?
      • Which WhatsApp workflows are you currently handling by hand, outside of ERPNext?
      • Which of the features above would matter most to your team?

      If you have thoughts, gaps you have run into, or features you wish existed, please share them. Real-world feedback is what will make this genuinely useful rather than just another integration.

Viewing 0 reply threads
  • You must be logged in to reply to this topic.