In development; production deployment is not confirmed.
What is being developed
The implementation uses a single entry agent per channel. One agent can orchestrate multiple channels. Microsoft Teams retains per-user agent selection.
Service continuity
Replacing the orchestrator preserves the channel and does not change the agent in existing conversations. Unlinking disables the channel and preserves its connection, widget and history. Agents with linked channels cannot be deleted.
Availability and next step
Technical documentation records this change as not yet published or applied to shared databases. Rollout requires coordinated API updates and migration. Wait for Zild confirmation for your environment before planning operational use.
Bring this idea into your operations.
Map the process, connect systems and evaluate outcomes with Zild.
Talk to an expert