What this page covers
Read this page first if you want the shortest path to understanding how Sippet is structured before diving into channel-specific setup guides. It explains:- how
sandboxandliveenvironments differ - the main objects your team works with
- the core workflows Sippet supports across channels
Live vs sandbox mode
Sippet gives each customer organisation alive environment and a sandbox
environment.
Use sandbox when you want to test safely without affecting your production
organisation or customer-facing workflows.
Use live when you are ready for real production traffic, operational usage,
and customer-facing activity.
Sandbox mode
Sandbox is for testing and rollout preparation. In sandbox:- you can test workflows without touching your live organisation
- outbound calls are restricted to verified team phone numbers
- each team member must verify their own sandbox phone before placing outbound calls
- saved AI agents can be promoted into a fresh live copy when you are ready
Live mode
Live is your production environment. In live:- changes affect your real organisation and production activity
- customer-facing workflows run against your real setup
- live access stays restricted until Sippet approves your legal entity
Core functionality
Contacts and conversations
Sippet keeps support activity tied tocontacts and conversations so your
team and AI agents keep context across channels.
That means you can:
- take a voice call and follow up later by WhatsApp or email
- keep notes, history, and channel activity attached to the same customer
- route the same contact between AI-led and human-led support
Omni-channel support
Sippet supports support operations across multiple channels:Call centerfor live inbound and outbound callsSMS & WhatsAppfor async messaging and follow-upEmailfor mailbox-based support workflowsDiscordfor community and product-support channels
AI agents and automation
Sippet is built around AI-assisted support, not just telephony. Core AI functionality includes:AI agentswith prompts, files, tools, and channel behaviorGitHubknowledge for product-aware answers and issue contextPlaybooksfor follow-up and operational automationTemplatesfor reusable messaging and outreach content
Integrations and settings
The platform also includes operational setup areas that shape how support runs:Integrationsfor WhatsApp, Discord, GitHub, and webhooksAI providersfor BYOK model accessVerificationfor sandbox phone verification and live approval readinessTeam membersfor operator and admin accessCustom SIP trunkingandCustom mailboxfor more advanced channel setup
How to use the docs
Use the docs in this order:- Read the overview and this page.
- Pick the channel or feature area you want to set up.
- Start with the feature overview page.
- Use the matching guide page for step-by-step setup.

