• Remove messages like "Thank you for your response"
• Disable send button while the agent is working on the request
• The entire conversation should look like the initial conversation without any additional messages
• The loader and the input box should be tied to individual chat
• Fix search bar css issue

• Move logic to parent component and pass the necessary state to the child components
• Write test cases for React components
• Polish UI in mobile and in desktop layouts

• Initially show new chat
• After the 1st request, generate a new name and update it
• Have edit button next to the chat name

• Ping server for every second to get the status of "inprogress" conversations

Show smart reply option in the UI and it should have the following suggestions:

• Move logic to parent component and pass the necessary state to the child components
• Write tests for the refactored components and new components
• Add unit_test job to the CI pipeline
• Store smart suggestions in the DB against the chat
• Generate a few quick suggestions for the agent response and show in the UI
• Do not generate suggestions for open ended agent responses
• Style the quick suggestion component

• Update DB
• FIx Google Auth
• Fix branding
• Create necessary pages
• Create necessary routes
• Integrate with Python backend
• Add necessary websockets
• Add necessary webhooks
• Fix React build issues
• Fix Stripe
• Allow admins to access all chats
• Add privacy policy and ToC to login screen
• Fix social share
• Create Landing page

• Show team name in the UI along with the task information

• The azure API returns 500 when the user request is categorised as harmful/sexual etc
• At persent we are showing an alert box in the UI saying "something went wrong. please try again later"
• But we could display some custom messages in the UI for better usability

• Should have the provision to show only the conversation between the user and the agent
• Should have the provision to show all the conversation between the user and the agents

• Show loader only for current conversation
• The user should be able to interact with other conversations without restriction

• update Conversation table to store each conversation in individual records
• Refactor the application code to make it work with the modified database schema
• Create teams when required
• Save the team status and questions/answers in the database when ready
• But show questions one by one to the user in the UI (Filter it at the react code)
• Polish UI and text mesage

• Add new uuid column and set values for existing chat records
• Display uuid instead of id in the URL
• Use uuid in google ads auth redirection URL
• Use uuid in daily analysis email

• Remove dummy from all the functions

• Add userID as foreign key in conversation table
• Update chat creation route input parameters
• Update retrieve chat conversation route
• Show error message at the frontend incase of invalid access
• Drop the existing DB

• Remove multiple conversation code from FE and BE
• Fix UI for mobile and desktop layouts