Associating needs-org tickets with appropriate organization

On this page


Associating tickets with the needs-org tag with appropriate organizations

Occassionally tickets come in without an associated organization, which means that no SLA is applied.

Potential reasons this might occur:

It could equally be the case that a ZD organization was manually created and the SLA type is out of date / incorrect. Many of the same principles apply here.

Please avoid manually creating organizations.

Determining if this workflow applies

This workflow applies if:

ZD prompts for an org to be created

Note on Trial License

While SFDC syncs organizations nightly to ZD, it does not include trial licenses. So organizations on a trial will not show in ZD, and this workflow does not apply and ZD admins should not manually create these organizations as trials do not receive paid support except in the same circumstances as free users.

To check if a customer is on a trial: In SFDC (see instructions below), the Initial Source will likely say Trial and Account Type will say Prospect instead of Customer.

This may display slightly differently if the organization was a Former Customer.

In the Customers portal, there is currently nothing to distinguish if a user or organization is on a trial except that there are no invoices or other evidence of billing.

Finding the existing organization in ZenDesk

You may attempt to find the organization within ZenDesk using the search functionality. Do note that TLDs don't necessarily correspond to company names, so you may need to search in SFDC to find the appropriate organization.

Also note that users may be using generic mail providers you might not be familiar with, so the TLD on their email address may not correspond with their company at all.

When in doubt, check SFDC

Selecting an organization in ZD

Finding the existing organization in SFDC

  1. Log in to to SalesForce using the shared credentials in 1Password.
  2. Enter a domain or full email address into the search bar at the top

Search bar, in repose

  1. Look for results in the Accounts section. You should also be able to see if they have a support level if they have one.

Account Name and Support Level in search results

  1. Click the Account Name to get a more detailed view in the GitLab Subscription Information section.

Detailed view with support level

Finding the exisiting organization in customers.gitlab.com

  1. Log in to customers.gitlab.com with the shared admin credentials in 1Password.
  2. In the Customers section, search for a domain or full email address
  3. You can impersonate an account to find out if they have a current subscription

Adding the domain (ZenDesk Admins only)

Important: Be extra careful here. If a large company has multiple subscriptions it may not be appropriate to add the domain. You'll need to add individual customers to the appropriate organization (see below)

Once you've determined the appropriate domain to add and identified the correct ZD Organization, you can click the Domains field to add it.

Filling in an organization domain in ZD

Adding a customer to an organization (All ZenDesk Users)

If you don't have admin access on ZD, you can still make sure the proper SLA is applied by adding the user to the appropriate organization.

  1. Click on the customers name in ZD
  2. In the "Org" field type the organization name

Adding a user to an existing organization

Verifying that the ticket now has the proper SLA applied

Now that you've added the apporpiate domain, head back to your original ticket and verify that it is associated with the appropriate organization and SLA.

Verifying SLA

Associated Trigers: