N-able™ N-central™

When working with alerts in N-able™, you should set up N-central™ according to the version you use:

Using N-able™ N-central™ version 6 or later

In order for the Commit Email Connector to identify the CommitCRM Account for the incoming N-central Email notification, you should include the External Customer ID field in the email notification Subject. The External Customer ID in N-central will be used to store the parallel CommitCRM Account' RecordID per customer.
 

To do this, customize the N-central Email template for notifications to include the External Customer ID in the email subject automatically.

See more details in Using N-central™ version 6 or later

Using N-able™ N-central™ versions older than 6

When using older versions of N-central, you may consider two alternative options for setting up the email alerts in order for the Commit Email Connector to analyze them correctly.

Option 1

For the Commit Email Connector to identify the customer for the incoming email alert, the customer's ID must  be in the email subject.
For each customer, hard-code the CommitCRM Account's Record ID in the email template subject so the Email Connector will be able to detect the Account when processing the email.
 

Option 2

This option allows setting the customer's email address as the "From" email address of the incoming alert and use it as the customer's identifier for the Commit Email Connector.
Set the alert's "From" email address per customer to contain the customer's email address (as it has been entered in Commit). You can then teach the Commit Email Connector to detect these alerts and open Tickets for the Account in CommitCRM based on the "From" email address.
 
This option requires your N-able™ server to allow relay in order for it to be able to send emails which will "originate" from the customer's email address. If your servers do not support relay, you should use the first option.
 

See more details under Using N-central™ versions older than 6