Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Chat contact missed results in error status rather than missed status
See original GitHub issueCurrently contact.onMissed() is not being fired when a contact chat has been missed.
From my understanding of what I have read contact.onMissed() seems to only handle call cases, but it should really handle both voice/ chat. This is because weather a contact is a voice/ chat contact they are a contact that has been missed.
Documentation snippet:
Subscribe a method to be invoked whenever the contact is missed. This is an event which is fired when a contact is put in state “missed” by the backend, which happens when the agent does not answer for a certain amount of time, when the agent rejects the call, or when the other participant hangs up before the agent can accept.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This is indeed the behavior, and although I coded my application appropriately, it does not seem right that it should go into error state and not missed state. Can this be fixed/updated?
@sseidel16 fair enough, In our Call contact system we usually show all information about the contact to an agent before they have accept a call so they can respond must faster to a customers query. Was pretty much trying to do the same thing here with chat and showing the current transcript and subsequent messages coming through before accepted.
Since the original issue around
onMissed()not working has been resolved as part of version 1.4.8 I will be closing this ticket.