Close vs Wacrm
Wacrm is a narrower, WhatsApp-centered alternative that trades Close’s broader sales-communications suite for source access, self-hosting, and customization. Choose Wacrm when WhatsApp is the primary channel and your team can operate and adapt its own deployment; choose Close when built-in calling, email, SMS, task prioritization, meeting capture, or broader sales reporting are essential.
Decision guide
The practical reasons to choose either option, based on documented capabilities.
Choose Wacrm if
- WhatsApp-led sales teams needing a shared inbox linked to contacts and deals
- Teams requiring self-hosting, source-level customization, or control of their CRM data
- Agencies or operators wanting to fork and rebrand an MIT-licensed CRM template
Stay with Close if
- Representatives depend on native inbound or outbound calling, recordings, voicemail drops, or power and predictive dialing
- Sales workflows require integrated email and SMS rather than a WhatsApp-only inbox
- Teams need lead forms, a prioritized task inbox, meeting transcription, or an AI agent that calls and qualifies leads; these are not documented for Wacrm in the supplied material_replaced?
Deployment and operations
Wacrm is an MIT-licensed, self-hostable TypeScript application using Next.js and Supabase, with the official Meta WhatsApp Business API. It can run through Docker or on any suitable Node.js host; the documented managed route uses Hostinger, while a VPS is suggested for custom binaries or long-running workers. Operators must configure Supabase and Meta credentials, schedule a cron drain when automation Wait steps are used, deploy application updates, and apply new database migrations when the Git
Migration considerations
Wacrm supports CSV contact import. The supplied documentation says historical chat transcripts and pipeline history do not transfer automatically, so migration generally means importing contacts, recreating pipeline stages, and starting new conversation threads.
Feature fit
What Wacrm covers
- Contact records with custom fields
- Deal pipelines with staged boards
- Conversation-linked sales context
- Trigger-based workflow automation
- Pipeline and activity dashboards
- AI-assisted message replies
What’s different or missing
- Built-in voice calling and dialers
- Integrated email and SMS outreach
- Lead-capture forms
- Prioritized sales task inbox
- Meeting transcripts and notes
- AI calling and lead qualification
- Documented representative-performance reporting
Project snapshot
- GitHub stars
- 1,969
- Contributors
- 13
- Language
- TypeScript
- Last commit
- Aug 12, 2026
- Latest release
- Not available
Categories: Customer Relationship Management, Marketing Automation, Customer Support, Content Marketing, Sales Intelligence, Workflow Automation, Business Intelligence
Sources and editorial review12 linked sources
Public documentation supports this comparison. Automation assists collection and classification; editorial standards and corrections remain the responsibility of Kris.
Self-hostable CRM template for WhatsApp — shared inbox, contacts, sales pipelines, broadcasts, and no-code automations.
repository description · github.comThis repo is the product — clone or fork it to run your own CRM.
readme · github.comShared inbox on the official WhatsApp Business API — multiple agents working one number, per-conversation assignment, status, and notes.
readme · github.comNo-code automations — triggers on inbound messages, new contacts, keywords, or schedule; conditional branches, waits, tags, webhooks. Visual builder.
readme · github.comReal-time dashboard — response times, daily volume, pipeline value, cross-module activity feed.
readme · github.comPrefer containers? See docs/docker.md for the Dockerfile + Docker Compose setup.
readme · github.comwhen you need several channels in one inbox today (Kommo and Trengo both do email, Instagram, and Telegram; wacrm is WhatsApp only), when you need a formal help desk with SLA timers and CSAT surveys, when you want a one-click Shopify app, or when you would rather pay per seat than run infrastructure
verdict · wacrm.tech**Contacts + tags + custom fields**, CSV import, deduplication.
shared feature · github.com**Sales pipelines** (Kanban) with deals linked to conversations.
shared feature · github.com_Note: wacrm is MIT-licensed and runs anywhere Node.js does (Vercel, Railway, your own VPS). Hostinger is recommended, not required._
deployment · github.comIf the database schema changed, apply any new SQL files from supabase/migrations/ in the Supabase SQL editor first — migrations are idempotent.
deployment · wacrm.techContacts, yes — export them as CSV from your current tool and import them into wacrm. Historical chat transcripts and pipeline history do not transfer automatically between systems, so plan to carry your contact list and start fresh on threads. Rebuilding pipeline stages takes a few minutes.
migration · wacrm.tech
