> For the complete documentation index, see [llms.txt](https://docs.concurrence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.concurrence.com/channels.md).

# Channels

- [Overview](https://docs.concurrence.com/channels/conversations.md): How voice, text, messaging, email, and Surfaces deliver a shared workflow while preserving distinct identity, consent, and completion rules.
- [Channel Program Readiness](https://docs.concurrence.com/channels/program-readiness.md): Review program permission, channel integration, delivery evidence, and recurring operational responsibilities before launching patient outreach.
- [Phone](https://docs.concurrence.com/channels/voice.md): Real-time phone-based conversations with conference-first architecture, emotion detection, and adaptive voice delivery.
- [Audio Pipeline](https://docs.concurrence.com/channels/voice/audio-pipeline.md): How speech recognition, emotion detection, filler speech, barge-in detection, and TTS work together in real time.
- [Emotion Detection](https://docs.concurrence.com/channels/voice/emotion-detection.md): How acoustic emotion scores, transcript analysis, rolling state, empathy tiers, and voice steering work in the live voice runtime.
- [Compound Emotions](https://docs.concurrence.com/channels/voice/compound-emotions.md): How the five-turn resolver produces scored compound-emotion signals from acoustic, transcript, and behavioral evidence.
- [Call Recordings](https://docs.concurrence.com/channels/voice/recordings.md): Workspace-scoped caller, agent, and merged stereo recordings with time-limited download links and best-effort availability.
- [Text Sessions](https://docs.concurrence.com/channels/text-sessions.md): Durable text conversations over the web API, SMS, iMessage, WhatsApp, and email, with channel-specific delivery behavior.
- [SMS](https://docs.concurrence.com/channels/sms.md): SMS channel for outbound and inbound text messaging through provisioned phone numbers.
- [WhatsApp](https://docs.concurrence.com/channels/whatsapp.md): Managed WhatsApp conversations with business-scoped identity, asynchronous replies, and a bounded customer-service window.
- [iMessage](https://docs.concurrence.com/channels/imessage.md): iMessage channel for patient communication through Apple's messaging platform.
- [Email](https://docs.concurrence.com/channels/email.md): Email channel with domain verification, inbound reply handling, thread continuity, and transactional and marketing use cases.
- [Surfaces](https://docs.concurrence.com/channels/surfaces.md): Agent-generated data collection interfaces delivered by email or web, with templates, progress tracking, and pending appointment requests.
- [Outbound](https://docs.concurrence.com/channels/outbound.md): Outbound paths for SMS and iMessage conversations and for direct voice calls, with the channel support, lifecycle, and retry rules of each.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.concurrence.com/channels.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.