Skip to main content
A conversation started from any channel is the same conversation, with the same agent, skills, permissions and record. Most channels live in the agent’s Channels pane (the CHANNEL row on the settings card). Email has its own switch beside the composer. What you see depends on what your organization connected and your user group’s switches.
Channels pane with Agents (Who can message this agent, Omni on, Any agent), Teams (Channels), API (Developer access) and Messages (off) sections

The Channels pane on an agent. Shown with sample data.

Every channel

  • Answers: in Slack, Teams, email, Telegram and WhatsApp (Telegram and WhatsApp on xpander cloud), the answer is the message itself. The agent publishes a live surface there only when you ask for a report, dashboard, scorecard or live view, or when its instructions say to.
  • Email: the Email switch (the mail icon beside the composer) gives the agent an address, <handle>@xpander.bot on xpander cloud. Choose who may write: Anyone, Listed senders or a Custom pattern, and whether to Reply to newsletters. Self-hosted installs can use their own domain.
  • WhatsApp and Telegram: switched per organization under Platform > Agents > Channels. A message sent mid-run steers the run.
  • Webhook: Developer access in the Channels pane covers REST and webhooks. Public webhook URL mints a URL that is itself the credential: anyone with it can POST and run the agent. Good for form builders, CI jobs and landing pages. Treat it like a password. Regenerate URL revokes the old one immediately. With ?asynchronous=true the call returns {"status": "Started", "task_id": ...}.
  • API: Developer access > API endpoint shows the address. conversations/invoke sends a message and returns the reply with the conversation record. /invoke starts tasks to read back later. Both take an organization API key, which can be scoped to named agents.
  • MCP: clients reach Omni at https://omni.xpander.ai/mcp, signed in with OAuth. It is a personal connection, not a per-agent setting. https://mcp.xpander.ai is a separate endpoint that exposes the xpander API over MCP (OAuth 2.1). It is not an agent. See Model Context Protocol.

Other agents

Who can message this agent decides which agents may start a conversation with this agent. Each conversation shows which rule allowed it.
Channels panel with Who can message this agent set to No agents and the Omni switch on, Teams channels, Developer access, and Messages on with Send on First available, Email checked and Who it can message set to Anyone in the organization

Agent settings > Channel > Configure: Who can message this agent, Teams channels, Developer access and Messages. Shown with sample data.

  • Omni: when on, Omni can find this agent and hand it a teammate’s request that matches its skills.
  • Other agents: Any agent, Selected agents or No agents. An @Agent mention in chat follows the same rule.
New agents start from the default in Platform > AI governance > Policies > Agents that can start sessions (Any agent or No agents, per organization or group). Each agent’s rule overrides it. An agent on Claude Code, Codex or OpenCode can also look another agent up by name or skill (xpsearch_agents_by_name_or_skill, one of its xpander built-in tools). It finds org-wide agents, and agents of a project the person it works for can reach, never private ones. It lists only agents whose rule above lets it message them, and from Slack, Teams and other channels only org-wide agents.

Post in Slack

An agent can act in Slack as part of its work: post in a channel, reply in a thread, react, share a text file, find a person, and read a channel @xpander is in or a thread by its link. Answering when someone talks to it in Slack works either way. Turn it on in the agent’s Channels pane, under Slack: Allow posting in channels. It is off by default, and only people who manage the organization’s channels can change it. Available on xpander cloud and Hybrid installs, where Slack runs through xpander cloud. On an Air-Gapped install it works only where your operator set up a Slack app; otherwise the pane says to ask the operator.
  • Send Slack messages as: Agent identity posts with the agent’s name and icon. Under Other identities, Each user posts from the Slack account of the person who runs the agent, and One selected user posts every run from one person’s account. Each person connects their account once with Connect my Slack; until then the agent posts as itself. A post from a person’s account names the agent and xpander. Where an install does not offer posting as a person, the options read Not available on this install yet.
  • Direct messages: lets the agent message a person privately too, not only post in channels.
  • Can post in: Any channel @xpander is in or Only these channels.
  • Advanced: Ask for approval before the first message to a new person holds that first message for the agent’s owner or an organization admin (off by default). Daily message limit caps posts per day (50 by default, at most 1000).
  • Replies: a reply in the thread under an agent’s channel post continues that conversation with the same agent, when the person replying may continue it. A message sent from a person’s account to another person is a plain DM: replies to it do not reach the agent.
  • In the task record the actions show as xpslack_send_message, xpslack_reply_in_thread, xpslack_add_reaction, xpslack_upload_file, xpslack_find_person and xpslack_read. They are xpander built-in tools, so switching those off removes them.

Direct messages

An agent can message one person on their own linked Slack, email, WhatsApp or Telegram (WhatsApp and Telegram on xpander cloud), for example to hand over a result or ask for input. Off until an organization admin turns on Direct messages in the Channels pane. Saving publishes at once.
  • Send on: First available (the first checked channel that delivers, in the order shown) or All selected. Slack and email start checked.
  • Who it can message: Only these people or groups, or Anyone in the organization. With no one picked, nobody.
When on, the agent gets the xpmessage-send action: one person per call, by email or user ID, on a checked channel.
  • Unlinked channels and channels switched off for the organization are skipped.
  • If nobody can be reached, nothing is sent and the agent is told why.
  • Every message links back to the conversation. Email subjects read <Agent> (agent) via xpander.
  • At most ten messages an hour per person per channel, platform notifications included.
Over the API: the direct_messages field of Update Agent.

What your administrator controls

Admins connect workspaces and tenants and switch each channel per organization under Platform > Agents > Channels. See Slack workspace and Microsoft Teams tenant. Which channel sections you may configure is set per user group under Triggers.
Every task appears in the Session Manager with its source, under the person who asked. Webhooks and schedules run as the agent’s background user. Slack and Teams channel conversations are listed in the organization’s tasks, direct messages in your personal sidebar. Organization switch changes are logged as Org Channels Updated in the Audit log.