Yeah I get the pain trying to serve multiple clients with a single inbound agent while still giving each their own voice/config is exactly where things tend to break down. I’ve worked around this before by dynamically injecting client-specific settings at call time (similar to outbound behavior), even when the platform didn’t natively support it. Happy to take a closer look at your setup there’s usually a clean way to solve this without spinning up 100 agents. @Q4