# Instruction
- You are an expert in cleaning process data descriptions. Given a task, you are provided with a set of annotation description
data for a certain visual LLM related to human user operation videos. Plus, You are provided with full trace of playwright action,
whic includes action and url before and after the action.
- You need to analyze all the descriptive data and ultimately summarize a complete and reasonable user operation description that can accomplish the given task.
- For each strategy, give a clear list of the low level action sequence.

# Task
Which number to call for the customer service?

# Annotation description
### Step-by-Step Actions in the Video Segment

#### 1. **Action:** I click on the "Add to Cart" button for the product "Elmwood Inn Fine Teas, Orange Vanilla Caffeine-Free Fruit Infusion, 16-Ounce Pouch."
   - **Page Changes:** The "Add to Cart" button appears to be highlighted or interacted with, but there is no immediate visible change to the page layout or content indicating a successful addition (e.g., cart icon update or confirmation message).
   - **Possible Purpose:** The likely intent is to add the selected tea product to the shopping cart for potential purchase.

#### 2. **Action:** I navigate to the "Contact Us" section of the website.
   - **Page Changes:** The webpage transitions from the product showcase page to a new page titled "Contact Us." This new page includes fields for "Name," "Email," "Phone Number," and "What's on your mind?" along with a "Subscribe" button.
   - **Possible Purpose:** The purpose of this action is to access the contact form, possibly to send a query or feedback to the website's support team.

#### 3. **Action:** I scroll down slightly on the "Contact Us" page.
   - **Page Changes:** The view shifts downward, revealing more of the "Contact Us" form fields and any additional information or text that may be present below the initial view.
   - **Possible Purpose:** The intent is to review the entire contact form, ensuring all necessary fields and options are visible before proceeding to fill out the form.

### Summary
- **Initial Action:** I added a specific tea product to the cart by clicking the "Add to Cart" button.
- **Transition:** I then navigated to the "Contact Us" page, which changed the displayed content to a contact form.
- **Final Action:** I scrolled down the "Contact Us" page to view more of the form fields.

Each step is performed with the clear intent of either preparing for a purchase or initiating communication with the website's support team, based solely on the observed interactions.

# Playwright action
[
  {
    "action_uid": "link_Contact Us",
    "idx": 0,
    "action_repr": "frame.clickget_by_role(\"link\", name=\"Contact Us\")",
    "before": {
      "url": "http://ec2-3-131-244-37.us-east-2.compute.amazonaws.com:7770/"
    },
    "after": {
      "url": "http://ec2-3-131-244-37.us-east-2.compute.amazonaws.com:7770/"
    }
  }
]

# Output format
- 先总结整个任务的Objective，然后按照Strategy-SubStrategy-action三级层次来给出整个过程，
- 接着给出整个操作流程后的观察和有趣的发现，最后严格按照json格式输出三级层次的过程描述。
- 最后的输出json应该是包在```{json}```之间，最底层动作需要包含描述、对应的playwright动作指令顺序编号，以及具体指令内容。

# Example
### Complete User Operation Description to Display Labeled Issues in kkroening/ffmpeg-python

**Objective:** Filter and display all issues labeled as "question" in the kkroening/ffmpeg-python repository.

---

#### **Strategy 1: Navigate to the Repository**
**Low-Level Action Sequence:**
1. **Search for the user "kkroening"**
   - Click the global search bar (placeholder: "Search GitLab").
   - Type "kkroening" and press `Enter`.
2. **Select the user from results**
   - Click the "Users" tab in search results.
   - Click on "Karl Kroening @kkroening" in the user list.
3. **Access the repository**
   - Navigate to the "Personal projects" section.
   - Click on the "ffmpeg-python" project.

---

#### **Strategy 2: Filter Issues by Label**
**Low-Level Action Sequence:**
1. **Open the Issues tab**
   - Scroll to the left sidebar menu.
   - Click the "Issues" tab (displaying the count, e.g., "Issues 402").
2. **Apply label filtering**
   - Click the search/filter bar in the issues list.
   - Select the "Label" dropdown from the filter options.
   - Type or select "question" from the label dropdown.
   - Click the search/apply button to confirm the filter.

---

#### **Final Oberservation**
The issues list will refresh to show only issues with the "question" label. The URL will reflect the filter:
`.../ffmpeg-python/-/issues/?label_name[]=question`.

---

### Key Observations from Playwright Trace
- The final URL after filtering:
  `http://ec2-3-135-39-80.../ffmpeg-python/-/issues/?label_name%5B%5D=question`
  confirms the "question" label filter is applied.
- Critical interactions include selecting the "Label" dropdown and explicitly choosing "question" to refine results.

### Final output
```json
[{
  "strategy" : "Navigate to the Repository",
  "substrategies": [
    {
      "substrategy": "Search for the user \"kkroening\"",
      "actions" : [
        {
          "description": "Click the global search bar (placeholder: \"Search GitLab\"). ",
          "playwright_idx" : 18,
          "playwright_instruction" : "frame.pressget_by_placeholder(\"Search GitLab\")Enter"
        }
      ]
    },
    {
      "substrategy": "Select the user from results",
      "actions" : [
      ]
    }
  ]
},
{
  "strategy" : "Filter Issues by Label",
  "substrategies" : [
  ]
}]
```