🚧

Alpha feature

Call Copilot is in early testing. It's available to all users but may change before general availability. Share your feedback →

Call Copilot lets one copilot invoke another during a conversation. The calling copilot handles the overall workflow; the called copilot brings specialized expertise to a specific step. The user sees the exchange transparently — with a link to view the full copilot-to-copilot conversation.

---

How it works

1. You ask the calling copilot something that requires a specialist.
2. The calling copilot determines it needs the other copilot and invokes it.
3. The chat shows "Calling [Copilot Name]..." while the specialist processes the request.
4. The called copilot responds using its own system prompt, tools, and knowledge.
5. The calling copilot incorporates that response into its final answer.
6. A link in the chat lets you view the full copilot-to-copilot conversation.

---

Setting up Call Copilot

Only the copilot's owner can configure Call Copilot.

1. Open your copilot's settings.
2. Enable the Call Copilot tool in the tools section.
3. Click Add Copilots to select which copilots this one can call.
4. Save your copilot.

The copilots you add must be ones you own, copilots shared with you, official copilots, or public community copilots. Users of the calling copilot must also have access to any called copilots — access is validated at runtime.

---

Example use cases

Research → document creation — A strategy copilot calls a research specialist for competitive analysis, then incorporates the findings into a PRD or brief.

Data analysis → action planning — A management copilot calls a data analyst copilot for insights, then calls a project management copilot to turn those insights into action items.

Content + media — A content copilot calls an image generation copilot to create a visual, then assembles the full package.

Reusable specialists — A single JIRA specialist copilot configured to be callable by your product, engineering, and QA copilots — no duplicating the same capability across three copilots.

---

Alpha limitations

• Single-level depth — Called copilots cannot call other copilots.
• Manual configuration — You must explicitly configure which copilots can be called; there's no automatic discovery.
• Permission dependency — Users must have access to all copilots in the chain for the call to work.
• Same organization only — Cross-organization copilot calls are not supported.
• Ownership restrictions — Ownership cannot be transferred for copilots that have Call Copilot enabled or are configured as callable.

---

Troubleshooting

Copilot doesn't respond to the call — Verify the user has access to the called copilot, the copilot ID is correct in the configuration, and the called copilot hasn't been deleted or archived.

Permission denied — Confirm the user has viewer access or higher to the called copilot and that its sharing settings haven't changed.

---

Related pages

• Custom copilots — building and configuring copilots
• Alpha and beta features