Return from a Child Agent to a Parent Agent in Copilot Studio

Question

Return from a Child Agent to a Parent Agent in Copilot Studio

Phillips, Kaelyn 10

Hello!

I am building an agent in Copilot Studio and have multiple "child agents" that it goes to when seeking answers.

The challenge I face is that I can't get back to the "parent agent." I want the child to answer the question, but then the user may have other questions and I need to loop back to the parent to get the right answers.

How do I direct the child to connect back to the parent?

Thank you!

Karan Shewale 2,585 Reputation points Microsoft External Staff

2025-07-22T04:44:20.79+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.
Raghav Khanna 0 Reputation points Microsoft Employee

2025-07-29T12:55:24.13+00:00

I tried updating the Description field of the child to be more precise and added some examples. For example, I added "only invoke when..." and "such as..." in the description of the child agent. This worked for me!
Phillips, Kaelyn 10 Reputation points

2025-07-29T13:53:56.26+00:00

Thanks, Raghav! Did doing so bring you back to the Parent when you were done with the child?

4 answers

Your answer

Karan Shewale 2,585 Reputation points Microsoft External Staff

2025-07-22T04:44:20.79+00:00

Thanks for bringing this issue to our attention. We will check and update you soon.
Raghav Khanna 0 Reputation points Microsoft Employee

2025-07-29T12:55:24.13+00:00

I tried updating the Description field of the child to be more precise and added some examples. For example, I added "only invoke when..." and "such as..." in the description of the child agent. This worked for me!
Phillips, Kaelyn 10 Reputation points

2025-07-29T13:53:56.26+00:00

Thanks, Raghav! Did doing so bring you back to the Parent when you were done with the child?

Answer 1

Phillips, Kaelyn 10

Thank you, Karan. This is more clear. I have done the following:

1- In the Parent/ Router Agent, I have created a topic called Return.

The trigger is "It's redirected to" because I couldn't find another trigger that's closer.
It looks for the phrase "I have another question."

2- In my Child Agent, when I want to return to the Parent, I have the user click "I have another question."

Everything works up to that point. However, every time, I get "SystemError." as the code. It doesn't give me more information but that's what it tells me.

I've tried with two different Child Agents and I get the same thing.

Any thoughts?

Thank you!

Karan Shewale 2,585 Reputation points Microsoft External Staff

2025-07-24T10:06:51.1166667+00:00
Hi Kaelyn,

The "SystemError" you're encountering is a common issue with the manual return approach in Copilot Studio. This typically happens due to conversation context conflicts when trying to route back to the parent agent. Here are the solutions:

Solution:

Method 1: Use Transfer Action (Recommended)

In Child Agent:

Remove "I have another question" button

Add: "Transfer to agent" action

Select: Parent Agent

Done - no manual triggers needed

Method 2: Fix Manual Return

In Parent Agent:

Delete current "Return" topic

Create new topic with trigger phrases:

"I have another question"

"Continue"

"Main assistant"

Use Intent trigger, not phrase trigger

Root Cause: Conversation context conflicts between agents

Best Practice: Always use "Transfer to agent" action instead of manual user input for agent switching.

Try Method 1 first - it eliminates the SystemError completely.
Phillips, Kaelyn 10 Reputation points

2025-07-24T16:08:02.87+00:00

Thank you, Karan. Strangely, I don't have the ability to transfer to agent. I can transfer conversation, see the first picture below, but that simply sets up a message box. Because I don't have (nor do I really need) the Customer Service Center, I don't even have a way to set up a person/ agent to send the conversation to.

Likewise, in the Child Agent, I don't have a plugin for the Parent Agent, so I can't set it to return to Parent. As shown in the second picture.

I'm trying Method 2 now but not getting very far. Do you anticipate the interface will soon change to allow transfer to Parent Agent?

Answer 2

Lab Admin 2 0

This YouTube video demonstrates a modern, smarter method for calling multiple child agents and passing them to the parent agent; it eliminates the need for custom topics and actions, utilizing pre-built features and prompt instructions: https://youtu.be/00VI-wQB868

0 comments

Answer 3

Phillips, Kaelyn 10

Thanks so much, Karan, for this super detailed answer!

One challenge is this- I cannot connect the Parent Agent TO the Child Agent and the Child Agent TO the Parent Agent. It only allows the Parent Agent to connect if the Child Agent isn't already connected to an agent. So, as soon as I connect the Child Agent to the Parent Agent, the Parent can no longer connect to the Child.

And, if I don't connect the Child to the Parent, then I can't transfer from the Child back to the Parent.

Additionally, I tried having multiple topics in a single agent, but the topics are similar enough that the agent couldn't identify the triggers properly (no matter how detailed the instructions...)

Any thoughts?

Thank you!

Karan Shewale 2,585 Reputation points Microsoft External Staff

2025-07-23T10:04:37.7333333+00:00
Hi Kaelyn,

Thank you for that important clarification! You've identified a critical limitation in Copilot Studio's current agent architecture - the circular dependency issue. This is a known constraint that many developers encounter.

The Core Problem You've Identified

Copilot Studio Limitation:

Agent A can connect to Agent B OR Agent B can connect to Agent A

But NOT both - no bidirectional connections allowed

This prevents the parent-child-parent flow you need

Workaround Solutions

Hub-and-Spoke Architecture (Recommended) Instead of direct circular connections, use a routing agent: User → Router Agent → Child Agent A → Router Agent ↘ Child Agent B → Router Agent ↘ Child Agent C → Router Agent

Implementation:

Router Agent: Handles all user interactions and routing

Child Agents: Specialized for specific domains, always return to Router

No direct connections between child agents

Router Agent Logic:

Analyze user intent

Route to appropriate child agent

Receive responses back

Continue conversation

Conversation Handoff with Context Variables

Since you can't have bidirectional connections, use a handoff pattern:

Parent Agent:

1. Set context variables before transfer

2. Transfer to Child Agent (one-way)

3. Create a "Return Handler" topic that triggers on specific phrases

Child Agent: 1. Process the request 2. Set completion flag 3. End with: "Please type 'continue' to return to the main assistant" 4. Don't transfer back - let user manually return

User Experience: User: "Help with Topic A" Parent: [Transfers to Child A] Child A: [Provides answer] "Type 'continue' to return to main assistant" User: "continue" Parent: [Resumes] "I'm back! What else can I help with?"

Single Agent with Better Topic Differentiation

For your similar topics issue, try these topic separation strategies:

A. Use Entity-Based Triggers: Topic A: Trigger phrases + specific entities (e.g., "Product X") Topic B: Trigger phrases + different entities (e.g., "Service Y")

B. Add Context Prefixes: Topic A: "For account management: [user question]" Topic B: "For technical support: [user question]"

C. Use Conditional Logic: Single "Dispatcher" topic: 1. Ask: "What area do you need help with?" 2. Present options: Account | Technical | Billing 3. Route based on user selection

Alternative: Power Platform Integration

Use Power Automate as Orchestrator

Copilot Studio agents expose their capabilities via Power Automate

Power Automate flow handles the orchestration logic

Single chat interface powered by the orchestrating flow

Flow Logic:

HTTP Trigger → Determine Intent → Call Appropriate Agent → Return Response

This bypasses the connection limitations entirely.

Immediate Recommendation

Given your constraints, I'd suggest:

Try the Hub-and-Spoke with a Router Agent

If that's too complex, use the "manual return" pattern with context variables

For similar topics, implement the conditional dispatcher approach

The Router Agent approach gives you the cleanest user experience while working within Copilot Studio's current limitations.

Would you like me to detail the Router Agent setup, or would you prefer to explore the Power Automate orchestration approach?

This is definitely a gap Microsoft needs to address in future updates!

Answer 4

Hi Kaelyn,

This is a great question about multi-agent orchestration in Copilot Studio. Currently, there are some limitations with agent-to-agent handoffs, but here are the available approaches:

Current Solutions

1. Using "Transfer to Agent" Action (Recommended)

In your Child Agent:

Add a "Transfer to agent" action at the end of your topic

Select your Parent Agent from the dropdown

This creates a handoff back to the parent

Configuration:

Go to your child agent topic

Add action: "Transfer to agent"

Select: [Your Parent Agent Name]

Add a message like: "Transferring you back to the main assistant"

2. Parent Agent Topic Management

In your Parent Agent:

Create a "Welcome Back" topic that triggers after child agent returns

Use conversation variables to track context

Set up routing logic to handle follow-up questions

Example Flow:

3. Using Global Variables for Context

Before transferring to child:

In parent agent, create trigger:

Trigger condition: Global.ConversationContext = "ChildAgentComplete"

Response: "I'm back to help with any other questions!"

Current Limitations

Important Notes:

No automatic return: Child agents don't automatically return to parents

Manual transfer required: You must explicitly add "Transfer to agent" actions

Context loss: Some conversation context may be lost during transfers

Single direction: Each transfer is a one-way handoff

Alternative Architecture (Better Approach)

Consider restructuring your solution:

Single Agent with Multiple Knowledge Sources

Instead of multiple child agents, use:

Single parent agent with multiple topics

Knowledge sources (SharePoint, files, etc.) for different domains

Conditional topic routing based on user intent

Benefits:

No transfer complexity

Better context retention

Smoother user experience

Implementation:

Recommended Implementation

Step-by-step:

In each Child Agent topic:

End with: "Is there anything else I can help you with?"

Add: "Transfer to agent" → Select Parent Agent

In Parent Agent:

Create a "Welcome Back" topic

Trigger: After agent transfer

Message: "I'm here to help with any other questions!"

Test the flow:

User asks question → Parent routes to Child

Child answers → Transfers back to Parent

Parent ready for next question

Future Considerations

Microsoft is working on improving multi-agent orchestration, so this workflow may become more seamless in future updates.

Thanks,

Karan Shewale.

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.