Skip to main content
Version: 8.5.0

Emails

Emails are used for sending and receiving notifications when any event occurs. This can be achieved by configuring the email server in the ServiceOps Portal.

The benefits of setting up the email server are:

  • Requesters can create requests using the email.
  • ServiceOps can send Email Notifications and Announcements.

Whether self-hosted or cloud-hosted, you can add any email address to the system using the email protocols like: SMTP, MAPI, POP3, and IMAP.

To view the Emails sub-menu, navigate to Admin > Support Channel > Emails.

Emails Menu

It consists of three tabs:

note

After upgrading the ServiceOps version from 8.0 to 8.1, kindly re-configure all the email servers as more parameters are added for configuration.

In ServiceOps version 8.0, the email configuration was based on the Client ID, Client Secret, Tenant ID, and the Authorization URL details. And now in version 8.1 onwards, it is based on the Client ID, Client Secret, Authorization URL, Token URL, Scope, and Redirect URL.

Outgoing Email Servers

This enables you to configure the outgoing email server and its rules using which the system will send the email notifications. You can have multiple Outgoing Email servers and rules.

Adding Outgoing Email Server

To create a new server, click on the Add Outgoing Email Servers button at the top-right corner of the page, and a side popup appears.

note

The server configuration information is available with your email service provider.

Add Outgoing Email Server

Enter the following details:

  • Name: Enter the name of the email server.
  • Email: Enter the email address.
  • Protocol: Select the protocol as SMTP or MAPI.
note

The selected protocol must be enabled on your email account. For example, If IMAP is selected, ensure that it is enabled.

  • Sender Name: If SMTP is selected, enter the sender's name.
  • Email Provider: Select the provider using which you want to send emails between the two options.
    • Sign in with Microsoft
    • Other
  • Reply-To Email: Enter the email address for replying over the email.
  • Proxy server: Select the proxy server to use to establish the email connection.
  • Enabled: Toggle the switch to enable or disable the server.
  • Primary: Enable if you want to use this server as primary for sending emails.

Setting Up a Microsoft Email Server

Prerequisites:

  • The URL https://email-app.serviceops.ai/ should be accessible.
  • Internet connectivity should be available.
  • The protocol used for connecting to the Email Server must be enabled on your email account. For example, If IMAP is selected, ensure that it is enabled.
  1. Click on the Sign in with Microsoft option to use the Microsoft email service.

  1. Select or sign-in to the Microsoft account you want to use.

  1. Click Accept and grant the permissions required to setup the email.

  1. Once done, save the configuration. The details will appear on the email server list. Now, check the connectivity using Test Connection. Once connected, you will receive a confirmation email saying the settings of Microsoft is properly set.

Setting Up Other Email Servers

Enter the following details:

ParametersDescription
NameEnter the name of the email server.
EmailEnter the email address.
ProtocolSelect the protocol that the email server supports. The options are: SMTP and MAPI.
Sender NameEnter the name of the sender.
Email ProviderOther
ServerEnter the address of the server.

For SMTP:

Azure: smtp.office365.com

Gmail: smtp.gmail.com

PortEnter the port number of the email server. For SMTP (TLS): 587, SMTP(SSL): 465
Security TypeSelect the type of security that the email server supports. The options are: None, SSL and TLS.
Authentication NeededEnable the flag if you want the user to authenticate to the server while logging in.
Email Auth Type

Select the type of authentication that you want to use. The options are:

- Basic Auth: If selected, enter the Gmail address in Username and password details. To know more details about configuring Gmail as an authentication server, refer to the link Configuring Gmail for Basic Auth. Note: Basic Auth is not supported for Microsoft Outlook.

- OAuth: If selected, enter the Client ID, Client Secret, Authorization URL, Token URL, and Scope. These details can be retrieved from the application created either in the Azure portal or Google Developers Console.

To know more details about configuring the Microsoft Azure as an authentication server, refer to the link Configuring Microsoft Azure for OAuth.

To know more details about configuring Gmail as an authentication server, refer to the link Configuring Gmail for OAuth

Reply-To EmailEnter the email address for replying over the email.
Proxy ServerSelect the required proxy server.
EnabledToggle the switch to enable or disable the server.
PrimaryEnable if you want to use this server as primary for sending emails.

Once done, click Save to add the Outgoing Email Server. Once the server is configured, you can later check its connection using the Test Connection button from the server list page as shown below.

Test Connection

Configuring Outgoing Email Rules

Outgoing email rules are used to route emails through specific email servers on the fulfillment of the said conditions.

In order to achieve this,

  1. Click the Configure Outgoing Email Rules button and the below popup appears.

  • Click the Add Outgoing Email Rule link and enter the details.
    • Enable the rule.
    • Select the desired Outgoing Email Server from the dropdown.
    • Set one or more conditions based on which the Email server will be selected for sending emails.
  • Similarly, you can add more rules. You can add as many rules as you want and enable/disable them according to your requirement.
  • Once done, click Update. Its audit entry will appear in the Configuration Audit tab.

Incoming Email Servers

This enables you to configure the Microsoft Email server or your own email server using which the system will receive email notifications. You can have multiple incoming email servers.

To create a new server, click on the Add Incoming Email Servers button at the top-right corner of the page, and a side popup appears.

note

The server configuration information is available with your email service provider.

Add Incoming Email Server button

Configuring Incoming Email Server in ServiceOps

Enter the following details:

  • Name: Enter the name of the email server.
  • Email: Enter the email address.
  • Technician Group: Select the technician group that should be assigned when a new request is created via the email.
  • Category: Select the category that should be assigned when a new request is created via the email.
  • Proxy Server: Select the desired proxy server.
  • Email Provider: Select the provider using which you want to send emails between the two options.
    • Sign in with Microsoft
    • Other

Setting Up a Microsoft Email Server

Prerequisites:

  • The URL https://email-app.serviceops.ai/ should be accessible.
  • Internet connectivity should be available.
  • The protocol used for connecting to the Email Server must be enabled on your email account. For example, If IMAP is selected, ensure that it is enabled.
  1. Click on the Sign in with Microsoft option to use the Microsoft email service.
  2. Select the Protocol that should be used for email configuration. the options are IMAP and MAPI. Here, MAPI is selected.
  3. Again click on the Sign in with Microsoft option to use the Microsoft email service.

  1. Select or sign-in to the Microsoft account you want to use.

  1. Click Accept and grant the permissions required to setup the email.

  1. Once done, save the configuration. The details will appear on the email server list. Now, check the connectivity using Test Connection. Once connected, you will receive a confirmation message.

Setting Up Other Email Servers

Enter the following details:

Parameters            Description
NameEnter the name of the email server.
EmailEnter the email address.
Technician GroupSelect the technician group that should be assigned when a new request is created via the email.
CategorySelect the category that should be assigned when a new request is created via the email.
Proxy ServerSelect the proxy server to use for establishing connection.
Email ProviderOther
ServerEnter the IMAP address of the server.
ProtocolSelect the protocol that the email server supports. The options are: IMAP, MAPI, and POP3.

The protocol used for connecting to the Email Server must be enabled on your email account. For example, If IMAP is selected, ensure that it is enabled.

Note: To avoid delays in receiving emails via POP3, it is recommended to use the MAPI or IMAP protocol instead.

PortEnter the port number of the email server. The numbers are: IMAP: 993, SMTP: 587, and POP: 995.
Security TypeSelect the type of security that the email server supports. The options are: None, SSL and TLS.
Email Auth Type

Select the type of authentication that you want to use. The options are:

- Basic Auth: If selected, enter the Gmail address and password details. To know more details about configuring Gmail as an authentication server, refer to the link Configuring Gmail for Basic Auth. Note: Basic Auth is not supported for Microsoft Outlook.

- OAuth: If selected, enter the Client ID, Client Secret, Authorization URL, Token URL, and Scope. These details can be retrieved from the application created either in the Azure portal or Google Developers Console.

To know more details about configuring the Microsoft Azure as an authentication server, refer to the link Configuring Microsoft Azure for OAuth.

To know more details about configuring Gmail as an authentication server, refer to the link Configuring Gmail for OAuth

Company

Select the company that should be assigned to the request when created via email.

Note: This field is available only if Managed Services Provider feature is enabled.

EnabledToggle the switch to enable or disable the server.
PrimaryEnable if you want to use this server as primary for receiving the emails.
Outgoing Email SeversEnable if you want to set the outgoing email server. If enabled, select the desired Outgoing Email from the dropdown.
Filter TypeSelect whether to allow or ignore the emails received.
EmailsAdd the email addresses that should be evaluated based on the filter type selected.
DomainsAdd the domains that should be evaluated based on the filter type. For example: yahoo.com.
KeywordsAdd the keywords that should be evaluated based on the filter type. The system will look for keywords in the email subject and body.

Once done, click Save to add the Incoming Email Server. Once the server is configured, you can later check its connection using the Test Connection button from the server list page as shown below.

Test Connection

See Also:

Additional Information (Primary Email): Suppose Mr. Sam is sending an email to request@motadataservice.com to create a request from his email address sam@example.com. The system will communicate with Sam from request@motadataservice.com only. Later in some stage, if request@motadataservice.com does not work. In this case, the system will look for the primary email address. For further communication, the system will use the primary email address until request@motadataservice.com comes up again.

Email Preference

This tab enables you to set the email configurations. The settings are:

Email Preference

  • Enable Email to Ticket: Allow users to create a new request by sending an email. Any user (registered/unregistered) can send an email to generate a request. If enabled, a requester can send an email on the email address configured in the Incoming Email Server. The email's subject line will be used as the Request Subject, and its content will become the Request Description. Additionally, this information will be accessible in the Work tab on the Request Details page in both the Technician and Support Portals.

  • Allow Guest User to generate request from E-mail to Ticket: Enable to allow the guest user to create request using the Email to ticket feature. By default, it is enabled. If disabled, the Guest user can send the Request email to the configured Incoming email address, but the Request will not be created.

    Also, if the option "Allow Guest Requester to report a Request" is disabled from the Support Portal Settings, the Guest user will be able to report a Request from the Support Portal but not using the Email to Ticket feature.

  • Select Recipient Type Considered as CC User for Requests: Select the type of recipients (To and CC User) to be considered as CC users while creating a ticket and adding them to the "Cc Emails" field of the Request Details Other Info section.

For example, if "To User" and "CC User" options are selected, and while creating a ticket, if jerry@motadata.com is written in the "To" field and in "CC", john@motadata.com and james@motadata.com are mentioned. All three email addresses will be added to the Cc Emails field as shown in the below figure.

note

The email address configured as an Incoming Email Server will not be considered in the Cc emails.

Email Preference

  • Use Reply-To email address to create Requester?: If the requester has configured a reply-to email address, the system will create the requester account using the reply-to address. Else, the system will create the requester using from email address.

  • For forwarded emails by Technicians, consider original sender as Requester: If the ticket is in the form of a forwarded email by a technician, enabling this flag will consider the original sender as the Requester.

  • Allow User to select Outgoing Email: Enable to allow users to select the desired Outgoing Email server for sending emails. If enabled, the Outgoing Email field will appear in the Notification and Work Conversations tab of Incident and Service Request Details page.

  • On reply received from requester for closed request

    • Add reply to request: Add reply to the request.
    • Reopen request and add reply to request: If selected, enter the Grace Period in number of days. If the request is received within the grace period, it will be reopened. If the request is received after the grace period is over, a new request will get created.
    • Create new request: Creates a new request.
  • On reply email received from other than assigned technician on request

    • Add reply mail as collaboration: Enable the option to include email replies from technicians, other than the assigned one, as part of the collaboration on the request.
    • Add reply mail as reply: Enable this option to add email replies from users, other than the assigned technician, as a response to the request.