TopGit
GitHub Repo Review

DeskcommCRM: Open-Source WhatsApp CRM

melgarafael/DeskcommCRM
DTopGit review image for melgarafael/DeskcommCRM
Review by Topgit.dev for melgarafael/DeskcommCRM, with GitHub repository stats and README context.
Quick verdict

DeskcommCRM at a glance: DeskcommCRM is an open-source WhatsApp CRM with AI agents, multi-tenant CRM workflows, and self-hosted deployment. It is worth using when your team wants WhatsApp sales and customer support under its own infrastructure instead of a hosted platform.

Stars
โ˜… 5.3k
Forks
โ‘‚ 1.5k
Contributors
๐Ÿ‘ฅ 181
Language
TypeScript
License
MIT
Topic
โ€”
Updated
Nov 2026

Why WhatsApp sales need more than chat

Why WhatsApp sales need more than chat: DeskcommCRM solves the problem of managing leads, conversations, follow-ups, and handoffs when sales happen inside WhatsApp. It gives teams a shared sales funnel and automation layer instead of leaving customer context inside an inbox.

An AI sales operating system

An AI sales operating system: DeskcommCRM is a self-hosted CRM for conversational sales. Its AI agents can answer customers, qualify leads, update the sales funnel, trigger automations, and hand work to a human through WhatsApp or the Meta Cloud API.

AI agents, CRM workflows, and WhatsApp

  • โœ“AI agents use tenant-specific RAG, skills, memory, sentiment analysis, and spending limits to qualify leads and move them through the funnel.
  • โœ“The CRM includes contacts, pipelines, Kanban views, quick replies, follow-ups, routing, assignments, team roles, and a sales funnel with configurable vocabulary.
  • โœ“WhatsApp connections support QR-based WAHA sessions and the official Meta channel, with approved templates, media storage, reconnect handling, and STOP detection.
  • โœ“Workflow automation uses incoming webhooks and CRM events with WHEN/IF/THEN rules that can tag leads, change pipeline stages, assign agents, or send WhatsApp messages.
  • โœ“Multi-tenant security uses Supabase Postgres, tenant-aware RLS, server-side RBAC, audit logs, anonymization preferences, and optional MFA.
  • โœ“The platform exposes CRM operations through MCP, supports Nuvemshop for its e-commerce origin, and can switch AI providers independently for conversations and indexing.
How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history โ†—

Built for conversational sales teams

  • โ€ขE-commerce teams can use the Nuvemshop integration and automate follow-up.
  • โ€ขClinics can qualify patients, pass requests to staff, and use the configurable pipeline vocabulary.
  • โ€ขReal-estate agencies can track interested buyers, answer initial questions, and route qualified leads.
  • โ€ขTraining and information-product businesses can qualify prospects and keep follow-up work moving.
  • โ€ขService businesses can combine WhatsApp customer support with pipeline management, team assignment, and audited AI-to-human handoffs.

Install the CRM on a VPS

Install the CRM on a VPS: clone the repository, then run `bash hostgator-setup-kit/install.sh`. The installer asks for the domain, administrator credentials, database connection details, and an AI-provider key; it can install Docker when needed, generate secrets, apply the Supabase schema, create the admin user, start the stack, configure HTTPS, and install the automation cron. You need a VPS with Docker, a domain pointed to its IP, Supabase credentials, an AI provider account, and a WhatsApp number. The documented alternative is `curl -fsSL https://raw.githubusercontent.com/melgarafael/DeskcommCRM/main/hostgator-setup-kit/comecar.sh | bash`, which asks for confirmation before installing.

Strengths

  • โœ“The installation path is unusually concrete for a self-hosted CRM: the README documents VPS setup, credentials, database preparation, HTTPS, cron installation, and first login.
  • โœ“AI agents are connected to actual CRM work, including lead qualification, funnel movement, follow-up, routing, and human handoff rather than only answering chat messages.
  • โœ“The application supports both a fast QR-based WhatsApp path and the official Meta channel.
  • โœ“Tenant-aware RLS, RBAC, audit history, and optional MFA address important operational and privacy requirements.
  • โœ“Updates, backups, health checks, password resets, and rollback behavior are covered by dedicated scripts and runbooks.

Infrastructure you need to operate

  • โ–ณInfrastructure you need to operate: a VPS, Docker, a domain, Supabase credentials, an AI provider account, and a WhatsApp number are part of the documented setup.
  • โ–ณSelf-hosting makes the business responsible for backups, HTTPS, database availability, service monitoring, and keeping the installation reachable.
  • โ–ณThe free Supabase plan does not provide automatic backups, so `backup.sh` needs to be scheduled according to the README.
  • โ–ณThe application has a broad feature surface and several external dependencies, including WAHA, Supabase, Redis, an AI provider, and optionally Meta or Nuvemshop.
  • โ–ณThe free Supabase plan does not provide automatic backups, so `backup.sh` needs to be scheduled according to the README.

How DeskcommCRM compares

Kommo โ€” a hosted CRM named in the README as an alternative for teams that prefer a managed sales workspace.Octadesk โ€” a hosted customer-support option mentioned in the README for chat-based service operations.Intercom โ€” a hosted customer-support platform listed in the README as an alternative to DeskcommCRM.

Who should choose DeskcommCRM

Who should choose DeskcommCRM: businesses that sell or support customers through WhatsApp, want AI customer support and lead qualification inside the sales funnel, and are ready to operate a self-hosted CRM on a VPS. It fits teams that need multi-tenant CRM controls and own infrastructure more than they need a fully managed SaaS product.

Frequently asked questions

Is DeskcommCRM open source and licensed for commercial use?

DeskcommCRM is open source and uses the MIT license, which permits commercial use. The repository also provides the application code, installation scripts, architecture notes, and contribution documentation.

What does it take to install DeskcommCRM on a VPS?

DeskcommCRM needs a VPS with Docker, a domain pointing to its IP, Supabase credentials, an AI provider key, and a WhatsApp number. The documented installer handles the schema, administrator account, application stack, HTTPS, and automation cron.

Can DeskcommCRM connect to WhatsApp through both WAHA and the Meta Cloud API?

DeskcommCRM supports WhatsApp through QR-based WAHA Plus sessions and through the official Meta Cloud API. The Meta option uses approved templates and channel synchronization, while WAHA supports multi-number operation.

Which AI providers can DeskcommCRM use?

DeskcommCRM can use OpenRouter, Anthropic, or OpenAI for conversations, with the README also listing Requesty and Google in its AI stack. The provider is selected during installation and can be changed later in the interface.

Does DeskcommCRM support multi-tenant data isolation and LGPD controls?

DeskcommCRM includes tenant-aware Supabase Postgres RLS, server-side RBAC, audit history, anonymization preferences, and optional MFA. Its documentation describes these controls as part of its multi-tenant and LGPD-oriented design.

How do backups and updates work in DeskcommCRM?

DeskcommCRM can back up the database and WhatsApp sessions with `backup.sh`. The `update.sh` script checks for a newer release, backs up the database, updates code and schema, pulls the application image, and verifies health; the interface also exposes an update workflow.

Related repositories

Source & attribution

Source: GitHub repository melgarafael/DeskcommCRM (https://github.com/melgarafael/DeskcommCRM).

GitHub data ยท last synced Oct 24, 2026Reviewed by Henry
โ† Back to TopGit

Still deciding about DeskcommCRM?

One click hands the question to an AI along with this page โ€” see what it says about DeskcommCRM.

GitHub