Choose Your First OpenClaw Messaging Channel
During OpenClaw setup, choose WhatsApp for a linked account, Telegram for bot DMs or groups, Discord for a server bot, or Slack for a workspace app. Enable one channel first and verify a round trip from the actual messaging app before adding another.
Link WhatsApp to the right account
Choose WhatsApp if the people testing your agent already use it and you can dedicate or explicitly approve the account being linked. Run openclaw onboard, select WhatsApp, and accept the plugin installation prompt if it appears. Complete the QR-link flow with the intended phone account. OpenClaw's gateway owns the linked session, so record which gateway and account you paired before moving on.
From a second, authorized WhatsApp account, send a harmless test message asking for a unique reply. Check that the reply arrives in the same conversation. If the gateway reports a connection but the chat stays silent, verify the linked account and check whether the inbound message reached the gateway before changing model settings.
Use the same mix of direct and group interactions on each eligible channel. A pilot dominated by easy direct messages can hide a failure in the intended group workflow.
WhatsApp - OpenClawUse Telegram for a bot identity
Choose Telegram when your pilot needs a bot identity for direct messages or groups. Select Telegram during onboarding, follow the bot setup instructions, and supply the bot token. Telegram defaults to long polling and uses pairing for DMs by default. Send the first DM from the intended tester account, approve that pairing, and send a fresh message to check the reply. Keep the token out of test messages and shared notes.
In an illustrative pilot with one operator and one private group, first verify that the operator's approved DM gets a reply containing the test word PINE. Then add the bot to the group and run a second test there using your planned mention rule. A passing DM and silent group point you toward group access or mention settings.
Count an acknowledged inbound event separately from a user-visible reply. That distinction tells you whether to investigate channel delivery or downstream processing.
Telegram - OpenClawTest Discord in the intended server
Choose Discord when your users already meet in a Discord server and the bot should answer in a specific server channel. OpenClaw connects as a Discord bot and supports both DMs and server channels. Install the Discord app, invite the bot to a test server, and configure the intended channel and mention behavior before inviting users. If you also need DMs, complete pairing for the test account.
Post a test request in the intended server channel and check that the reply lands there. Repeat in a channel you intend to exclude and confirm the bot stays silent. If DMs work while the intended server channel stays silent, check the bot's access to that channel, the server allowlist, and whether your test message met the mention rule.
Discord - OpenClawProve Slack access in a pilot channel
Choose Slack when your operators need the agent in an existing workspace. Install the OpenClaw Slack plugin, create the Slack app, and configure the tokens for the chosen transport. Start with Socket Mode if it fits your deployment, since OpenClaw uses it by default. Consider HTTP Request URLs when your team already operates a suitable endpoint and wants to route Slack events through it.
Enable a single test channel and send a message there under the mention rule you plan to use. Success means an authorized workspace user sees the expected reply in that channel. If a paired DM succeeds but the channel test fails, check the app's access to the channel, the channel allowlist, and mention gating before switching transports.
Slack - OpenClaw