Communication with your app users can be initiated in two ways:
- The user reaches out to you by creating a new chat which you can reply to from the chats page.
- You reach out to the user from your dashboard to reply to a specific bug report or survey response.
Responding to your users can encourage even more useful feedback. You can directly communicate with your users that have reported bugs, crashes, and even responded to surveys.
Each open conversation can only be viewed from its related issue. If a user contacts you using any of the methods mentioned here, the conversation will appear in the chats page of your dashboard.
If a user reaches out to you through composing a new chat message, you can directly reply to them from the chats page. All of this and more is discussed in the page here.
Let's say you receive a bug report from a user and you want to let them know that a fix is on the way or ask for more details. You can do this by reaching out to them directly from the bug report in your dashboard using the Reply to User button (or View Conversation if one already exists) as shown below.
Valuable insights can be garnered from user survey answers, even negative responses, and often you want more information. Being able to chat with survey responders is really useful. Doing so is possible from the survey results page in your dashboard and choosing Reply to User (or View Conversation if one already exists) next to each answer.
A handy way of knowing if there are any unread messages would be to check the icon next to the bug, crash, chat, or survey in the list. There are 4 different representations for each conversation.
- No icon: there is no chat ongoing with the customer
- Grey with arrow: you have replied to this user (you sent the last message in the chat)
- Blue icon with red dot: you have a new unread message from the user
- Blue icon only: you read the message but didn't reply (the user sent the last message)