You can configure both AI Agent Studio and Freddy AI Agent (Classic) simultaneously in your account to run different agents across different communication channels. With this setup, you can deploy a new Studio agent on one channel while keeping a Classic agent active on another.

To keep your message routing clear and prevent overlapping automations, a single channel (such as Slack, Microsoft Teams, or the Support Portal) can only host one agent type at a time. When an agent framework is active on a channel, that same channel is instantly locked out in the other environment.

Note: This feature is available only for Enterprise users. 

Manage Freddy AI Agent (Classic) configurations

Follow these steps to configure the AI agent:

1. Go to Admin > Freddy.

2. In the Freddy AI Agent (Classic) section, review the toggles for Freddy AI Agent (Classic) for collaboration apps and Freddy AI Agent (Classic) for Support Portal to verify their current operational statuses.

3. Review the info banner beneath the toggle if the control is grayed out to confirm whether an active deployment from AI Agent Studio is blocking classic activation on Slack and Teams.

Use cases 

Review these common configuration scenarios to understand how channel availability changes based on your configuration.

Scenario 1: Classic Agent active on Slack and Microsoft Teams

• Configuration: An administrator enables the toggles for Freddy AI Agent (Classic) for Slack and Microsoft Teams within the configuration settings.

• Result: When navigating to Agent Studio > Deploy, the options for Slack and Microsoft Teams are restricted.
  

Scenario 2: Studio Agents deployed on collaboration channels

• Configuration: One or more agents built within AI Agent Studio are deployed on Slack and Microsoft Teams.

• Result: When navigating to the Classic configuration menu (Admin > Freddy Features), the toggle for Freddy AI Agent (Classic) for collaboration apps cannot be switched on.

Scenario 3: Impact on Servicebot settings for Slack and Microsoft Teams

• Configuration: Admin enabled AI agent Studio on Slack. 

• Result: Under the global settings for Servicebot for Slack, the classic feature toggles for Freddy AI Agent are blocked from activation and get activated for Microsoft Team, displaying a corresponding channel conflict alert.

Scenario 4: Multi-workspace configurations for Slack

• Configuration: The organization utilizes a multi-workspace Slack environment where multiple distinct workspaces connect to a single instance.

• Result: The exclusivity rule applies directly at the individual workspace level. If workspace A and workspace B have an active deployment, they remain locked. However, the system allows deployment on Workspace C if it currently has no active agent assigned.