Check a bot connection from pairing to result

Connection setup and task execution are separate. A bot that verifies successfully can still route work to a teammate with a broken engine or missing files.

Work through these checks

1. Identity

confirm the bot and provider account. Record the evidence or the unresolved question before moving on.

2. Pairing

use the intended private chat. Record the evidence or the unresolved question before moving on.

3. Assignment

inspect the selected teammate. Record the evidence or the unresolved question before moving on.

4. Engine

run a desktop test task. Record the evidence or the unresolved question before moving on.

5. Round trip

send one harmless chat task and inspect its result. Record the evidence or the unresolved question before moving on.

Put the checklist to work

Use a short text-only task first so unsupported attachment behavior does not obscure basic connection testing.

Keep the checklist beside the task brief and the actual output. Mark a check complete only after inspecting the relevant file, setting or event. If a required check cannot run in the current environment, describe that gap and choose an appropriate next review rather than substituting a confident summary.

A boundary to remember

Telegram, Discord and Slack private-chat adapters do not turn group messages into tasks.

For the corresponding controls and troubleshooting steps, read the desktop help guide. These checks are a practical review aid; adapt them to the specific source material and intended use of your deliverable.