Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Hi Amanda,

Thanks for the information

If we decide to split the queues and assign separate Copilots, I just had a couple of follow-up questions:

• Can a queue be linked to only one Copilot?

• Are there any financial implications we should be aware of when assigning separate Copilots to different queues?

Appreciate your guidance!

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Hi Ramsha,

You can have the same Agent Copilot assigned to different queues. The restriction is a queue can only have one Agent Copilot assigned to it.

There's no financial implications, it's just more of a admin overhead to create and maintain the queues.

Hope that helps!

Amanda

Hi Amanda,

Thanks for the information

If we decide to split the queues and assign separate Copilots, I just had a couple of follow-up questions:

• Can a queue be linked to only one Copilot?

• Are there any financial implications we should be aware of when assigning separate Copilots to different queues?

Appreciate your guidance!

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Noted, thank you for the information.

On a related note, 

I'm trying to explore AI Studio > Summarization Workbench, but both the "Save" button and the "Generate Preview" button are disabled in the UI.

I've already assigned the necessary AI Studio summaryConfig permissions, so I'm wondering if I might be missing a step.

Thanks!

Hi Ramsha,

You can have the same Agent Copilot assigned to different queues. The restriction is a queue can only have one Agent Copilot assigned to it.

There's no financial implications, it's just more of a admin overhead to create and maintain the queues.

Hope that helps!

Amanda

Hi Amanda,

Thanks for the information

If we decide to split the queues and assign separate Copilots, I just had a couple of follow-up questions:

• Can a queue be linked to only one Copilot?

• Are there any financial implications we should be aware of when assigning separate Copilots to different queues?

Appreciate your guidance!

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Simply click "config name" and update the configuration name, then it will enable the save button.

Noted, thank you for the information.

On a related note, 

I'm trying to explore AI Studio > Summarization Workbench, but both the "Save" button and the "Generate Preview" button are disabled in the UI.

I've already assigned the necessary AI Studio summaryConfig permissions, so I'm wondering if I might be missing a step.

Thanks!

Hi Ramsha,

You can have the same Agent Copilot assigned to different queues. The restriction is a queue can only have one Agent Copilot assigned to it.

There's no financial implications, it's just more of a admin overhead to create and maintain the queues.

Hope that helps!

Amanda

Hi Amanda,

Thanks for the information

If we decide to split the queues and assign separate Copilots, I just had a couple of follow-up questions:

• Can a queue be linked to only one Copilot?

• Are there any financial implications we should be aware of when assigning separate Copilots to different queues?

Appreciate your guidance!

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

Simply click "config name" and update the configuration name, then it will enable the save button.

------------------------------
Prem

Original Message:
Sent: 07-04-2025 08:46
From: Ramsha Shaikh
Subject: Multiple Agent Copilot Summarization behavior across Queues

Noted, thank you for the information.

On a related note, 

I'm trying to explore AI Studio > Summarization Workbench, but both the "Save" button and the "Generate Preview" button are disabled in the UI.

I've already assigned the necessary AI Studio summaryConfig permissions, so I'm wondering if I might be missing a step.

Thanks!

------------------------------
Ramsha Shaikh
Telecom/AI Engineer

Original Message:
Sent: 07-04-2025 08:39
From: Amanda Halpin
Subject: Multiple Agent Copilot Summarization behavior across Queues

Hi Ramsha,

You can have the same Agent Copilot assigned to different queues. The restriction is a queue can only have one Agent Copilot assigned to it.

There's no financial implications, it's just more of a admin overhead to create and maintain the queues.

Hope that helps!

Amanda

------------------------------
Amanda Halpin
EMEA Strategic Solutions Lead

Original Message:
Sent: 07-04-2025 08:08
From: Ramsha Shaikh
Subject: Multiple Agent Copilot Summarization behavior across Queues

Hi Amanda,

Thanks for the information

If we decide to split the queues and assign separate Copilots, I just had a couple of follow-up questions:

• Can a queue be linked to only one Copilot?

• Are there any financial implications we should be aware of when assigning separate Copilots to different queues?

Appreciate your guidance!

------------------------------
Ramsha Shaikh
Telecom/AI Engineer

Original Message:
Sent: 07-04-2025 04:26
From: Amanda Halpin
Subject: Multiple Agent Copilot Summarization behavior across Queues

Hi Ramsha,

Summary configurations are applied at the Agent Copilot level, so if those different queues have different Copilots assigned then yes, they could have different summary configurations.

In your scenario, you have just one queue so you will likely have to create a summary template that works for all those teams on that queue. If the teams have strong needs for different summary outputs, they would need to be spilt out to a separate queue so a new Copilot could be applied.

Thanks,

Amanda

------------------------------
Amanda Halpin
EMEA Strategic Solutions Lead

Original Message:
Sent: 07-03-2025 12:27
From: Ramsha Shaikh
Subject: Multiple Agent Copilot Summarization behavior across Queues

Hi everyone,

With the new AI Studio Summarization Workbench release, I had a few questions about how to manage different model behaviors across multiple queues.

For example:

• Queue A may require a specific summarization approach or prompt customization.

• Queue B may need a completely different model behavior or summary style.

In this case, would the recommended approach be to create two separate Copilot configurations, each aligned to its respective queue?

I'd like to understand:

• What potential challenges or limitations might come with this setup?

• Currently, we have one Copilot supporting all queues, would splitting configurations have any financial implications?

• Most importantly, what would be the most optimized and scalable way to support different summarization behaviors across queues if needed?

Appreciate any insights or best practices from others who may have explored similar scenarios!

Thanks,

#ConversationalAI(Bots,AgentAssist,etc.)
#Implementation

------------------------------
Ramsha Shaikh
Telecom/AI Engineer
------------------------------