How the System Responds to Errors

This topic explains how the system handles scenarios where it cannot generate a response due to incomplete or unclear inputs. It provides users with insights into fallback mechanisms, error messaging, and clarification requests.

Fallback Prompts

When the system encounters an error or lacks sufficient information to generate a response, it triggers fallback prompts to guide the user.

Example
Input: What is the performance of my campaign?
Fallback Prompt: Could you specify what aspect of performance you are looking for? For example, audience engagement, revenue, or response rates?
Why it Happens?
The query is too broad, and the system needs more details to provide an accurate response.

Clarification Requests

The system may ask for additional input to refine the query.

Example
Input: Show me campaigns for this week.
Clarification Request: Are you asking for active campaigns, completed campaigns, or campaigns by specific metrics?
Why it Happens?
The query lacks specificity, leading to potential ambiguity in the system’s response.

Default Error Messages

When the system cannot find relevant data, it provides polite error messages:

Example
Input: Tell me the sentiment of campaign emails.
Error Message: Sorry, I cannot analyze sentiment as it is outside the scope of this system. Please ask about supported analytics or documentation.
Why it Happens?
The query is beyond the system’s capabilities or unrelated to its design.

Handling Context-related Errors

If the system identifies cross-context issues (for example, switching between reports and analytics without resetting), it will attempt to guide the user back on track:

Example
Input: What is the click-through rate of Campaign X? Also, explain how Unica handles email delivery.
Response: Your first question pertains to analytics, and the second to documentation. Please clarify if you want the system to prioritize analytics or documentation.