IOne agent, every channel

One AI agent on every channel, with one memory

Most platforms sell you a Slack bot, then a Telegram bot, then a WhatsApp bot. Three prompts, three memories, three bills, and none of them knows what the others said. A Clawployee is one agent that answers wherever it is addressed and remembers all of it.

Put one agent on every channelSee all use cases
  • Live in 5 minutes
  • BYO API key
  • No vendor lock-in
One agent at the centre, connected out to Slack, Telegram, WhatsApp and email
Fig. 1. One agent at the centre, connected out to Slack, Telegram, WhatsApp and email
One Tuesday, one agent, three channels

09:14 Slack #support Escalated ticket 4412 to Dana and drafted the customer update.

13:40 Telegram DM "What did you tell the 4412 customer?" It pastes back the exact reply it sent at 09:14.

17:02 Email Follows up with the customer on the same thread, signed from your domain.

No handover, no re-briefing, no copy and paste between bots.
8+
Channels built in
1
Agent, one memory
BYO
Model and key

IIWhat it does

Work that lands on your desk (or doesn’t, because the agent handled it).

  • Slack

    Channels, threads and DMs. It reads the thread it is replying in, so context comes free.

  • Telegram

    DMs and groups with your own BotFather token. Voice notes transcribed, files read.

  • WhatsApp

    Customer conversations on the channel most of the world actually answers.

  • Discord

    Community support and moderation, with per-server permissions.

  • Email

    A real mailbox on your domain. It triages, drafts, replies in thread and follows up.

  • Web, SMS, iMessage and Teams

    The same agent, the same memory, wherever the person you serve already is.

IIISkills

Arrives knowing its job

  • Shared memory across channels
  • Per-channel permissions
  • Threaded replies
  • Voice transcription
  • Scheduled messages
  • Escalation to a human
  • Approval rules

IVIn detail

Why one agent beats one bot per channel

A bot per channel is not a smaller version of the same thing. It is a different colleague every time. Each one starts the day with no idea what the others promised, so the customer explains twice, your team reconciles the difference, and nobody can answer the question "what did we tell them?" A single agent has one workspace, one instruction set and one running memory, and every channel is just a door into it.

VIn detail

What stays the same everywhere

  • Its memory. What it learned on Telegram at lunch is there in Slack at four.
  • Its instructions. One SOUL.md and one AGENTS.md, not six copies drifting apart.
  • Its skills. Attach a skill once and it works on every channel the agent answers.
  • Its guardrails. Approval rules and escalation paths apply per channel, from one policy.
  • Its model. One provider key, one model choice, one place to change it.

VIIn detail

What changes per channel

Tone and permissions, because they should. A community Discord and an executive inbox deserve different manners. You set the DM policy, the allowed senders and the approval level per channel, and the agent adapts its register without forgetting who it is.

VIIIn detail

You keep the accounts

You create the Telegram bot in BotFather, you install the Slack app in your workspace, the mailbox sits on your domain. Clawployees runs the agent behind them on managed infrastructure. If you ever leave, the channels are still yours, because they were never ours.

VIIIFAQ

Questions we hear a lot.

Your next hire doesn’t need onboarding.

Pick a role, plug in your API key, connect your channel. Live in five minutes. Free to start.

Put one agent on every channelBrowse all agents

IXKeep exploring