Welcome to Instabug's Documentation! Here you'll find
a comprehensive technical guide to help you start
working with the Instabug SDK as quickly as possible.

Get Started

Saved Replies

This page covers the saved replies feature which allows you to save replies and use them whenever needed instead of typing the same content several times.

At Instabug we do believe in the importance of the user engagement. It helps to build a network of supporters and loyal customers who act as your main source of validation and information. Hence, we built some products that serve this purpose as the In-App Surveys and the In-App Chats.

The In-App Chat opens and maintains a 2-way communication channel between your customers and you. This connection can be initiated by your customers from within the application or by your team from the dashboard. In both cases, your team should always aim to be super responsive to motivate your customers to communicate with you more and more. Especially in the first case, where the user was the one who took the initiative and started the process.

After a while, you start to discover that some of the replies you send are repetitive. You type almost the same message several times. To make your process faster, we build the Saved Replies feature. Instead, of typing the same content several times, you can simply save it and use it whenever needed.

Create a Saved Reply

To create a new saved reply or edit an already existing one, click on your Name appearing on the bottom left corner of the dashboard. Then, select Company. Last, open the Saved Replies tab from the left column.

Types of Saved Replies

Normal Replies

This type of saved replies is sent as a normal text. To create one you should select the radio button next to the None option. It can be used in many scenarios. As an example, an answer to a frequently asked question by the users.

Call To Action Replies

This type of replies is suitable when you want to the user receiving the message to do a certain action. For example, if you are asking the user to check a blog post, instead of just sending them a link, you can add an action which will appear as a button when received, that navigates to the blog post you are referring to. Another example, if you want the user to update the app to the latest version or rate your app on the store, if you just send them the request, there is a high possibility that they will ignore it. If you make it easier for them by adding a button that directly opens the app's page on the store within the message, you are increasing the possibility that they follow the instruction sent.


In some cases, you don't only use a specific reply more than once, you use it in the same exact situation and under some defined conditions. Here, it makes sense to automate the process, instead of sending the reply yourself, you can use the Rules to automate the process for you.