Teams pair WhatsApp channels, monitor health, and keep customer entry points visible.
Product guide
ReplyBox gives teams a shared WhatsApp workspace with ownership, status, routing, automation, and customer context built around every conversation.
Teams pair WhatsApp channels, monitor health, and keep customer entry points visible.
New conversations move through assignment, status, tags, search, pins, and ownership.
Messaging supports rich WhatsApp types, internal notes, activity, calls, and customer history.
Broadcasts, scheduled sends, public API tokens, outbound webhooks, and integrations connect ReplyBox to the wider stack.
Core surface
Conversations are the primary work unit: assign, tag, pin, star, search, resolve, and keep customer context close.
Open inbox guideAgents send text, media, voice notes, documents, locations, replies, reactions, edits, revokes, and group mentions.
Open messaging guideWhatsApp connections are paired, monitored, migrated, and routed so teams can operate without sharing one phone.
Open channels guideContact records, CRM details, tags, and activity help agents understand who they are talking to before they reply.
Open CRM guideInternal notes and activity keep operational context inside the conversation without sending it to WhatsApp.
Open notes guideTeams send paced broadcasts and scheduled messages with audience controls based on contacts and tags.
Open broadcasts guideAdmin layer
Workspace identity
Each workspace can optionally have a logo shown in the workspace switcher and the workspace list; when absent the UI falls back to two-letter initials.
Upload, Replace, and Remove all live there.
Uploads are decoded and re-encoded to a 256×256-or-smaller WebP before storage.
org:manage edits them
Workspace logos are visible to workspace members; only users with org:manage can upload, replace, or remove them.