Product guide
Documentation that matches the implemented product.
This overview describes the current workspace, CRM, messaging and operations model. Provider-specific setup still requires the operator’s application credentials and approved provider assets.
Start with a workspace
Create or select a workspace, invite active members, configure roles and keep the global workspace switcher as the tenant context for every child page.
Connect provider accounts
Use Platforms to authorize supported channels, select provider assets and review health, permissions, token expiry and reconnect guidance.
Operate the shared inbox
Claim or assign conversations, select an eligible delivery channel, use templates and quick replies, attach scanned media, and recover failed or ambiguous deliveries.
Build ordered automations
Automations are ordered human-configured steps. The current worker supports the trigger and action catalogue shown in the editor; arbitrary graph branches are not advertised.
Use developer contracts
Developer pages document scoped API keys, pagination, idempotency, error handling, signed webhooks and operational request evidence.
Deploy and verify
Run the frozen install, semantic type check, lint, tests and production build. Then execute tenant, Storage, queue, provider, billing and browser acceptance matrices in staging.