# melgarafael/DeskcommCRM

Source: [GitHub](https://github.com/melgarafael/DeskcommCRM)  
Feed7 permalink: https://feed7.dev/p/deskcommcrm-0c300yq  
Published: Unknown  
Trust: Needs Review (needs_review)

## Why Included

DeskcommCRM is a self-hosted, multi-tenant WhatsApp CRM where AI agents can qualify leads, operate pipelines through MCP, and hand work to humans under audit and budget controls.

## Source Summary

DeskcommCRM combines WhatsApp, a multi-tenant CRM, and agents with **tenant-scoped RAG**, memory, executable skills, audited human handoff, and organization spending caps. The CRM is exposed through **MCP**, while RLS isolation tests gate CI.

## Practical Implication

Builders can study it as a concrete agent system: events enter an event_log, a scheduled worker drains them, and agents operate business state under RBAC and audit controls. Installation targets a Docker VPS; updates back up the database, apply a tagged release, and roll back the app image if it breaks.

## Agent-Ready Context

DeskcommCRM combines WhatsApp, a multi-tenant CRM, and agents with **tenant-scoped RAG**, memory, executable skills, audited human handoff, and organization spending caps. The CRM is exposed through **MCP**, while RLS isolation tests gate CI.

Builders can study it as a concrete agent system: events enter an event_log, a scheduled worker drains them, and agents operate business state under RBAC and audit controls. Installation targets a Docker VPS; updates back up the database, apply a tagged release, and roll back the app image if it breaks.

The repository makes broad operational and security claims, but the supplied material does not provide independent validation or workload benchmarks. Deployment still depends on Supabase, a model provider, WhatsApp infrastructure, cron health, and careful handling of production credentials.

## Connected Context

Feed7 judgment across 757 accumulated Signals:

DeskcommCRM turns several proposed context and orchestration patterns into one vertical, multi-tenant system: business events, scoped retrieval and memory, reusable skills, MCP operations, human handoff, spending limits, RBAC, audits, and CI isolation tests. It supports the value of a shared substrate, but narrows it to tenant boundaries and concrete operations; its broad claims remain unvalidated and its dependency chain adds operational failure points.

- [The Building Blocks of GTM Orchestration — Arman Vaziri, Ramp](https://feed7.dev/p/the-building-blocks-of-gtm-orchestration-arman-vaziri-ramp-1mjpli3) — DeskcommCRM implements the shared data, durable event processing, skills, and MCP substrate described for GTM orchestration, while adding explicit tenant isolation, spending caps, audit controls, and human handoff.
- [WTF Is the Context Layer? The Missing Infrastructure for Production Agents — Prukalpa Sankar](https://feed7.dev/p/wtf-is-the-context-layer-the-missing-infrastructure-for-production-agent-0t47xqf) — Its tenant-scoped RAG and memory are a concrete form of shared business context, but remain embedded in one CRM rather than the portable, versioned context layer proposed across changing agent harnesses.
- [TencentCloud/TencentDB-Agent-Memory](https://feed7.dev/p/tencentdb-agent-memory-0gx8nnn) — Both govern reusable agent context, but TencentDB treats conversations, skills, docs, and code as a general asset hub, while DeskcommCRM binds memory to tenant-scoped customer operations and RLS enforcement.
- [SkillProx: Self-Evolving Agent Skills via Proximal Textual Gradient Descent](https://feed7.dev/p/2608-07449v1-1co8km3) — DeskcommCRM’s executable skills create the maintenance problem SkillProx addresses: changes should be evaluated, rolled back on regressions, and pruned when low-value; the repository’s CI isolation tests cover a different but complementary control.

## Context Map

- Layer: tools
- Domains: coding, data
- Topics: mcp, skills, agent-memory

## Uncertainty

- The repository makes broad operational and security claims, but the supplied material does not provide independent validation or workload benchmarks. Deployment still depends on Supabase, a model provider, WhatsApp infrastructure, cron health, and careful handling of production credentials.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.