As well as resolving conversations when they’re started, Resolution Bot can also proactively suggest answers for your customers in two ways:

  • Predictive answers When a customer opens the Messenger to start a new conversation, Resolution Bot will detect relevant context, like the page in your app they’re on, and suggest the answers most often useful in that context.

  • Answer suggestions — As your customers type in the Messenger they’ll see suggested answers to choose from based on their message, so they can find their own solution faster, and save your support team more time.

Enable automatic content suggestions in the Messenger

To start automatically suggesting answers for users and visitors, go to Operator > Settings and open the ‘Suggest relevant answers tab’:

Then, enable Resolution Bot to suggest answers Before customers start typing (Predictive answers), While customers are typing (Answer suggestions), or Both:

Note: To enable either of these settings for visitors or users separately, just switch between these tabs:

Tip: To only suggest content to a certain subset of visitors or users, choose ‘Visitors/users who match certain data’, then ‘+ add a rule’. For example, you might want to suggest content for users on your free plan, in which case you’d add a filter like this:

If you enable predictive answers, when a user or visitor who matches your filters starts a new conversation in the Messenger, Resolution Bot will show potentially helpful answers before they start typing based on the page they’re on, or other relevant attributes:

Important: When you enable predictive answers, all of your existing answers will be eligible to be shown to customers. If you’d like to exclude any from sending, you can set this on the individual answer.

If you enable suggested answers, when a user or visitor who matches your filters starts a new conversation in the Messenger, Resolution Bot will show matching answers as they type based on the content of their message:

Prevent certain answers from being shown before a customer starts typing

If you’d like to prevent certain answers from being shown before a customer starts typing, just uncheck this box on step 4 when creating or editing an answer:

Note: The answer will still be sent in matching conversations, and can be suggested after customers start typing, if you have suggested answers enabled. 👌

How does it work?

Before customers start typing, if Resolution Bot has learned that certain answers are commonly sent on the current URL to customers with similar attributes it will show relevant answer suggestions above the composer for them to choose from.

While customers are typing If Resolution Bot detects at least two matching keywords in their message it will show relevant answer suggestions above the composer for them to choose from.

If the customer chooses an answer, they’ll enter the answer flow until the end where they can choose if it was helpful, or if they’d like to wait for the team:

Suggested answers & Custom Bots from new conversations

If you have a Custom Bot that starts from new conversations, and a customer matches its filters, predictive answers will not be shown. The Custom Bot’s first message, and reply buttons will display for a user to choose from.

If the customer doesn’t choose a Custom Bot path, and begins typing a question, suggested answers will appear based on the content of their message.

When are suggestions shown?

Predictive answers will only be shown after Resolution Bot has learned enough about your customers’ questions, but you can enable it at any time. If you enable it before it has enough information to make predictions, you’ll see the following warning:

Automatic suggestions are not supported in apps using our Mobile SDKs, so they'll only be presented to customers in their web browser.

Suggestions are only presented at the beginning of a new conversation in the Messenger.

A customer may also see suggestions for additional messages they send before engaging with any answers, or getting a response from a teammate.

What’s next?

Did this answer your question?