Add Agent to Call Queue

When synchronous is requested with "yes" the response will be a 200 on success and will contain a valid JSON representiation of the new resource. If no or left off request a 202 "Accepted" will be given in a success case and this can be considered a success. Synchronous responses will be a little slower as the API will process the geo replication request and wait till the local copy has been written and can be read back berfore sending a response.

This is the main identifier for a "agent" in a queue. There are two format supported here, either a user based option which will look like user@domain or a device based method like sip:device@domain.

This is the callqueue id for which the agent is in. The agent may be in multiple callqueus, but this value is a single entry.

This is the main organization name. This is used to link resource to its group/tenant/organization/enterprise. ~ and * can be used alone in special cases to mean My Domain (~) and All Domains (*).

This is the main toggle for the agents status in the queue. "automatic" is logged in, which manual is logged out with the option for one call. From a angent perspective and the actions of logging in and out the recomention would be to use the specific "agent actions" api instead of the basic agent update request.

This is the number of seconds that the system will hold the agent offline before logging them back in automatically. This time allows the agent to comolete needed notes and conclusions to previous calls and prepare for next call.

For use in callqueues that have a linear order, this value would be to the order of the agent in that list, the lower the number the higher agent in the order.

This setting is a priority value for this agent's entry with respect to the other callqueues they are in. Lower number is higher priority. This means that when the agent comes back available after a call the priority would be used to determine which queue its attempted first.

This is the maximum number of calls an agent will be given at at time. Default and ideal is 1, but if needed it can be higher

This read only status will show the agents registration infor and if the system believes the device is registered.

This is the status for the agent generated by the system using all available informaion.

This is the total number of calls on the agent's account across all their queues

This timestamp is the datetime of the last change to the agent's configuration and status

This is the maximum number of SMS queue sessions the agent will be requested to handle before queing up future requests.

This timestamp is the datetime of the last dispatch to the agent.

This is a read only field that will tell you the type of agent config that is setup, this might include device or user based agents or "offnet"

This value read only from the user that is linked to this agent. Its the user's login if needed.

This value read only from the user that is linked to this agent. Its the user's full name.

This value read only from the user that is linked to this agent. Its the user's first name.

This value read only from the user that is linked to this agent. Its the user's last name.

This value read only from the user that is linked to this agent. Its the user's depeartment.

This value read only from the user that is linked to this agent. Its the user's site

This value read only from the user that is linked to this agent. Its the user's scope.

This value read only from the user that is linked to this agent. Its the user's status message.

This is the main identifier for a "agent" in a queue. There are two format supported here, either a user based option which will look like user@domain or a device based method like sip:device@domain.

This is the callqueue id for which the agent is in. The agent may be in multiple callqueus, but this value is a single entry.

This is the main organization name. This is used to link resource to its group/tenant/organization/enterprise. ~ and * can be used alone in special cases to mean My Domain (~) and All Domains (*).

This is the main toggle for the agents status in the queue. "automatic" is logged in, which manual is logged out with the option for one call. From a angent perspective and the actions of logging in and out the recomention would be to use the specific "agent actions" api instead of the basic agent update request.

This is the number of seconds that the system will hold the agent offline before logging them back in automatically. This time allows the agent to comolete needed notes and conclusions to previous calls and prepare for next call.

For use in callqueues that have a linear order, this value would be to the order of the agent in that list, the lower the number the higher agent in the order.

This setting is a priority value for this agent's entry with respect to the other callqueues they are in. Lower number is higher priority. This means that when the agent comes back available after a call the priority would be used to determine which queue its attempted first.

This is the maximum number of calls an agent will be given at at time. Default and ideal is 1, but if needed it can be higher

This read only status will show the agents registration infor and if the system believes the device is registered.

This is the status for the agent generated by the system using all available informaion.

This is the total number of calls on the agent's account across all their queues

This timestamp is the datetime of the last change to the agent's configuration and status

This is the maximum number of SMS queue sessions the agent will be requested to handle before queing up future requests.

This timestamp is the datetime of the last dispatch to the agent.

This is a read only field that will tell you the type of agent config that is setup, this might include device or user based agents or "offnet"

This value read only from the user that is linked to this agent. Its the user's login if needed.

This value read only from the user that is linked to this agent. Its the user's full name.

This value read only from the user that is linked to this agent. Its the user's first name.

This value read only from the user that is linked to this agent. Its the user's last name.

This value read only from the user that is linked to this agent. Its the user's depeartment.

This value read only from the user that is linked to this agent. Its the user's site

This value read only from the user that is linked to this agent. Its the user's scope.

This value read only from the user that is linked to this agent. Its the user's status message.