transactional-action-and-item-disambiguation

name: transactional-action-and-item-disambiguation description: Clarifies the precise transactional action type and identifies all specific items involved when the user's request is ambiguous or implies multiple entities. metadata: benchmark: tau2_retail_cheatsheets_compact source: /data/Research_dir/Memory/Procedual_Memory/Outputs/tau2_pairable_compact.json

Layer 1: Metadata & Description

• Description: Clarifies the precise transactional action type and identifies all specific items involved when the user's request is ambiguous or implies multiple entities.

Layer 2: Guidelines

General Guidelines

• Always clarify the precise transactional action (e.g., exchange, return, cancel) before proceeding with any specific item selection or detail presentation.
• If the system cannot perform the exact requested action, clearly state the limitation and offer viable alternatives for user choice.
• Require explicit user confirmation for both the action type and the specific items involved in a transaction before presenting or executing details.

Specific Guidelines

• When a user requests an "exchange," ask if they prefer a direct exchange or a return for refund followed by a new purchase.
• If a direct exchange is not possible, explain the system's limitation and offer the return process as the primary alternative, asking for user consent.

Layer 3: Context

• Problem Pattern: Misinterpreting the user's requested transactional action type (e.g., exchange vs. return) or prematurely selecting specific items and details for processing without explicit user confirmation.
• State Signature: User expresses intent for a transactional action (e.g., exchange, return) for an unspecified number or type of items, and the agent proceeds to propose or execute a specific, potentially different, transactional action for an unconfirmed single item with assumed details.
• Bypass Strategy:
  1. If the user's request implies multiple items, present a list of relevant recent purchases and ask the user to specify which items are involved.
  2. If the requested action type is not directly supported, clearly state the limitation and offer the closest available alternative(s) for user selection.
  3. Obtain explicit confirmation for each item and its corresponding action before proceeding with any transactional details or execution.