We spend a lot of the working day in WhatsApp. The team coordinates in it, we send clients documents through it, and until recently most of that still happened by hand.
Copy a number, paste a message, attach a file, repeat. For a one-off chat that is fine. Across a team and a steady flow of clients it becomes a quiet tax on every day, and none of it was connected to the systems where the actual work lives.
The common reflex is to reach for a “bulk WhatsApp sender” and blast everyone at once. That is the fast way to get a number banned and, in the EU, to land on the wrong side of the law. The real question was never how to send more messages. It was how to connect WhatsApp to our own systems without breaking the channel.
The system we built
So we built our own: a self-hosted service that turns WhatsApp into a clean API our scripts and AI agents can call, on numbers we control. We use it for personal and internal automation, and we put it out in the open.
- Send from code. Internal tools now send messages, documents, and voice notes through a single API call instead of a person doing it by hand.
- Receive and react. Incoming messages reach our systems through webhooks, so an AI agent can read the context and draft a reply for a human to approve.
- Many numbers, one place. Several numbers run through one service, with history stored so nothing slips through.
- Self-hosted and owned. It runs on our own server. No third-party gateway holding our data or charging per message.
It is open source, so you can see exactly how the personal tier works: github.com/jgalea/pigeon
Two kinds of WhatsApp automation
This is where most people get it wrong. There are two different jobs, and they need two different tools.
- Personal and internal, low volume. Automating your own or your team’s numbers: notifications, internal workflows, a human-in-the-loop assistant, the few hundred conversations you already have. Lightweight and self-hosted. This is what we built for ourselves.
- High volume and customer-facing. Marketing, broad outreach, automated support at scale. This belongs on the official WhatsApp Business Platform, with approved message templates, customer opt-in, and real sender reputation. It is priced per message and it scales without burning your number.
Using the first kind of tool for the second job is the exact mistake that gets numbers banned and rules broken. They are not interchangeable.
Where the real work is
The value here is in the judgment, not the plumbing. Our internal messaging now runs through the tool, AI agents draft replies for a person to approve, and the engine is open source so the personal tier is there to inspect and run. The hard part was never the code. It was knowing where the line sits between what you can safely automate on your own number and what has to move to the official platform, handling reconnection, message delivery and history so nothing is lost, and engineering each side to hold up in production rather than break the first time WhatsApp changes something.
Want WhatsApp wired into your business?
Whether you need a quiet assistant on your own number or a compliant, high-volume channel for customers, the right build depends on the job, and the two are not the same. We build both, matched to what you actually need.
