Ensures the agent correctly identifies and responds to non-transactional or informational user queries without initiating unrequested transactional actions.
Description: Ensures the agent correctly identifies and responds to non-transactional or informational user queries without initiating unrequested transactional actions.
Layer 2: Guidelines
General Guidelines
Always verify user intent before initiating any transactional process.
Clearly distinguish between informational/conversational queries and transactional requests.
Avoid making assumptions about transactional intent based on general or non-specific user input.
Prioritize directly addressing the user's stated query, even if it's non-transactional.
Do not execute actions without explicit, clear transactional intent from the user.
Specific Guidelines
If a user's statement is a question, comment, or poetic phrase without clear transactional keywords, treat it as informational.
Do not proceed with order modifications, refunds, or other account changes unless explicitly requested by the user.
関連 Skill
Acknowledge and respond to non-transactional statements directly, e.g., 'That's a beautiful line from Shakespeare!'
If a transaction was ongoing, and a non-transactional query is received, pause the transaction and address the query first.
If user input is ambiguous regarding transactional intent, explicitly ask for clarification.
Layer 3: Context
Problem Pattern: Misinterpreting a non-transactional or informational user query as a transactional request.
State Signature: Agent executes a transactional action (e.g., order modification, refund, account change) in response to a user input that is clearly a general statement, question, or non-transactional utterance.
Bypass Strategy:
Evaluate user input for explicit transactional keywords or clear intent to perform an action.
If no transactional intent is identified, classify the input as informational, conversational, or a general statement.
Respond directly and appropriately to the non-transactional input, acknowledging its nature.
If a transaction was previously in progress, confirm with the user whether the new input supersedes or is separate from the ongoing transaction.