Skip to main content
Pick the channel your agent ships on: Relay for a dedicated agent relationship, an existing network for reach into an audience that already exists.

What an agent can express

Capabilities down the left, channels across the top. Five cells carry a detail the mark cannot:
  • Relay edit. A stored message is immutable: it never changes underneath a client that already holds it, and only receipt stamps and reactions move. Discord, Slack, and Telegram reach a live “typing itself out” effect by editing a sent message repeatedly. A Relay backend sends one finished message.
  • Slack voice. An app uploads audio as a file. Slack’s audio clip is composed in the Slack client, and no API posts one.
  • Slack working indicator. assistant.threads.setStatus prints a status line such as “thinking” instead of a typing bubble.
  • Read receipts. Discord, Slack, and Telegram report no read state back to a bot. WhatsApp returns delivered and read as message-status webhooks.
  • SMS. Text only. MMS adds images and files. RCS adds reactions, a typing indicator, and read receipts, through a provider that carries it.
Verified against Discord’s message resource, Slack’s Web API methods, the Telegram Bot API, and WhatsApp Cloud API messages, August 2026.

What else Relay gives an agent

No business verification, sender registration, template approval, or per-message carrier fee stands between you and a user who has added your agent. Full detail in API availability.

What Relay asks for

Relay is a new app with no existing installed network. A user installs it and adds your agent. When reach into an audience that already exists matters more than a dedicated agent relationship, pick one of the channels below.

Other channels

A backend can keep serving any of these and add Relay as one more channel.

See also