Sending email messages
As a service desk agent, you can communicate with customers and other IT users directly from tickets, including incidents, work orders, tasks, problem investigations, known errors, and change requests. You can send emails, request information, and update work notes without needing additional permissions, as long as you have access to the ticket.
This feature provides the following benefits:
- Context-aware communication: Emails sent from a ticket automatically include the ticket ID and title. You can also add customers and related contacts without knowing their email addresses.
- Easy sharing of resources: You can attach files and knowledge articles to emails, making it easier to share reference information with customers.
- Improved security: Emails are sent and received through a generic system account, protecting your corporate email address.
- Complete audit trail: All email activity is captured in the ticket’s Activity feed, ensuring traceability.
- Two-way communication: Recipients can reply directly to system-generated emails, and responses are associated with the ticket.
Attaching knowledge articles to emails
When sending emails from an incident, you can attach one file or one pinned knowledge article. The article can be in any status, but it must have the Publish to External Audiences option set to Yes. If multiple versions of the article exist, only the version pinned to the incident is sent, and the current copy of that pinned article is attached. You can send articles created using any supported knowledge article template, including custom templates. The article content can be in any language supported by BMC Helix ITSM, except Chinese, Japanese, Korean, Russian, and Hebrew. Sending a knowledge article as an email attachment is an asynchronous process, so delivery to recipients might take some time.
To compose and send an email from a ticket
- Open a ticket.
- Click the Email
icon. - In the Compose Email pane, enter the email addresses in the To and CC fields.
Specify the name, login ID, email address, or corporate ID to search for a recipient who has a profile in BMC Helix ITSM. For users who do not have a profile in BMC Helix ITSM, enter their email addresses. You cannot use accelerators—exclamation mark (!) to populate the To field with content from fields on the ticket, such as the assignee.
The CC field is available only in incidents and not in other ticket types. - To see the recipient suggestions, in the To field, press the ↓ key.
For incidents, the system suggests the customer, contact, and assignee when working on an individual ticket, and the assignee when tickets are selected from the Ticket Console. For problem investigations and known errors, the assignee is the suggested recipient for single or bulk tickets. - To search for only those users who are related to the ticket, select the Only search people related to this ticket
checkbox. - To send an email with high importance, select High checkbox.

To use accelerators to draft an email, complete the following steps:
Type an exclamation mark (!) in the email content area or select the Help using accelerators to insert content option.
BMC Helix ITSM opens a list of accelerators, which are fields from the ticket.
- Select an accelerator, and the system adds the value of the field to the email content.
For example, if you select !Description, BMC Helix ITSM inserts the description of the ticket in the email content area.BMC Helix ITSM provides predefined accelerators that differ as per the ticket type. Accelerators are the key fields of the ticket type. You cannot customize accelerators.
If you have opened an incident, and you want to select an existing email template, complete the following steps:
- Click Select email template.
You can view only those templates that are available for your company, support group, and agents.
(Optional) To select a locale for the email template that is different from the default agent-preferred locale, select it from the Locale field.
The table is refreshed based on the locale that you select.Click Yes to rewrite any information that you typed in.
In the Select email template pane, select the template.
Click Apply.
The information from the email template is populated in the email that you are composing. Any existing email that you had composed is overwritten.
- Click Select email template.
- To attach up to one file to the email, click
. - To attach a knowledge article as a reference, click
. - Click Send.
After the email is sent, a link to the knowledge article is displayed in the ticket’s Activity feed. Users following the incident can view the article link in their Updates feed. You can use the link to open the full article in a separate window. The RKM:SHR_RKM_Document_Email_Status form in Mid Tier tracks the email delivery status and maintains failure logs for emails with attached articles.
To track emails in the Activity feed and Updates feed
The Activity feed and Updates feed help you get details of emails sent from a ticket. When the system successfully delivers the email, BMC Helix ITSM adds a feed about the email to the Activity feed of the ticket and the Updates feed of the followers of that ticket. You can search for emails in the filters available in the Activity feed and Updates feed. The Activity feed displays the name of the person who sent the email, the number of recipients, and attachment, if any. You can select the number of recipients to see their names. A link to the knowledge article that you emailed is available in the Activity and Updates feed. You can click the link to view the complete article.
- Open an incident, and in the Activity tab, view the email sent to the recipients from the incident.
Click the name of the recipients to view their profiles.
If the recipient is not registered with BMC Helix ITSM, when you click the recipient's name, an email window with the email address of the person pre-populated in the To field is displayed.- To reply, reply all, or forward the email from the Activity feed, complete the following actions:
- Click
, and select the appropriate option.
The subject is automatically populated in the email, and the email context is added to the body. - (Optional) Select a template for the email.
- (Optional) Attach a file.
- Click Send.
- Click
If the underlying BMC Helix ITSM: Service Desk installation is configured to allow the creation and the updating of tickets by email (version 8.1.00 and later) and the recipient replies to the email note sent from the ticket, then BMC Helix ITSM adds the reply to the ticket and to the Activity and Updates feed.
To track emails in the Email status form
When you send an email with a file or a knowledge article attached to it, you can view the email delivery in the NTE:Notifier log form and the AR System Email Messages form in Mid Tier.
You can track the status of sent emails and PDF conversion of the article in the RKM:SHR_RKM_Document_Email_Status form in BMC Helix ITSM. To find out the status of the email, enter details of the email, such as the incident ID, knowledge article ID, email subject, or the date of sending the email:
The form maintains a record of the email that the system failed to deliver. The following reasons could lead to failure in delivering emails:
- The email server or the classic Smart IT server is down
- The attached file is corrupt
- The file size is more than the set limits
- The file type is not supported in BMC Helix ITSM: Service Desk or BMC Helix ITSM
- Invalid email addresses of the recipients
- Issues in PDF conversion
Based on the reason given in the form, you may rectify the error and resend the email.
Updating filters while updating out-of-the-box email template
If you copy and rename an out-of-the-box template, you need to update the run-if qualification for the filters for the new template name, so that the Source ID gets associated correctly for the new template. For example, if you rename ITSM_Generic_Template and it has a run-if qualification ('EmailTemplateName' = "ITSM_Generic_Template"), then you need to update the following filters:
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetIncidentType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetProblemType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetReleaseApprovalType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetChangeApprovalType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetActivityType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetReleaseType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetKnownErrorType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetWorkOrderType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetChangeType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetRequestType
- NTE:NTS:Email_SystemNT_with_EmailTemplateSetTaskType
Instructions for classic interfaces
Related topics
Configuring Email Engine (Action Request System documentation)
Restricting users from uploading and viewing files with specific extensions (Action Request System documentation)