In Fastpath, if you reject a message and then set your status to away, the client is routed forever instead of being prompted for email
Description
If you have a set of agents, and all are away but one who is online, that one agent will get a chat. If the agent rejects the message, and changes his status to away, he no longer receives the chat request (good), but the initiating customer is not stuck in the "waiting for agent" queue. Instead, the customer should be redirect to the email page.
If you have a set of agents, and all are away but one who is online, that one agent will get a chat. If the agent rejects the message, and changes his status to away, he no longer receives the chat request (good), but the initiating customer is not stuck in the "waiting for agent" queue. Instead, the customer should be redirect to the email page.