> ## Documentation Index
> Fetch the complete documentation index at: https://sippet.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Core Features

> Understand Sippet's core product model, including live vs sandbox mode and the main workflows the console supports.

## 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 `sandbox` and `live` environments differ
* the main objects your team works with
* the core workflows Sippet supports across channels

## Live vs sandbox mode

Sippet gives each customer organisation a `live` 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 to `contacts` 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 center` for live inbound and outbound calls
* `SMS & WhatsApp` for async messaging and follow-up
* `Email` for mailbox-based support workflows
* `Discord` for community and product-support channels

## AI agents and automation

Sippet is built around AI-assisted support, not just telephony.

Core AI functionality includes:

* `AI agents` with prompts, files, tools, and channel behavior
* `GitHub` knowledge for product-aware answers and issue context
* `Playbooks` for follow-up and operational automation
* `Templates` for reusable messaging and outreach content

## Integrations and settings

The platform also includes operational setup areas that shape how support runs:

* `Integrations` for WhatsApp, Discord, GitHub, and webhooks
* `AI providers` for BYOK model access
* `Verification` for sandbox phone verification and live approval readiness
* `Team members` for operator and admin access
* `Custom SIP trunking` and `Custom mailbox` for more advanced channel setup

## How to use the docs

Use the docs in this order:

1. Read the overview and this page.
2. Pick the channel or feature area you want to set up.
3. Start with the feature overview page.
4. Use the matching guide page for step-by-step setup.

## Related pages

* [Sippet AI Console overview](/)
* [Call center](/console/call-center)
* [Integrations](/console/integrations)
* [Verification](/console/verification)