CRM for WhatsApp is a free, open-source WhatsApp CRM that you install on your own server. It gives a team a shared real-time inbox for WhatsApp conversations, contacts with consent tracking, a deals pipeline, template campaigns to opted-in contacts, chatbot flows and an AI assistant, and it can run as a multi-tenant service with plans and online payments. It is MIT-licensed and has been public on GitHub since October 31, 2026.
CRM for WhatsApp is an EpiFive project. The source code is at github.com/epifive/whatsapp-crm, and it is listed with the other EpiFive repositories on the open-source projects page.
Who CRM for WhatsApp is for
Many customers would rather send a WhatsApp message than an email or a phone call. Once more than one person answers those messages, a single phone stops working: chats get missed, two people reply to the same customer, and nobody knows which conversations turned into sales. CRM for WhatsApp suits:
- Small businesses and online stores that answer product questions, orders and delivery queries on WhatsApp and want several team members on one number.
- Sales teams that want each WhatsApp conversation linked to a contact, a deal in a pipeline and follow-up tasks.
- Support teams that want assignment, internal notes, quick replies and chatbot flows for common questions.
- Software companies and resellers that want to offer a WhatsApp CRM to their own customers. The app is multi-tenant, with plans, trials, payments, white-label branding and a super-admin panel.
If you are comparing general-purpose CRMs as well, see HubSpot versus Zoho CRM versus Salesforce pricing.
Opt-in, templates and WhatsApp's rules
Before the features, the rules. WhatsApp is a personal messaging app first, and Meta protects it with policies that every business account has to follow. In general terms:
- People must opt in before a business starts a conversation with them, and they must be able to stop the messages.
- Business-initiated messages use approved templates. Outside the 24-hour window after a customer's last message, a business can only send message templates that Meta has approved.
- Quality matters. Messages that people block or report harm the business number.
CRM for WhatsApp has features that support these rules: consent tracking on every contact, 24-hour window handling in the inbox, template sync, creation and submission for approval, and throttled campaign sending. It is a tool for talking to customers who want to hear from you, not a bulk sender. Read the current WhatsApp Business Messaging Policy and Meta's terms before you start, because the policy, not the software, decides what you may send.
The app can also link a regular WhatsApp number by scanning a QR code, with warm-up, pacing and daily limits. Meta's official Cloud API is the route Meta supports for business messaging, so for business use start with the Cloud API, and check WhatsApp's terms before relying on a QR-linked number.
Feature overview
Real-time team inbox
The inbox is shared by the whole team and updates in real time. Conversations can be assigned to a person, and team members can add internal notes that the customer never sees, tags and quick replies. It handles media, read receipts and typing indicators, follows the 24-hour window and offers approved templates when a template is required.
CRM: contacts, deals and tasks
Contacts have custom fields, CSV import and export, segments and consent tracking. A drag-and-drop deals pipeline follows opportunities from first message to sale, tasks have reminders, and a contact timeline shows the history of each customer in one place.
Campaigns to opted-in contacts
Campaigns send approved Meta templates, which you can sync, create and submit for approval from inside the app. Campaigns can be scheduled, are sent with throttling, and report delivery live. Use segments and consent tracking so a campaign only reaches contacts who have opted in.
Chatbot flow builder
A visual flow builder creates automated conversations from menus, questions with validation, conditions, delays, assignment to a person, tags, deals, webhooks and AI replies. Flows start on a keyword, on a contact's first message or on a reply to a campaign. A common pattern is a welcome menu that answers simple questions and hands everything else to a person.
AI assistant
Each workspace connects its own OpenAI, Gemini or Claude API key. The assistant suggests replies, rewrites and translates messages, summarizes chats and can send auto-replies from a knowledge base. Review what auto-replies say before you turn them on, as you would with any AI that speaks for your business.
API, billing and administration
Every workspace has a REST API and signed webhooks. For running it as a SaaS, billing includes plans with limits and features, trials, Stripe, Razorpay, PayPal and bank transfer, coupons, taxes and invoices. A super-admin panel manages workspaces, plans, payments, a "view as owner" mode, branding, email templates and SMTP. The app can be white-labeled with your own app name, logo, color and favicon, is translation-ready with right-to-left support, and has a web installer.
Try the live demo
The demo is at crm-for-whatsapp-demo.vercel.app. The sign-in page has one-click demo logins for three roles:
admin@demo.test platform admin
owner@demo.test workspace owner
agent@demo.test team member
Password: demo1234
The data resets daily. Sign in as the agent to see the inbox as a team member would, then as the owner to look at contacts, deals, campaigns and the flow builder.
Install CRM for WhatsApp
Requirements
- Node.js 20.9 or newer (22 LTS recommended) and PostgreSQL 14 or newer, or Docker with Compose.
- A domain with HTTPS for production, because Meta only sends webhooks to HTTPS.
Local quick start
The README's quick start runs the web app and the background worker in two terminals:
git clone https://github.com/epifive/whatsapp-crm.git
cd whatsapp-crm
npm install
npm run dev # web app + realtime -> http://localhost:3000 (opens the installer)
npm run dev:worker # background worker, in a second terminal
The web installer at /install checks the server, connects the PostgreSQL database, runs the migrations and creates the platform admin, optionally with demo data. Until SMTP is configured in Admin > Settings, outgoing emails are saved as JSON files in storage/mail-outbox/.
Production with Docker
cp .env.example .env # set POSTGRES_PASSWORD, APP_KEY and APP_URL
docker compose up -d --build
Production on a VPS with PM2
npm ci
npm run build
pm2 start ecosystem.config.cjs
Then open the app in the browser and complete the web installer. An example Nginx configuration is in deploy/nginx.conf.
Command-line alternative to the installer
cp .env.example .env # set DATABASE_URL, APP_KEY, APP_URL
npx prisma migrate deploy
npm run create-admin -- --email you@example.com --name "Your Name" --password "a-strong-password"
npm run seed:demo # optional demo data
In production the app runs as two processes: the web app (npm start) and the background worker (npm run worker), which handles campaigns, QR connections, chatbot timers, reminders and billing. If the worker is not running, those jobs do not run.
Checklist before you go live
- The app runs on your own domain with HTTPS, and the Cloud API webhook points to it.
- Your WhatsApp Business account and number are set up through Meta's Cloud API, and you have read the Business Messaging Policy.
- Contacts imported from CSV carry their consent status, and campaigns are built from opted-in segments only.
- Message templates are approved before any campaign is scheduled.
- Chatbot flows and AI auto-replies have been tested on your own number.
- Both the web app and the worker are running, SMTP is configured, and the PostgreSQL database is backed up.
Hosted version and installation
If you would rather not run the server yourself, EpiFive can host CRM for WhatsApp for you, install it on your own server or customize it as part of custom application development. Other EpiFive projects are listed on the open-source page.
References
- CRM for WhatsApp repository and README: https://github.com/epifive/whatsapp-crm
- Full documentation (installation, connecting WhatsApp, billing, FAQ; open in a browser after cloning): https://github.com/epifive/whatsapp-crm/blob/main/documentation/index.html
- Live demo: https://crm-for-whatsapp-demo.vercel.app
- MIT license: https://github.com/epifive/whatsapp-crm/blob/main/LICENSE
- WhatsApp Business Messaging Policy: https://whatsappbusiness.com/policy/
- WhatsApp Cloud API documentation: https://developers.facebook.com/documentation/business-messaging/whatsapp/about-the-platform
This guide was researched and drafted with AI assistance and checked against the vendor documentation listed in its References. Read the maintained version and related guides on EpiFive.


Top comments (0)