Farstax
← All Stacks

Application Stack · customer-support

Chatwoot

Run a shared customer-support operation and let the workspace agent triage or assist with conversations through supported interfaces.

Workflows the agent can manage

  • receive support conversations
  • manage contacts
  • triage inbox
  • automate support follow-up

Agent operability

Editorial agent-readiness estimate: 5/5. This reflects documented interfaces and proposed workflows, not a successful installation or a support promise. Assessment date not recorded; verify upstream documentation before use.

  • REST — Application/client APIs
  • WEBHOOKS — Conversation/integration webhooks

Evidence consulted

  • Official deployment page publishes a production-oriented 8 GB / 4-core / PostgreSQL 14+ / Redis 7+ profile. [stated; https://www.chatwoot.com/deploy]
  • Official developer requirements separately state a 4 GB required RAM minimum and 4-core recommendation, so sizing must be revalidated. [stated; https://developers.chatwoot.com/self-hosted/deployment/requirements]
  • Official repository/developer docs describe self-hosting, APIs and webhooks. [stated; https://github.com/chatwoot/chatwoot]

Implementation notes

Adopt when multi-channel support is a real operating need; re-check the conflicting current sizing pages, connect only required channels and verify current API permissions before agent automation.

Licence / edition: MIT for the open-source project; enterprise features and commercial product terms are separate. Enterprise and paid self-host support features are separate from the community edition.

Resources: heavy class — Current official guidance is inconsistent: the Chatwoot deploy page lists 8 GB RAM minimum (16 GB recommended), 4+ CPU cores, 60 GB SSD, PostgreSQL 14+ and Redis 7+, while the developer requirements page states 4 GB RAM is the required minimum and 4 cores are recommended. Treat production sizing as heavy and re-check both current pages. (stated)

External prerequisites: provider credentials for selected messaging channels

Security: Upstream security policy supports only the latest version; deploy a current supported release and review advisories. Catalogue qualification is not a security certification; inspect current advisories, supported versions and deployment guidance before setup.