Open-source product status

What WATeamInbox
includes today.

WATeamInbox does not have a tagged public release yet. Until it does, this page summarizes the features implemented on the main branch of the open-source repository.

Implemented surfaces

These features are present across the web app, API, database, and workers. Some require additional services, configuration, or the right workspace permissions.

01

Omnichannel inbox and connections

The current application brings WhatsApp linked-device and Telegram Bot conversations into one provider-aware inbox while preserving each channel's identity, delivery state, and capabilities.

  • WhatsApp QR pairing, history sync, reconnection, archival, presence, reactions, groups, and supported media.
  • Telegram bot-token setup, webhook ingestion, direct customer conversations, replies, and provider-specific delivery state.
  • Channel-neutral accounts, contacts, messages, workflows, search, and permission-aware routing.
  • Duplicate-customer review and merge, so a customer who writes on WhatsApp and Telegram reads as one person.
  • WhatsApp Status and Stories updates stay out of the inbox, Chats, and Groups.
  • Connection-scoped workers and adapters with durable command and event paths.
02

Team workflows and access

Workspace roles and granular permissions define who can see conversations, send, assign, manage connections, export data, or inspect operational history.

  • Owner, admin, and member roles with owner-managed permission overrides.
  • Contact assignment, assignment history, shared and private notes, tags, and CSV contact import.
  • Blocked contacts replace outbound actions until an authorized user unblocks them.
  • Workspace invitations with automatic join after email verification, audit logging, and access-aware search and exports.
  • Built-in remote MCP server for AI agents (ChatGPT, Claude, Gemini, Cursor) with scoped read-only or read + write tokens, covering search, conversations, contacts, notes, tags, assignment, sending, scheduling, broadcasts, quick replies, auto-reply settings, and SLA policies.
03

Business inbox tools

The web app and API include the business-facing tools represented in the repository, without implying that every capability is supported by every provider.

  • Quick replies with shortcuts, WhatsApp Business label sync and tag linking.
  • First-contact automatic replies, sent once when a new customer first writes in.
  • WhatsApp media galleries: send several photos or videos as one album.
  • Catalog and product sync with archive/restore and product visibility controls.
  • Scheduled messages and permission-gated broadcast jobs with pacing and quota configuration.
04

Analytics, notifications, and data

Operational views expose activity and response information while keeping PostgreSQL as the durable source of truth.

  • Dashboard metrics for messages, contacts, teams, engagement, response time, and resolution cases.
  • Calendar-aware response and resolution SLA policies plus breach views.
  • In-app and desktop notifications, optional Web Push, PostgreSQL full-text and fuzzy search, and CSV/JSON/ZIP exports.
  • Email and in-app alerts when a WhatsApp connection drops; the in-app alert clears once it recovers.
  • A faster inbox: cold-load splash screen, bounded chat pagination, fewer realtime refetches, and cheaper search highlighting.
05

Self-hosting and repository boundaries

The open-source product repository contains the development and single-host production baselines. The managed Cloud control plane and this public website remain separate from the MIT-licensed application.

  • Development Docker Compose for PostgreSQL, NATS, Centrifugo, and MinIO lives with the open-source product.
  • The product repository documents a production Compose baseline with Caddy, a readiness-aware API router for 1–10 homogeneous API replicas, private data services, secret files, migrations, backups, and monitoring guidance.
  • Channel workers use independently tagged artifacts and rollback-aware rollout gates; the single-host orchestrator remains a singleton.
  • The public website links to the managed Cloud application while keeping commercial plans, billing, and entitlements outside the open-source repository.
Questions? Message usWhatsApp · +65 8404 2683