"Ticket.conversation.property" is not triggering in Ticket1, when the Agent is active on Ticket2 | Community
Skip to main content

"Ticket.conversation.property" is not triggering in Ticket1, when the Agent is active on Ticket2

  • October 18, 2023
  • 1 reply
  • 0 views
Abdul15

Hello..

We are facing some minor issue in our app functionality..
We are using "TICKET.CONVERSTION.CHANGED" property in our app, to capture the conversation changes and to pick the latest user message...

If the Agent is working on more than 1 ticket, and the Agent is currently active on Ticket2.. So, If any new message came in Ticket1, at that time "TICKET.CONVERSTION.CHANGED" property is not triggering..
And When we make any scroll movements in the chat area of Ticket1, it triggers and finding the latest message..

Why the "TICKET.CONVERSTION.CHANGED" property is not triggering in Ticket1, when the Agent is currently active on Ticket2?
Is there any other property, to capture these changes in Ticket1, when the Agent is not active on that?

Thanks..

    1 reply

    Tipene
    • Tipene
    • October 20, 2023
    Hey Abdul Hameed P,
     
    Just a heads up that I've opened a private ticket so we can look in to this in more detail!
     
    Thanks,
     
    Tipene
    Terms & ConditionsCookie settingsAccessibility statement