Choose the Right AI Partner for a Task

When you have several AI partners, choosing the right owner before handing over work reduces transfers and rework. Check three things: whether the role fits, whether the partner can take work now, and whether the channels and capabilities required by the task are ready.

Before you start

Write the intended result in one sentence. For example: review this week's customer feedback, produce a prioritized issue list, and stop for my approval when a product tradeoff appears.

Include the input, a reviewable result, and the point where the partner must wait for your decision.

1. Shortlist by role

Open AI Partners from the sidebar. Review partner names and roles, or search for a keyword from the task. For content work, start with content, research, or operations roles. For customer follow-up, look at sales, support, or customer-success roles. For technical diagnosis, start with engineering or technical roles.

When several roles fit, keep two or three candidates and compare their state and capabilities. Do not assign work from the name or avatar alone.

2. Confirm that a candidate can take work now

• Idle: available for a new task. Still confirm that its model, channels, and required capabilities are ready.
• Working: inspect recent activity and the original task first. Wait or choose another partner when important work is still running.
• Offline: unsuitable for urgent work. Confirm whether it should be online, then recover it or choose someone else.
• Error: keep the failure details and start recovery. Assign live work only after recovery and a small retest.

Runtime state is one operating signal. Idle does not prove that setup is complete, and Working does not prove that the original task has finished.

3. Check the partner's capabilities

Confirm what this task actually needs:

1. If the task receives or sends messages through Lark, WeChat, or another channel, confirm that the channel is connected and can open a conversation.
2. If the task creates content, searches for information, or handles a particular file type, confirm that the required skills, tools, or knowledge bases are enabled.
3. For long-running work or a large input set, confirm that the current model and workspace fit the job.
4. When the card shows Needs setup or a health problem, complete setup or diagnosis before using a live task as a test.

4. Hand over the task

Open the partner workspace, or send the task through a channel that you have already verified. Structure the instruction with four parts:

• Input: files, links, conversations, or a specific local folder.
• Action: organize, compare, draft, inspect, or follow up.
• Result: format, save location, and completion criteria.
• Approval point: stop before sending, publishing, deleting, paying, or taking an action that affects someone else.

Start with one independently reviewable piece of work. For a larger task, ask for a plan and the first reviewable result before continuing.

5. Verify the result where it belongs

Return to the agreed file, workspace, or channel. Confirm that the result exists, meets the criteria, and still waits at any required approval point. A Working state, a sent message, or a triggered task does not replace result verification.

If another partner needs to continue, hand over the verified material, current conclusion, and remaining questions together so the next partner does not have to reconstruct the context.

Done when

You can explain why this partner was chosen, the input, result, and approval point are explicit, the required capabilities are ready, and the final result has been checked in the agreed location.

Troubleshooting

• Two partners have a suitable role: choose the idle candidate whose capabilities and relevant context are already ready. You may ask both for a short plan, but do not let them execute the same live task in parallel.
• The partner is idle but cannot start: check its model, channel, skills, and input. Idle only means that no task is currently running.
• No result appears after handoff: inspect recent activity and the original task. Run a health check only when activity has stopped, and avoid duplicate submissions.
• A result exists but is not usable yet: identify the exact gap and expected change, then ask the same partner to revise it. Transfer only when a different capability is required.

Related pages

See Check AI Partner Status and Choose the Next Step for runtime-state decisions, Connect and Manage Channels for an AI Partner for channel setup, and Run Your First AI Partner Workflow with One Recurring Task for a complete first run.

Data boundary

Work data stays on your device by default; only channels you connect and model calls go online as the task requires.