Choose theme
AI Resources
DeskcommCRM
DeskcommCRM brings WhatsApp conversations, lead pipelines, and AI agents into a self-hosted sales and support workspace. People can take over a conversation when the agent needs a human.
The repository provides the application source, an English overview, installation scripts, and release notes. Running it requires your own server and database; its AI features need a provider key that can be added later. Use this as a first read, not a recommendation. Open the original project before trusting details like terms, limits, privacy, cost, setup, or safety.
What it is
A CRM built around chat
The project combines a WhatsApp inbox, contacts, lead stages, follow-ups, and AI agents that can answer questions and use organization-specific knowledge. Teams can assign or transfer conversations to people.
Why it stands out
Agents and staff share the same workflow
AI agents can work inside the lead pipeline rather than sit beside it as a separate chatbot. The project also documents spending caps, assignment controls, audit records, and a human handoff path.
Availability
Source and setup are public
The repository declares an MIT license and publishes a VPS installer, development setup notes, and version tags. Hosting, database, AI-provider, and WhatsApp connection choices still need to be made by whoever runs it.
Why it matters
What makes it useful
DeskcommCRM puts AI replies alongside lead ownership, follow-ups, spending limits, and handoffs to staff. Teams using WhatsApp for sales or support can see how those controls fit together before deciding whether to run the system themselves.
What to know
Where it fits
It fits teams already using WhatsApp for sales or support and willing to run a server. The repository describes both QR-based WhatsApp connectivity through WAHA and Meta's official Cloud API, with different setup paths.
Notable points
What stands out
The project lists an internal MCP server for its own agents among shipped features. A public MCP interface for connecting outside agents remains on its roadmap. That distinction matters if your team already uses a separate AI agent.
Before using
What to review
Plan for a VPS and Supabase database. The project's installer offers a guided server path; an AI provider key can be added during or after installation to enable AI features.
Choose the WhatsApp connection path from the current project documentation. The QR route uses WAHA; the repository also describes Meta Cloud API. Check the setup and operating requirements for the path you intend to use.
Decide which staff and AI agents can see conversations, move leads, send follow-ups, and use organization knowledge before connecting real customer data.
Review the project's backup and update instructions. A self-hosted installation leaves server care and recovery with its operator.
Most detailed setup documents are in Brazilian Portuguese, although the project has an English overview.
Reader fit
Who may find it relevant
Teams comparing a self-hosted WhatsApp CRM with AI-assisted replies and human ownership of leads.
Builders who want to inspect the application, deployment scripts, and agent controls before adopting or adapting them.
Less suited to someone looking for a ready-to-use personal chatbot or a service that needs no server administration.
Editorial note
Why LifeHubber lists it
DeskcommCRM puts AI agents, a human inbox, and a sales pipeline in one project. For a team using WhatsApp for sales or support, the question is whether those controls fit its workflow and whether it can manage the server and data connections.
Source links
Source materials
Reader note
Before relying on this entry
LifeHubber lists entries to help readers inspect AI projects, not to endorse them or prove they are safe, suitable, accurate, maintained, or right for a specific use. We do not verify every entry in depth. Before relying on anything listed, review the original materials, terms, privacy practices, limits, and risks that matter for your situation.
More in Productivity
Keep browsing this category
Explore more productivity tools.
Penpot
penpot/penpot
An open-source collaborative design platform with an official MCP server that lets AI agents inspect and modify Penpot files, components, tokens, styles, layouts, and assets through hosted or local connection paths.
ffmpeg-skill
kajisho5/ffmpeg-skill
An agent skill and local FFmpeg toolset for cutting, captioning, adjusting, checking, and exporting video through structured commands, with a probe-first workflow and optional MCP interface.
MiMo Code
XiaomiMiMo/MiMo-Code
A Xiaomi MiMo terminal-native AI coding assistant built on OpenCode, with public source, docs, install paths, build/plan/compose agents, persistent memory, task tracking, subagents, provider configuration, and release assets.
For project maintainers
Listed here? You can use the badge.
If you maintain a project with a current LifeHubber listing, you may add the optional “Listed on LifeHubber AI Resources” badge to its README, docs, or website. No introduction or permission request is needed.
