Illustration of the chat message display sequence between Requester and Agent in chat window at both requester side and agent sideThe order of showing the messages depends on when the messages are sent, and how long it takes to transfer the message from browser to the server and from server to another browser. Because of the network and processing latency, it is possible that messages are displayed at different order at requester side v.s. at agent side. EXAMPLE: Time Requester typing message Requester chat window Agent chat window Agent typing message 9:01:01 Are you working on my case? 9:01:02 Are you work on my case? 9:01:03 What is your name? 9:01:05 What is your name? 9:01:06 Are you working on my case? 9:01:07 What is your name? Yes. Your case num is 123. 9:01:08 My name is Tom. Yes. Your case num is 123. 9:01:09 My name is Tom. 9:01:10 Yes. Your case num is 123. 9:01:11 My name is Tom. 1. The requester window will display as below: Are you working on my case? What is your name? My name is Tom. Yes. Your case num is 123. 2. The agent window will display as below: What is your name? Are you working on my case? Yes. Your case num is 123. My name is Tom. EXPLANATION: The messages are showing in slightly different order if requester and agent are typing very fast. In reality, if the requester and agent are chatting by acknowledging each other, the chance of crossing over each other will be small. In short, the order of messaging displaying at the browser depends on when and the order the client’s browser receives the messages. NOTE: Transcript could be same to agent or requester or neither depending on when the server receives the messages.