Live Chat portion of web app

I am currently developing an event-based web app which is live to the public for a set period of time and provides information to users. While an 'event' is live, there are also scheduled chat dates and times when live chat functionality will be available. The administration area and front end of this app will be developed by myself using sass, bootstrap and php and hosted using AWS. The live chat design is included in this, so I am just looking for a programmer to developer the functionality. There are many starting points out there for chat apps, and frameworks and technologies to make things easier ([login to view URL] / node.js etc) but I am leaving this open for people to decide what they would like to use and what would make things the easiest. I can then go through this with you. One thing worth mentioning is that AWS has a range of database options, so I am open on this front too. Full project prototypes are available via an invision project, but here is a quick overview of functionality requirements. USER VIEW: During chat times (which are scheduled in the admin), a user is able to chat with an agent. When they finish chatting they are asked to rate the chat as helpful or not helpful. AGENT VIEW: Via the administration panel (all designed and templated by myself), an agent is presented with 3 tabs: 1) Users waiting to chat: A queue of users in line waiting to chat. 2) Users in chat: Users currently chatting with the agent in question that is logged in. 3) Users chatting with others: Agents are able to monitor chats with other agents, but not to participate. Other required functionality: - Agents are able to transfer chats between each other. - Agents can 'star' a chat and add a note for later reference. - Agents can send links to information on the event frontend, including specific articles and media. STATISTICS: The following statistics will need to be displayed on the stats page (libraries such as [login to view URL] can be used when graphical element required - open to feedback). - % of chats users found helpful and unhelpful - Breakdown of number of chats by advisor - Total Chat candidates - Total Messages sent CHAT LOGS: The chat logs page lists all chats for a period which can be filtered, and exported to a .csv file. BLOCKED USERS: Users can be blocked, with the agent required to add a reason. A list of blocked users is to be shown on the blocked users page in the admin. USERS: Users are only required to add their name when chatting, and no email or sign up is needed. Chat agents are administrators who have 'chat agent' privileges. Therefore the user control element of the chat functionality will need to communicate with that of the web app itself. CANNED MESSAGES: Chat agents can send pre-entered messages in order to save time This is a good overview of the required features. Again, full project prototypes are available. I am looking for someone with similar experience. Thank you