Associating needs-org tickets with appropriate organization

1. You are here:
2. Handbook
3. Support Team Handbook
4. Support Workflows
5. Associating needs-org tickets with appropriate organization

On this page

• On this page
• Use case
  • Determining if this workflow applies
• Overall Flow
• Identifying customers and users
  • Identifying customers
  • Identifying and marking prospects
    • Priority prospect with SLA
    • Other prospects
    • Organization incorrectly marked as a Prospect in SFDC
  • Identifying and marking trials
  • Identifying free users
• Associating an organization
  • Finding the appropriate organization name
  • Adding a customer to an organization
  • Removing a user from an organization
• Marking free users

Use case

Tickets often come in without an associated organization, which means that no SLA is applied.

Potential reasons this might occur:

1. It's the first time user has submitted a ticket.
2. The user is writing from a domain name that doesn't match what we have in ZD (for example, using a personal email address for a work-related issue).
3. The user or organization has a no subscription or a trial subscription.

Determining if this workflow applies

This workflow applies if ZD is prompting you to create an organization.

Note: Please do not manually create organizations. This can break the ZD<>SFDC integration and cause users to receive incorrect SLAs. If you notice an organization needs to be created, please notify support-ops to rectify this.

Overall Flow

See also the

• triage page on assigning the correct form, and
• SLA and Zendesk views page for after an org is associated.

Identifying customers and users

Tickets can be created by different types of users. Check whether a requester matches a type in the following order:

1. Customer - Has a paid current subscription for GitLab SaaS and/or self managed.
   • Customers receive SLA on their tickets as described in the Standard and Priority Support section.
2. Prospect - Organization trialing GitLab that is sales assisted, also often referred to as a POC (proof of concept).
   • Prospects do not receive SLA unless sales has manually marked them as a priority prospect.
3. Trial - User or organization that has taken out a trial, typically using the free trial form.
   • Often, users identify themselves as Ultimate based on their trial plan, but Trial users do not get support as mentioned on the Free trial page.
4. Free User - User of GitLab (SaaS or self managed) who has not purchased any type of paid subscription plan, and is not a Prospect.

Identifying customers

If a requester has identified themselves as a paid customer, you can tie the ZenDesk organization to the user if the user meets one of the following:

1. In Salesforce (SFDC), the email is listed as a contact for an organization.
2. Meets proof of entitlement, meaning:
   • For self-managed, the user has provided the required license information.
   • For GitLab.com, user is a member of paid group. Use the GitLab User Lookup app in the Zendesk sidebar to check the user's membership details.
3. Possibly, ask the TAM (Technical Account Manager) or Account Owner (also known as AM / Account Manager) listed in SalesForce, in the #account-management slack channel, to add the user under the contacts for that Salesforce Account. While that's happening, please let the customer know you are reaching out to their TAM/AM to get them properly associated with the organization.

Look up resource: You can use the customer account look up workflow to find the relevant subscription and organization name.

If the user has not met the above criteria:

• If it's unclear, you may need to ask the customer to prove their entitlement (for self-managed, macro: Support::Self-Managed::Locating GitLab subscription).
• If the customer has a subscription, but not for the product they're inquiring about, let the customer know and consider them a prospect.
• If after reviewing the "proof", they do not appear to be a customer, check the following sections on identifying and marking trials, prospects, and free users.

Identifying and marking prospects

The user is a prospect:

• if SFDC Account Type is "Prospect".
• typically self-identified in ZD as "Sales Assisted Trial".

Priority prospect with SLA

When sales has marked a prospect organization with Manual Support Upgrade:

• Associate the org synced from SFDC.
• SLA will be automatically applied based on the priority_prospect tag.

Note: Further tags need to be manually added to show in a single view.

Other prospects

For all other prospects:

• add the prospect tag.

Note: It will be moved to the Free/Self-Provisioned Trial Support view without SLA, so you should also respond with the appropriate Free User macro.

Organization incorrectly marked as a Prospect in SFDC

In SFDC, you may notice an organization has the Type set to Prospect but associated with a non Expired support level, and the account in the CustomersDot shows that the org has a valid self-managed license or a GitLab.com subscription. In this case, you may need to update the org in SFDC:

• Check if Subscriptions section in SFDC contains information about a valid subscription.
• Check if account in the CustomersDot contains information about the purchased subscription.
• Double click Prospect type, change it to Customer and click Save.
• After that, notify @Sales-Support by following the steps similar to the ones in this section to tag them.
• IMPORTANT: if you are not sure about the changes, ask Sales-Support to do it.
• As soon as the org has a valid Customer type, it will propagate to Zendesk.

Identifying and marking trials

If you cannot find an account (organization) in SFDC, when searching by email, you should find:

• a Lead, where Initial Source mentions Trial,
• date is within the last 30 days.

Alternate ways to check:

• GitLab.com: CustomersDot > GitLab Groups Tab > an expiration date under the Trials column. If needed, also check the internal-requests project for manual plan changes.
• Self-managed: LicenseDot portal as per customer info license lookup.

If you identify a ticket as from a trial user,

• add the trial tag to it.
• subscription type field does not need to be updated.

Note: It will be moved to the Free/Self-Provisioned Trial Support view without SLA, so you should also respond with the appropriate Free User macro.

Identifying free users

If you cannot identify a user as a customer, prospect, or trial, mark them as a free user.

Associating an organization

Finding the appropriate organization name

While often they match, the organization name a customer provides will not always match what's in ZD.

Since the ZD organization information is synced from the SFDC Account, if you're unsure, looking up the account in Salesforce for the org name.

You can search for organizations using the ZD search (see screenshow below).

Adding a customer to an organization

Follow these steps after identifying the user as a customer.

To associate a user with an organization:

1. Click on the user's name in ZD ticket.
2. In the "Org" field type the organization name.
3. Select the appropriate organization.

Note: If a customer raises a ticket to add some users in their organization, here are some things to take note of:

• If the user exists in both SFDC and Zendesk, we can associate the user to the org.
• If the user exists in SFDC but not in Zendesk, you can create the user in Zendesk if you desire or just inform the user that when they first submit a ticket in the Support Portal the Zapier process we have in place should auto-associate the user in the org.
• If the user does not exist in both SFDC and Zendesk, we can ping their TAM/AM (via Chatter) and ask them to add the user in SFDC. Once the user is in SFDC, the Zapier process we have in place will also auto-associate the user to their org when they register or submit a ticket via the Support portal.

Removing a user from an organization

If you erroneously assigned a user to an incorrect organization, follow these steps to un-assign a user:

1. Click on the user's name in ZD ticket.
2. Click the "Org" field and type - instead of the org name.
3. Make sure that the user changes were saved - you will see a message like <User Name> was successfully updated.
4. Please remove the form related tags in case if form of the ticket needs to be changed from the ticket as well. For example, Subscription type or problem type tags would be different for SAAS or Self Managed form.

Note: If the organization automatically comes back after un-assigning it, it likely means that this org has Domains specified: if an org has domain.tld in Domains list, any user with @domain.tld will be automatically added to this org. If it is the case, please contact #support_operations Slack channel to discuss and fix it.

Marking free users

After identifying a free user ticket:

• Self-managed:
  1. Change the ticket to use the GitLab CE form if applicable.
  2. Reply using the Free user macro to explain they do not receive support.
• GitLab.com:
  1. Ensure the correct form (accounts or general).
  2. Tell us about your GitLab subscription change to Free user.
  3. Select the appropriate Problem Type.
     • If you cannot choose an appropriate problem type, then check if the user qualifies.
  4. If the user does not qualify for support, use the appropriate Free user macro.

The ticket will be moved to the Free/Self-Provisioned Trial Support view.

For example:

• a user username@domain.tld submits a ticket to GitLab Support.
• you search by the requester's e-mail i.e. username@domain.tld, the e-mail specified in the field Email associated with your subscription, or using the customer's domain and you cannot find any related accounts in SFDC.
• you search for the same data in the CustomersDot and cannot find any accounts there.
• you view any groups the user is a member of and confirm that no subscriptions exist in the CustomersDot
• you view GitLab User Lookup app in the Zendesk sidebar and none of the groups are on a paid plan
• if an account exists in the CustomersDot, no subscriptions are shown and you see Choose a plan that suits your needs when using Impersonate functionality.