Update startups workflow page

Why is this change being made?

Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

CHANGEME

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update startups workflow page

---

content/handbook/marketing/developer-relations/community-programs/community-programs-workflows/startups-program-workflows.md

@@ -49,13 +49,15 @@ When the promotion period ends, startups will have the option of becoming regula
 
 Here are some common workflows associated with managing the program, including qualifying a startup:
 
-### Review application within Zendesk "Startups" view
+### Review application within 
+
+- [Startups Issue Board](https://gitlab.com/gitlab-com/marketing/developer-relations/startups-program/startups-program-support/-/boards)
 
 Scenario: User did not submit complete application
 
-In **Zendesk**:
+In **GitLab Service Desk**:
 
-1. Apply the "Funding Info" macro.
+1. Navigate to the [Support-Macros](https://gitlab.com/gitlab-com/marketing/developer-relations/community-programs/operations/-/tree/main/support-macros?ref_type=heads0) Use the the "Funding Info" macro.
 
 Then, in **Salesforce**:
 
@@ -70,7 +72,7 @@ Then, in **Salesforce**:
 If funding amount is less than $5 million USD, startup is deemed **Seed Stage**.
 Follow this flow.
 
-In **Zendesk**:
+In **GitLab Service Desk**:
 
 1. Apply the `Seed stage` macro to send welcome email to customer
 2. Insert a coupon code from the coupon code sheet within the macro
@@ -78,7 +80,7 @@ In **Zendesk**:
 
 Then, in **Salesforce**:
 
-1. Open lead / contact in the Zendesk ticket
+1. Open lead / contact in the Service Desk ticket
 2. Ctrl F "Startups Program Status"
 3. Change to "Qualified" Seed Y1
 
@@ -87,20 +89,24 @@ Then, in **Salesforce**:
 If funding amount is less than $20 Million USD and greater than $5 million USD, startup is deemed **Early Stage**.
 Follow this flow.
 
-In **Zendesk**:
+In **GitLab Service Desk**:
 
 1. Apply the `Early Stage` macro
 2. Set ticket status to `Open`
 
+**Use the Sales Case Routing Sheet**
+
+This sheet can be found [Here](https://docs.google.com/spreadsheets/d/1etzGAGH4n-pzA52xka_VAymMYSE44UBySblXhAEh6rM/edit?gid=0#gid=0) 
+
 Then, in **Salesforce**:
 
-1. Open lead / contact in the Zendesk ticket
+1. Open lead / contact in the Service Desk ticket
 2. Ctrl+F to find "Startups Program Status"
 3. Change to "Qualified" Early Y1
 4. Convert the Lead to an Opp
 5. Rename the Opportunity as `Customer Name, Seats, License Type, Startups - Early - Y(1)`
 6. Chatter Mktgops to assign the correct account executive
-7. Once the account executive has been confirmed, handoff the customer via the Zendesk Ticket
+7. Once the account executive has been confirmed, handoff the customer via the Service desk Ticket
 
 For more clarification regarding Startups sales process, please refer to this [highspot page](https://gitlab.highspot.com/items/6410e355fb9e0fe9d2823fcc?lfrm=irel.1#3)