elicit-specific-order-help-intent

name: elicit-specific-order-help-intent description: Prevents the agent from prematurely assuming the specific type of assistance needed for an order, or executing complex transactions, when the user makes a general request for 'help with an order.' metadata: benchmark: tau2_retail_cheatsheets_v2 source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_skill_tool.json

Layer 1: Metadata & Description

• Description: Prevents the agent from prematurely assuming the specific type of assistance needed for an order, or executing complex transactions, when the user makes a general request for 'help with an order.'

Layer 2: Guidelines

General Guidelines

• Always clarify the specific intent when a user requests general 'help with an order.'
• Never assume the nature of 'help' (e.g., modification, cancellation, information) from a general statement.
• Do not execute any transactional actions without explicit user confirmation of the specific order(s) and the exact details of the requested action.
• Prioritize eliciting specific details over making assumptions about user intent or scope.

Specific Guidelines

• Upon receiving a general request for 'help with an order,' respond by asking, 'I can certainly help with that. Could you please tell me what kind of help you need with your order, and which order number you're referring to?'
• If the user provides a general problem (e.g., 'something is wrong'), follow up with questions to narrow down the specific issue (e.g., 'Is it about the item, shipping, or something else?').
• Before any action, explicitly state the understood problem, the proposed solution, and the affected order(s) for user confirmation.
• Avoid making assumptions about the number of orders involved or the specific changes required, even if past interactions suggest a pattern.

Layer 3: Context

• Problem Pattern: Premature execution of complex transactional actions based on a general request for order assistance.
• State Signature: User expresses a general need for assistance related to an order, without specifying the nature of the help or the order identifier, leading the agent to execute unconfirmed, complex transactional actions.
• Bypass Strategy:
  1. Acknowledge the user's general statement.
  2. Explicitly ask for clarification on the type of help needed.
  3. Explicitly ask for the specific order identifier(s).
  4. Elicit full details before proposing or executing any action.