Tickets that arrive by email
How an email to the desk's address creates a ticket, how replies are added to the same thread and what happens with people who aren't users.
On this page
Every service desk has its own email address. What arrives at that address becomes a ticket, and the team's replies go out from it. That way the requester can do everything by email, without entering the portal.
Where to see the desk's address
In the ticket list, below the title, Desk email: appears with the address.
If you are the desk's Lead, in Settings, Email tab, Desk address field.
Administrators connect each desk's mailbox in Settings → Email, Mail server tab.
How an email becomes a ticket
Someone writes to the desk's address.
Elion ITSM checks the email: it discards auto-replies, bounces and loops, and rejects suspicious email (spam or a sender that couldn't be verified).
If the sender is a company user, or the unknown senders policy allows it, a ticket is created in the desk:
the subject becomes the title;
the body becomes the description, with the notice Written by the requester;
allowed attachments are added to the ticket; those that aren't accepted are skipped;
the people in copy (Cc) who are company users become watchers.
The ticket is assigned with the same rules as any other (see Take and assign a ticket). On the ticket page, its origin says email.
If your company turned it on, the sender gets an auto-reply with the ticket number.
How replies are added to the same ticket
When the requester replies to an email from Elion ITSM, their reply is added to the same ticket's conversation, with the email label. Elion ITSM recognizes it in two ways:
Because it replies to an email sent by Elion ITSM.
Because the subject has the ticket number in square brackets, for example
[INC-000123]. This only works if the person writing is the requester, the person on whose behalf it was requested, a watcher or a company user.
The new text of the reply is kept; the quoted part of the previous email is trimmed.
Also:
If the ticket was On hold with Waiting for the requester, it goes back to In progress by itself.
The assignee gets a notification of the reply; if there is no assignee, the group does.
If the ticket is already Closed or Cancelled, the reply isn't added: a new ticket is opened.
Senders who aren't users
What happens when someone who isn't a company user writes depends on the policy the administrator chose in Settings → Email, Policies tab, Unknown senders section:
Option | What happens |
|---|---|
Reject (registered people only) | The email doesn't create a ticket. |
Create the requester and open the ticket | Elion ITSM registers the person as a requester and opens the ticket. |
Create the requester only if their domain is allowed | Same as the previous one, but only for the domains in the allowed domains list. |
In a CSM desk, if the sender's domain matches that of a customer account, the new person is linked to that account (see Accounts and contracts (CSM)).
An external watcher, added by email, can reply to their ticket's thread even if they aren't a user.
The team's replies
When someone on the team replies to the requester from the ticket page, the reply goes out by email from the desk's address to the requester and the watchers. Internal notes never go out by email.
If an email didn't reach the desk
The administrator can check it in Settings → Email, Log tab: it shows what came in and went out, with its status (for example, processed, ignored or rejected) and the ticket it generated. For privacy, the log shows the sender masked and never the email body.
Related
Settings: Settings → Email