Return Merchandise Authorization case user journey

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Return Merchandise Authorization case user journey

    The Return Merchandise Authorization (RMA) case user journey outlines the structured process that both customers and support agents follow to manage sales return cases effectively. This journey begins when a customer reports an issue with a product and proceeds through four clear stages: initiating the case, reviewing details and entitlements, resolving the issue, and closing the case. This method ensures smooth handling of requests with transparent communication and a focus on resolution.

    Show full answer Show less

    Key Features

    • Customer Initiation: The customer identifies the product issue, contacts support, and provides necessary details, triggering the creation of a support request in the system.
    • Agent Case Creation: Agents access the RMA Case list, start a new case in draft state, and enter customer/account information along with the request source.
    • Case Line Management: Defective products are added as RMA Case Lines from the customer’s install base, with each line updated with reason codes and expected resolutions.
    • Case Processing: Agents assign the case for processing, moving it to a Work In Progress state, and review warranty and entitlement statuses for each case line, adding entitlements as needed.
    • Decision and Resolution: Agents decide to accept or reject the RMA request. If accepted, they propose solutions and update repair types; if rejected, they notify the customer and close the case.
    • Customer Feedback and Task Management: Customers review proposed solutions and provide feedback. If further work is needed, agents create specialist tasks, monitor progress, and update case statuses accordingly.
    • Case Closure: Once resolved, agents communicate the final resolution to the customer and formally close and archive the case and all related records.

    Key Outcomes

    • Ensures every RMA request is managed through a consistent and transparent workflow.
    • Facilitates clear communication between customers and agents throughout the return process.
    • Enables effective tracking of product issues, entitlements, and repair actions.
    • Supports timely resolution and proper documentation for audit and service improvement purposes.

    The Return Merchandise Authorization (RMA) user journey describes the steps a customer and support agent take when handling a sales return cases.

    The RMA user journey starts when a customer reports an issue. The agent then manages the request through a clear four-stage process:
    1. Initiate the case
    2. Review the details and entitlements
    3. Resolve the issue
    4. Close the case
    This approach confirms that every request is handled smoothly, with clear communication and a focus on effective resolution.
    Table 1. Steps involved in the RMA case user journey
    Steps User Action System response
    1 Customer Identifies product issue and contacts customer support. Support request is logged. Customer is guided to provide product and issue details.
    2 Agent Receives request and navigates to the RMA Case list. Agent selects New to initiate RMA Case creation.
    3 Agent Fills in customer or account details and request source in the RMA Case form. System renders the form and creates the RMA Case in Draft state.
    4 Agent Adds defective products as RMA Case Lines by selecting from customer’s install base items. System creates RMA Case Lines for each selected item.
    5 Agent Updates each case line with request reason code (such as defective, damaged) and customer expected resolution. System saves details. Agent submits the case for processing.
    6 Agent Assigns the case to self (or another agent) to begin processing. RMA Case and lines move to Work In Progress state.
    7 Agent Reviews warranty and entitlements for each case line. System displays entitlement status and enables agent to add entitlements as needed.
    8 Agent Decision: Accept or Reject RMA Case? If accepted, proceed to next step. If rejected, agent notifies customer and closes the case.
    9 Agent (If accepted) Proposed solution and updates repair type. System records proposed resolution.
    10 Customer Reviews proposed solution and provided feedback (accepts or requests clarification). System logs customer response.
    11 Agent If additional work is required, create task for specialist. System assigns task and tracks progress for each case line.
    12 Agent Updates case line and overall case status as tasks are completed and customer feedback is received. System transitions case through Resolved and Closed states as appropriate.
    13 Agent Communicates final resolution to customer and formally closes the case. System archives the case and all related records.
    Figure 1. RMA case user journey
    This infographic displays the RMA case user journey for reporting a product issue.

    What to explore next