Phase 2 · Contacts & segments
Customer messaging that outgrows the founder’s phone.
One workspace for the conversations your business runs on: WhatsApp, Telegram, broadcasts, automations and the team behind them.
- Telegram
- Web forms
- Broadcasts
- Automations
See it in action
What CustomerDock does
Shared inbox
Every WhatsApp and Telegram conversation in one queue, assigned to whoever owns it.
Campaigns
Broadcast to a segment and let the sender pace itself inside each channel’s limits.
Automation & AI
Auto-replies, routing and follow-ups, with AI drafts for the teams whose plan includes them.
Contacts & segments
One record per customer, with consent history per channel and audiences that re-evaluate themselves.
Analytics
Volume, response times and campaign performance, broken down by channel and agent.
Roles that fit a real team
Owners, admins, managers, agents and analysts, each seeing exactly what they should.
Isolation you can audit
Workspaces are separated by database row-level security, not by a filter someone might forget.
Built multi-tenant from the first migration
Tenant isolation is enforced by PostgreSQL row-level security, so a workspace cannot read another workspace’s data even if the application layer is wrong. Platform staff get their own separate axis of authority, never a back door through disabled security.
- Row-level security policies on every tenant table
- Workspace creation is transactional: no half-built tenants
- Entitlements read from a plan matrix, never from a plan name
- Append-only audit log for every administrative action
- Single-use, expiring invitation tokens