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

# Channels

> Every channel is built to write the same customer record - voice and chat in production today, messaging channels in build.

Voice, chat, WhatsApp, SMS and email are different ways to reach the same
human. The design goal is that every one of them writes the same spine -
entity, conversation, interaction, outcome, event - so adding a channel
changes routing, not architecture. Voice gets there first: it is in
production on the [Calling Engine](https://docs.unpod.ai/telephony/concepts/calling-engine.md). Chat is in
production as an API. The messaging channels are in build - see
[Status](#status).

Two kinds of connector, and the distinction matters. **Channel connectors**
(WhatsApp, email, SMS, web chat) carry conversations - they deliver
interactions to an entity and back. **System connectors** (Google Sheets
and Shopify today) push and pull rows - they sync records with the Context
Engine but never carry a conversation. A Sheets sync updates rows; a
WhatsApp message extends a conversation. Same backend, different verbs.

## The primitives

| Primitive | What it is | Where it lives today |
| - | - | - |
| Messages | One unit of content on any channel - a WhatsApp message, an email, an SMS, a chat turn | Web chat via the [Chat API](https://docs.unpod.ai/get-started/chat); WhatsApp, SMS and email in build |
| Identities | The per-channel addresses (phone number, email address, WhatsApp ID) that resolve to one entity | [Entities](https://docs.unpod.ai/context/entities.md) |
| Connectors | The bindings to each channel provider - and to systems like Google Sheets and Shopify, which sync rows rather than carry conversations | Per channel; see [Status](#status) |
| Routing | Which channel, which identity, which agent handles the next touch | Voice routing in [Telephony](https://docs.unpod.ai/telephony/introduction.md); cross-channel routing in build with [Conversations](https://docs.unpod.ai/context/conversations.md) |

Voice is a channel too - the largest one. It has its own component page
because the rails underneath it are deep: see the
[Calling Engine](https://docs.unpod.ai/telephony/concepts/calling-engine.md).

## On the spine

Channels sit in the Talk layer: they reach the human. An inbound message
resolves its sender identity to an entity, lands in that entity's
channel-neutral conversation, and runs as one interaction; an outbound
message is an interaction routed out through the channel the entity is
reachable on. Every delivery, reply, and failure emits an event, so the rest
of your system reacts to a WhatsApp reply exactly the way it reacts to a
completed call.

## What stays hidden

Provider quirks, wherever normalization is safe. WhatsApp template approval
mechanics, email bounce classification, per-carrier SMS segmentation, chat
transport details - these differ per provider and change under you. The
goal is a message with a status, with the connector absorbing the rest.
Where a channel has semantics you genuinely need (WhatsApp's 24-hour session
window, for one), they are meant to surface as explicit fields, not leaked
provider payloads.

## Status

Per channel, honestly:

* **Voice** - production, via the [Calling Engine](https://docs.unpod.ai/telephony/concepts/calling-engine.md).
* **Web chat** - production as an API: the [Chat API](https://docs.unpod.ai/get-started/chat)
  (text in, text out; you render the UI). No embeddable widget yet.
* **WhatsApp** - in build. Two-way agent conversations over the Meta Cloud
  API are coded end to end, but not generally available.
* **Email** - in build, through Gmail-connected flows. Unpod's own email
  sends platform notifications only.
* **SMS** - in build for conversations. A narrow in-call action (a template
  SMS to Indian numbers) is in production.
* **LinkedIn** - not available.

There is no SDK messages resource yet. Until there is, each channel is
reached through the paths linked here.

## Go deeper

> [card] [Calling Engine](https://docs.unpod.ai/telephony/concepts/calling-engine.md)
>
> The voice channel: owned rails, numbers, calls, streams.

> [card] [Conversations](https://docs.unpod.ai/context/conversations.md)
>
> The channel-neutral thread every channel writes into.

> [card] [Chat API](https://docs.unpod.ai/get-started/chat)
>
> Web chat today: text in, text out, one URL swap.

> [card] [Telephony](https://docs.unpod.ai/telephony/introduction.md)
>
> SIP, PSTN, and carrier-level details for the voice channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.