[Extension] How to Discover Where Your Chatbot Is Failing on Blip with the Waizer Extension

1. Introduction

2. How to Identify Chatbot Failures

3. Usage Example

4. Best Practices

5. Support

Brief Description: Discover where the Blip chatbot fails with Waizer: each conversation is evaluated by AI, critical errors are grouped by recurrence, and insights are prioritized by impact.

Introduction

Noticing that the bot is having a problem is usually the easy part. The hard part is knowing exactly where it fails and what to do about it. Without this clarity, the support team is always putting out fires: one contact complains, someone investigates that case, but the pattern behind the error keeps repeating silently for other users.

This is where Waizer changes the game. Each bot conversation goes through an AI evaluation that identifies the failure, groups critical errors by recurrence, and orders the insights by the impact they have on the operation. Instead of a generic list of errors, you receive a description of each problem, a recommended solution, and the link to the real conversations that support the adjustment. The working logic changes: instead of reacting to isolated complaints, the team first tackles the causes that weigh most on the outcome.

Before You Start

Before analyzing chatbot failures, check if:

• The Waizer extension is installed and active on the bot. Activate Waizer in the Blip Store.

• The bot already has conversations recorded in the period you want to analyze.

• You have access to the Waizer Dashboard.

• The analyzed period has a sufficient volume of conversations to reveal patterns.

How to Identify Chatbot Failures

1. Open Waizer on the desired bot and click Dashboard.

2. Locate the Problems and Failures card. It lists the errors found in the period, ordered by severity (High, Medium, or Low) and, within each severity, by the number of occurrences.

3. Click on a problem to open the details. The screen shows the Problem Description, the Severity, and the error subcategories, each with the number of occurrences and a Suggested Solution when available.

4. Analyze the subcategories to understand the points that most hinder the service, such as unclear responses, missing options, integration failures, or incorrect paths in the flow.

5. Click View Impacted Contacts to open the list of unique contacts affected by that problem. From there, you can access the real conversations and confirm what happened.

6. Also check the Insights and Suggestions card. Each insight carries an impact badge (High, Medium, or Low impact) and, when opened, shows the Identified Problem, the Recommended Solution, the Expected Results, and the metrics supporting the prioritization, such as recurrence, average frustration, and failure rate.

From there, the team prioritizes the adjustments that appear most frequently or generate the greatest impact on the journey.

Usage Example

Suppose many contacts abandon the conversation right after a specific bot question. In Waizer, you identify the pattern, open the impacted conversations, and discover whether the cause is an unclear response, the lack of an appropriate option, an integration failure, or an incorrect path in the flow.

With this insight, you fix the flow and monitor in the following days whether that problem stops appearing among the recurring failures.

Best Practices

• Start with the errors of highest severity and highest recurrence.

• Prioritize failures that directly impact conversation resolution.

• Compare data before and after each flow adjustment.

• Use insights to review the bot's questions, answers, and paths.

• Check if the corrected points have been removed from the Problems and Failures list.

Support

If you have any questions or problems with the extension, contact us by email at support@wiv.com.br.

Need more help? Explore our content at the Blip Academy or the Blip Community, watch tutorials on our YouTube channel, or get your questions answered in our support channel 😃