How we attribute the email

When an Autotask entity is created from an incoming email, we attempt to attribute the message to either a resource in your Autotask instance, or a customer contact. However, customers do not always use an email address you have saved in your Autotask instance. They might use a private email address, or they might be a new employee who is not in your Autotask instance.

For an Autotask entity to be created, the following preconditions must be met or creation will fail:

We first attempt to attribute the incoming email to one of your resources (users), then to a customer contact or co-managing user. If there is no match, but the incoming email's Subject line contains a ticket, task, or project number, the email is attached to the entity as a note. If there is no ticket, task, or project number, but the sender's email domain matches a single organization's web domain, we will associate the entity with that organization. If there is still no match, we will create a ticket either for your local organization The database record of your own organization in Autotask. It has the organization ID "0", and is used as the sender address on quotes, invoices, etc. Previous versions of the help referred to this database record as: 0 Account, Zero Company, Your Own Company., or an organization you have set up for incoming emails that cannot be otherwise attributed. Refer to Ticket Organization (Tickets tab only). If all else fails, we will send a failure notification to the email originator.

If the email matches an organization email domain address

The sender's (originator's) email address determines which organization and resource or contact to attribute the item to, according to the following rules:

We will search resources first.

Flowchart Description

  1. If we find one active matching resource, the item is attributed to that resource.
  2. If more than one matching active resource is found, we will attribute the item to the first matching resource. This is a very unlikely case because it would mean that multiple resources in your Autotask instance have the same email address.
  3. If one active matching resource is found, and the email is also found to be associated with an organization other than the zero account, the ticket is created under the zero account, with no contact.
  4. If the resource has a co-managed security level, it is not assigned to the zero account or the ticket organization. Instead, we continue with the contact check.

IMPORTANT  If the resource has a security level that does not provide View permission to the your local organization account, the resource will not be selected as the ticket contact, although the ticket will be created. To support adding the sender to as a contact to the ticket, you must make them part of the Account Team.

If no resource match is found, we will then search every contact's Email Address for a match. If no match is found, we will next search the Email Address 2 field and, if there is still no match, the Email Address 3 field.

Flowchart Description

  1. If we find one active matching contact, the item is attributed to that contact.
  2. If we find a single matching active organization that has a contact or co-managing user with the same domain as the originator's email address, but do not find a matching active contact, we will create a contact for that organization. Autotask will use the Display Name if available, or <Unknown> as their first and last name. All other fields will be blank, except for UDFs that have a default value.
    In the event that no contact can be identified for a co-managing user, the ticket should be assigned to the organization the co-managing user is configured for if there is only one organization found.
  3. If we find multiple matching active organizations with the same domain as the originator's email address, but do not find a matching active contact, tickets will be created for the Ticket Organization, but without a ticket contact. For all other entities, creation will fail and a failure notification will be sent.
  4. If the same contact with the same email address exists in both the parent organization Your Autotask instance may be configured to use one of the following terms instead: Headquarters, Parent Account, Parent Client, Parent Company, Parent Customer. and a sub-organization Previously: Subsidiary. Your Autotask instance may be configured to use one of the following terms instead: Sub-Account, Sub-Business Unit, Sub-Client, Sub-Company, Sub-Customer, Sub-Site., the email parser will associate the new ticket with the parent organization.
  5. In the event that no contact exists for a co-managing user, and a match based on the incoming email’s domain cannot be made, the ticket is assigned to the co-managed organization with lowest ID that is associated with the co-managing user.
Flowchart Description

If the originator's email references a valid ticket, task, or project number and we cannot determine which contact sent the email, or the contact is not associated with the referenced entity's organization or parent organization, we will add the email content to the entity as a note. For a ticket it will be an internal note; for a project or task it will be an internal project team note. The note's creator will be Autotask Administrator, and we will append From [Sender's email address] to the beginning of the note content.

If we cannot determine the organization based on contact email addresses or if multiple organization matches are found, we will look next to the organization's Website domain, and attempt to find a match.

Flowchart Description

  1. If we find multiple matching active contacts, creation will fail, and a failure notification email will be sent to the originator, with the exception of tickets. Tickets will be created for the Ticket Organization as identified in the mailbox, with no contact.
  2. If we cannot find a matching active organization or active contact, creation will fail and a failure notification email will be sent to the originator, with the exception of tickets. Tickets will be created for the Ticket Organization as identified in the mailbox, with no contact.

For Kaseya tickets, we will determine the organization using the string after the first period in the machine.groupname.subgroupname. Kaseya tickets will not have a contact. They will have a creator of Admin Autotask.

If the email domain is a public domain

If the originator's email domain is one of the common public domains (gmail.com, icloud.com, hotmail.com, etc.), and no matching email address is found, the same rule will apply to search among all contact primary addresses for the same domain. In the unlikely scenario when the domain is only found under exactly one organization in your Autotask instance, the ticket will be created for that organization, and a new contact will be created for the organization. The contact will have the originator's email, and the display name or <Unknown> as their first and last name.

To prevent this from happening, we recommend that you create a Blocklist organization, create a contact for each public domain that you wish to blocklist, and populate their primary email with the corresponding domains.

EXAMPLE  
fakename@gmail.com
fakename@hotmail.com
fakename@icloud.com

Any incoming email from these domains will then create the ticket for the ticket organization (if multiple organizations have email addresses with this public domain) or the blocklist organization, if it is the first incoming email from this domain.

Attributing incoming emails based on a formatted string

Another way to match a ticket to a sender is by using a text string formatted in a certain way. Refer to Enable Organization/Contact matching from email subject/body (Tickets tab only).

NOTE  Also review the following article: FAQs.