Core concepts
Workspaces, channels, contacts, templates, campaigns, conversations and the durable outbox — the vocabulary Servus is built on.
Last updated 18 June 2026
Workspace & tenant
A workspace (a tenant) is the isolation boundary for everything you create — channels, contacts, templates, messages, and team members. The tenant is always derived from your credential (the portal session or an API key), never from a request body, so data never crosses workspaces.
Channels
A channel is a connected account you send and receive from — a WhatsApp number, an SMS gateway phone, or an email sending domain. Each channel has a connection lifecycle (Pending → Connecting → Connected) and its credentials are encrypted at rest and never shown back to you.
Contacts, segments & consent
A contact is a person you can reach (a phone, an email, or both) with tags and a consent state. A segment is a saved filter over contacts (e.g. "has tag vip, opted in") that resolves to live membership and feeds campaigns. Opt-out is always honored — a contact who replies STOP is opted out, and sends to an opted-out contact are blocked.
Templates & campaigns
A template is a reusable, versioned message body with {{variables}} and an approval lifecycle. A campaign broadcasts an approved template to a segment or an explicit list, paced by the gateway as it drains the outbox.
Conversations & the outbox
Inbound messages thread into conversations — one contact on one channel — surfaced in the shared inbox. Every outbound send is persisted to a durable outbox before the API returns, then a gateway worker dispatches it asynchronously and records the real result, so a send is never silently lost.