Skip to content

Channels

Channels let your agents communicate through the messaging platforms your team and customers already use. Instead of requiring everyone to log in to the Sprigr Team portal, you can bring your agents to Telegram, WhatsApp, or Slack (through the Slack marketplace app).

Once a channel is connected, messages from that platform flow into Sprigr Team automatically. The agent responds in real time, and the conversation appears in the agent’s conversation list on the Chat page, where you can read it.

Channels are configured per agent. Open the agent’s settings page and find the Channels section. Each channel appears as a card you can expand, configure, and toggle on or off. The toggle and the credential fields are shown only to organisation owners and admins.

Each channel type has its own setup process. Select the channel you want to configure below.

WebChat is the built-in chat surface. It is always available inside the Sprigr Team portal, so anyone with portal access can chat with the agent from the Chat page without any setup.

  1. Open the agent’s channel settings

    Go to the agent’s settings page and find the Channels section. Expand the WebChat card.

  2. Enable WebChat (optional)

    WebChat works through the portal without being enabled. Toggle it on only if you want to record it explicitly in the agent’s channel configuration for programmatic access.

Some ways to reach an agent do not have a card on the agent page:

  • Website chat — A chat widget on a website hosted by Sprigr, so visitors can talk to an agent. See Websites.
  • Webhook — An inbound webhook that delivers a payload to an agent or workflow. See Inbound Webhooks.
  • MCP — External AI clients (Claude Code, Claude Desktop, Cursor) that talk to an agent through the MCP server. See MCP.
  • Internal — Agent-to-agent traffic such as delegation and team-chat mentions, which never leaves the platform.
  • Voice chat — Inside the portal chat, an agent can speak its replies aloud, and hands-free mode listens, sends after a pause, and speaks back. See Chat.

Once configured, you can manage the agent’s channel cards from its settings page:

  • Enable or disable a channel with its toggle. Its settings and saved credentials are kept. For Telegram, save the bot token again after turning it back on (see above).
  • Update credentials if tokens or secrets change. Secrets are encrypted and stored securely; enter a new value to replace the old one.

Conversations from Telegram and WhatsApp appear in the agent’s conversation list on the Chat page. The Inbox holds email and support-ticket threads synced from connected mailboxes and help desks.

Text works on every channel. Beyond that, the richer channels support attachments and interactive prompts:

  • Telegram — the agent can send text, photos, and documents, plus interactive decision buttons (inline keyboards). Messages you send to the bot must be text; photos and files sent to it are not picked up. Works in direct messages and groups.
  • WhatsApp — text, images, documents, audio, and video, plus interactive reply buttons, list menus, and native forms for structured questions. Works in direct messages and in groups once the group is linked with /agent. If an agent needs to message you outside WhatsApp’s 24-hour reply window, the message is sent with an approved template instead of being dropped; a file sent then arrives as its name and a link.
  • Slack — handled by the Slack app; see Slack (App).
  • WebChat — text, file attachments, and inline artifacts such as rendered documents, tables, and HTML panels (see Chat).

A single agent can be connected to multiple channels at the same time. For example, your customer support agent could be available in WebChat inside the portal, in Slack (through the Slack app) for internal staff, and on Telegram for customers, all at once.

The agent keeps a separate conversation per person per channel, so context does not bleed between unrelated conversations. A group chat on Telegram or WhatsApp is one shared conversation for everyone in the group.

  • Chat — Use the built-in chat interface for direct conversations with agents.
  • Inbox — Work through email and support-ticket threads from connected mailboxes.
  • Agent Settings — Configure which channels are enabled for each agent.
  • Decisions and approvals — See how agents ask users to pick options with buttons on each channel.
  • Creating Agents — Set up new agents to handle specific channels.