1. Agent who is a mapped user in Unified CCX, logs in to the Live
Application Servlet (LAS), which makes agent’s entry in the Session
manager and informs Agent Assignment Service (AAS) about agent login
2. The customer initiates a chat through an entry point on the website. This
entry point is mapped to a Unified CCX queue.
3. When customer initiates a chat, a request is sent to the LAS, which then
checks for agent availability (from AAS) and loads the Login template at
customer-end
4. The customer submits the completed login form, which then creates a
session in LAS (also written into database)
5. AAS receives this session information, and assigns an available agent
and informs LAS about the agent assignment. LAS sends the response
back to the customer with the session info and connection info to
connect with EVS (supplied by the Cisco Interaction Manager platform).
Customer gets a nailed connection to EVS and registers himself to
receive the messages
6. The Service template is loaded at the customer end
7. LAS fetches latest information about the session and publishes message
to EVS and sends the selects agent ID to EVS. A nailed connection is
then established with the respective agent browser and the agent
registers himself to receive the messages
8. All chat messages are stored in memory periodically; the rest of the
activity information is written into DB asynchronously
9. During the chat, the agent and customer browsers intimate LAS of their
respective connection status
When the agent ends a call:
— Agent browser sends http request to LAS, which sends a
message to DB
— All session messages are written into DB.
— LAS informs AAS (as an RMI call) so that the agent load is
decremented
LAS renders exit page at the customer end, through the Template Cache
10. Also all events are logged for each agent action during the lifecycle of
the activity, and this is useful for reporting on agent/user or queue/CSQ
or user group/team.