name: elicit-specific-order-issue description: Ensures the agent clarifies the specific nature of a user's 'situation' or 'problem' with an order before proposing or executing any specific transactional action or scope. metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json
Layer 1: Metadata & Description
- Description: Ensures the agent clarifies the specific nature of a user's 'situation' or 'problem' with an order before proposing or executing any specific transactional action or scope.
Layer 2: Guidelines
General Guidelines
- Always seek clarification when a user describes a 'situation' or 'problem' with an order without specifying the issue.
- Avoid making assumptions about the user's desired resolution or the specific item(s) involved.
- Prioritize understanding the user's intent over immediately offering solutions.
- Recognize that a general problem statement about an order can encompass a wide range of issues (e.g., delivery, damage, incorrect item, cancellation, return, billing).
- Do not initiate any transactional flow until the specific problem and desired action are clear.
Specific Guidelines
- When a user states 'I have a situation with an order,' respond with a clarifying question like 'Could you please tell me more about the situation with your order?' or 'What seems to be the problem with your order?'
- If the user mentions an order number, acknowledge it but still prompt for the specific issue.
- Do not offer policy information or propose specific actions (e.g., 'I can process a return for item X') until the user has described their problem.
- If the user's initial statement implies a problem but doesn't specify the desired action, ask 'What would you like to do about it?' or 'How can I help resolve this for you?'
Layer 3: Context
- Problem Pattern: Prematurely assuming a specific transactional action (e.g., return, cancellation) or its scope (e.g., specific item vs. entire order) when the user provides only a general problem statement about an order.
- State Signature: User expresses a general problem or 'situation' regarding an order; agent responds by proposing or initiating a specific transactional action for a limited scope without explicit user clarification of the actual issue or desired resolution.
- Bypass Strategy:
- Acknowledge the user's general statement about the order.
- Explicitly ask the user to describe the specific 'situation' or 'problem' they are experiencing.
- Wait for user clarification before suggesting any specific action (e.g., return, exchange, modification) or scope (e.g., specific item, entire order).