Logs the agent into this queue so the platform can start routing interactions to them.
A promise that resolves when the agent is successfully logged into the queue.
AvayaInfinityAgentSdkError If the login request fails. * *
Whether the agent can log out of this queue right now.
Returns true when the platform rules allow logout (e.g. the agent is logged into CX,
has access to the queue, and is currently logged in). Returns false otherwise.
Logs the agent out of this queue so the platform stops routing interactions to them.
The reasonCode must be a ReasonCode with type LOGOUT from User.getAssignableReasonCodes.
The logout reason code. Must have type equal to ReasonType.LOGOUT.
A promise that resolves when the agent is successfully logged out of the queue.
AvayaInfinityAgentSdkError If the logout request fails. * *
Subscribes to queue events.
The QueueEventType to subscribe to
Callback invoked each time the event fires
A handler ID to pass to unsubscribe when done
Unsubscribes a previously registered event handler.
The QueueEventType to unsubscribe from
The handler ID returned from subscribe
The unique identifier of the queue.
The display name of the queue as configured in the contact center platform.
The category of the queue.
GENERAL and HYBRID queues support explicit login /
logout; PERSONAL queues do not — the platform manages them
automatically. UNKNOWN indicates the backend did not send the type
field (typically an older backend version); the SDK does not gate
login/logout for UNKNOWN — any server-side restriction surfaces via
the server's rejection response instead.
Whether the agent is currently logged into this queue and eligible to receive interactions from it.
The timestamp when the agent last logged into this queue.
undefined if the agent is not currently logged in.
Whether the platform automatically logs the agent into this queue upon logging into CX.
Represents a queue assigned to the agent for receiving interactions.
Obtained from User.getAssignedQueues or refreshed via User.refreshAssignedQueues. An agent must log into a queue before the platform routes interactions to them from it. Multiple queues can be logged into simultaneously.
Typical usage
LOGOUTwhen the agent is done.Example
See