Thursday, January 30, 2025
2 changes · saas-18.1
Resolved issues and error corrections
Chat windows now wait for the chat hub to finish loading before applying other updates. This prevents restored chat states from being lost or overwritten, giving users a more consistent live chat and messaging experience.
Original PR description
Changes to chat window done before chat hub is loaded would either be overriden by the initial chat hub state, or overriding the initial state depending on when during the restore process the change would happen. This commit ensures the initial state is always restored before doing other changes.
Live chat operators now keep access to the message composer after a conversation has ended, allowing them to complete follow-up actions such as creating a lead. Visitors still see a clear ended-conversation message and cannot continue the closed chat.
Original PR description
When a livechat has ended, it replaces the composer by "This livechat conversation has ended" for both visitor and operators. This is good for visitor to make it very clear the conversation has ended, and they cannot post message again to the operator unless they initiate another livechat session. Operators however sometimes need to do extra things after the conversation has ended, such as `/lead`. Because of the removal of composer, this was no longer possible. This commit fixes the issue by keep showing the composer for livechat operators even when the conversation has ended. Part of Task-4528331 Before / After <img width="383" alt="Screenshot 2025-01-30 at 11 25 49" src="https://github.com/user-attachments/assets/67ca2f71-180a-4545-9f41-2b3927884a66" /> <img width="384" alt="Screenshot 2025-01-30 at 11 25 37" src="https://github.com/user-attachments/assets/c3e93086-b3fc-4604-9dce-0931178eaeb7" />