When optimistically dispatching agents at token creation, LiveKit allows for explicit agent dispatch to ensure proper separation and concurrent handling of rooms. Here's how it works: • Each agent can be identified using the

agent_name

field in the

WorkerOptions

. • You can use the

AgentDispatchService

to explicitly dispatch the agent to a specific room. • Alternatively, you can configure a participant's token to dispatch one or more agents upon connection using

RoomAgentDispatch

entries in the

RoomConfiguration

. This approach ensures that even if two users start rooms with the same agent identity (e.g., "abc123"), the agents are handled separately and can operate concurrently in different rooms. This method is particularly useful for scenarios like SIP inbound calls where explicit agent dispatch is recommended over automatic dispatch. If you have further questions or need assistance implementing this, feel free to ask! Sources: Web and mobile frontends | LiveKit Docs | Agent dispatch | LiveKit Docs