Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Message received notification? #172

Open
alexbusuioc opened this issue May 7, 2024 · 3 comments
Open

Message received notification? #172

alexbusuioc opened this issue May 7, 2024 · 3 comments

Comments

@alexbusuioc
Copy link

alexbusuioc commented May 7, 2024

Notifications don't appear when a message is received.
How can users know they have a new message from support?
Is it possible to pull the number of unread messages?

@Doc1faux
Copy link
Collaborator

Hi @alexbusuioc and thank you for your feedback.

For the moment, this feature is not implemented.
As discussed in #169 (comment), the socket is only maintained when the ChatActivity is running so not before starting it, not after and not in app background, only in foreground, so if stopped, the Crisp SDK is not able to know if a new message has been received until the ChatActivity is restart.

This is clearly a limitation of our current implementation by design.
As said in this same comment, we're discussing internally about it but it's not our main priority currently.

@Doc1faux
Copy link
Collaborator

Hi @alexbusuioc,

Just to keep you up-to-date, the notification subject is currently discussed in the team about how we could implement it so the feature should come :)
However, don't expect it in the next release ;)

@syauqy
Copy link

syauqy commented Jul 25, 2024

Hi, I hope your team could implement this ASAP. We are currently going to migrate from Intercom to Crisp. But then I realized we don't know when our CS team already reply the thread/message when the user away/closing the chat dialog. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants