Platform Guide

Agents & channels

One control plane drives every agent: sessions, tasks, streaming, steering, and cancellation — across every channel your organization already uses.

The control plane

Sessions, tasks, streaming, steering, and cancellation are platform concerns, not per-agent code. An operator can watch a run, redirect it mid-flight, or cancel it, and the same controls work whether the agent is answering in web chat or on a phone call.

Channels

Email, SMS, WhatsApp, Slack, Teams, webhooks, and realtime voice are normalized behind one interface, with consent, delivery retries, human handoff, and cost attribution built in per channel. Putting an agent on SMS is a deployment, not a messaging-infrastructure project.

Handoff and cost

Escalation to a person is a first-class path rather than a fallback: the conversation, its evidence, and its history transfer intact. Cost is attributed per conversation and per channel, so the economics of running an agent on voice versus email is something you measure rather than estimate.

See Agent Studio for the product surface, or Agents & skills for the SDK contract.