The ASM Core Incoming Email module provides great flexibility for a support desk or workflow management system.
The ASM Core Incoming Email module provides great flexibility for a support desk or workflow management system. Any person with access to email can, for example, log calls and action tasks by way of a specific email address. The mail server holding this address will routinely check for these messages and log or update calls and tasks accordingly. This functionality is especially useful for analysts who are out fixing problems in the field or people who are traveling or using hand-held devices and have limited Internet access.
ASM Core has a polling service which can be configured to check a number of incoming mail accounts for any received email messages. If the polling service picks up an email, it can take the appropriate course of action, whether it is to log or close a call, approve or reject tasks, or simply update an existing call, request or task.
the settings configured for the incoming email account in Email Settings in System Administration.
The following actions can be taken as a result of an incoming email:
log calls
update calls
return a summary of calls
close calls
reopen closed calls
approve an Approval Task or User Approval Task
reject an Approval Task or User Approval Task
update a task or approval
update a request
return a summary of requests
return a summary of tasks and approvals
Once the polling service has processed an incoming email, the email is deleted from the mailbox. This is to prevent ASM Core from logging new calls from the same email. If you want to keep a copy of these emails, it is recommended that you set up your mail server such that it sends a copy of every email received by the mailbox used for ASM Core incoming email to another email account.
ASM Core considers SMTP error numbers 501, 503, 550 and 553 to be permanent and fatal errors.
If ASM Core receives an incoming email with any of these errors, it will immediately delete this message and the message cannot be recovered.
Alemba® recommends that if any incoming emails show these error numbers, the mail administrator should review the mail infrastructure to determine the origin of these errors
Logging a Call with Email
A New Call is Logged When:
Unrecognized Subject Line - If the messaging service picks up an incoming email but does not recognize the email’s subject line, ASM Core will log a call based on the details of that email.
Invalid Call Numbers - A call will also be logged if the email matches a recognized subject line but has an invalid call numberand the Log New Call on Invalid Number option is selected on the incoming email server. If Log New Call on Invalid Number is not selected, the email will be discarded and the person who sent the email will not be notified.
Invalid Request or Task Number - If the email matches a recognized subject line but has an invalid request or task number, a call is always logged (whether Log New Call on Invalid Number is selected or not in System Administration).
Who is the User and Logging Analyst?
When a call is logged by incoming email, ASM Core looks in the CMDB for a User or analyst with an email address matching the address used to send the email.
Based on these findings and the settings for the incoming email account used, ASM Core will allocate a User and logging analyst for the new call:
Create New Calls Anonymously: The email address is not defined for an existing User or Analyst in ASM Core.
If an email is sent from an address which does not correspond to any existing ASM Core User or analyst, and Create New Calls Anonymously is selected for the incoming email account, a new User record is created (that is, a new person record flagged as a User) and the call is logged with this User specified in the User field.
The logging analyst is set to the analyst specified in the Default Logging Analyst field on the incoming email account.
If the Create New Calls Anonymously option is not selected for the incoming email account, a call is not created.
Analyst Only: The email address is defined for an existing Analyst (who is not also flagged as a User).
If an email is sent from an address which corresponds to an existing analyst in the ASM database and this analyst is flagged as an analyst only (not as a User), the call is logged with this person specified in the User field.
The logging analyst is set as follows:
If the Use Linked Analyst option is not selected for the incoming email account, the logging analyst is set to the analyst specified in the Default Logging Analyst field for the incoming email server.
If the Use Linked Analyst option is selected for the incoming email account, the logging analyst is set to the person who sent the email.
If an analyst logs a call by incoming email and he is not already a User, the User flag will be selected on the analyst’s person record
Person is an Analyst and a User: The email address is defined for an existing person who is flagged as both an Analyst and a User.
If an email is sent from an address which corresponds to an existing person record in the ASM database and this person is flagged as both an Analyst and a User, the call is logged with the person specified in the User field.
The logging analyst is set as follows
If the Use Linked Analyst option is not selected for the incoming email account, the logging analyst is set to the analyst specified in the Default Logging Analyst field for the incoming email server.
If the Use Linked Analyst option is selected for the incoming email account, the logging analyst is set to the person who sent the email.
Other Actions
The next available number is assigned to that call and the body of the email is automatically entered as the description.
The other fields are left blank, with the exception of the User field, which is filled in depending on who logged the call (see above).
If there are any attachments to the email, they are added as objects attached to the call.
The call will use the call template specified for the mail server that picked up the incoming email.
The call template will determine the call properties such as the partition, call screen set, IPK status and stream, assigned analyst and group, and so on.
Any objects attached to an incoming email will use the Unspecified security profile when added as an object on the logged call.
The history entry that is recorded about attaching this object will also use the Unspecified security profile.
If you have renamed the Unspecified profile, that name will be reflected instead.
Updating a Call with Email
To update an existing call by email, send an email to a ASM Core incoming email account with a recognized subject heading and the call number.
The body of the incoming email is added to the history of the specified call.
Update Closed Calls via email must be enabled in the Incoming email server settings or closed calls will not be updated.
If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the call.
If there are any attachments to the email, they are attached to the call as objects and can be accessed from the Object Explorer option on the Call Details window.
Finally, a note icon is added to the specified call in the Calls Outstanding window to indicate to the handling analyst that the call has been updated.
When ASM Core has updated the call, a return email message is sent with the subject “Call <Call Number> has been updated”, where <Call Number> is the reference number of the call, if auto-reply has been enabled for that incoming email server in Email Settings.
What happens if the Call is Closed?
If the incoming email matches a recognized subject heading for updating a call, but the call is closed:
If Update Closed Calls is selected on the incoming email server, the call remains closed but a note is added to the call with the details of the email. The sender of the email also receives the following message: “Call No xyz has been updated by ASM Core.
If Update Closed Calls is not selected, the call remains closed and the following message is sent back to the sender of the email: “Call No xyz is already closed and has not been updated.”
What Happens if the Call Number or Email address is not recognized?
A New Call is Logged - If ASM Core receives an incoming email with a subject heading used to update a call, but it does not recognize the call number specified in the subject line, it logs a new call if the incoming email account has the Log New Call on Invalid Number option.
The Email is Ignored - If Log New Call on Invalid Number is not selected, ASM Core ignores the email and the person who sent the incoming email is not notified.
Invalid or Unknown Email - If ASM Core receives an incoming email with a subject heading used to update a call, but it does not recognize the sender's email address, it ignores the email.
However, if the Update Calls Anonymously option is selected for the incoming email account, the call is updated.
Ensure updates made via email notify the Assigned Analyst
To have email notifications sent to the assigned analyst or group when a call is updated by incoming email, ensure that the Email at Update via Email In option is selected under IPK Management on the Messaging administration window.
Viewing a Call Summary with Email
A support analyst can check a summary of their calls by sending an email to a ASM Core incoming email account with the following subject:
[MyCalls]
Closing a Call with Email
Rules
What happens if the email comes from an Unrecognized Email Address? If the Close Calls Anonymously option is not selected in the incoming email account, a call cannot be closed by an email sent from an unrecognized address (that is, an email address that does not correspond to a ASM Core analyst or User).
If the sender is flagged as a User only, the call will only be closed if the same User is specified in the User field of the call.
If the sender is a ASM Core analyst, the call will be closed if they own the call or have Take Over rights as part of their IPK Management security role. Otherwise, a return email with the following message will be sent: “Reason: Insufficient Permission”.
To close a call through Email
Send an email to a ASM Core incoming email account with the subject: [CLOSE#xyz] , where xyz represents the call number of the call you want to close. The square brackets are required and It must be a valid open call number.
The call you specified will be closed and a return email will be sent to you to confirm the closure.
Reopening a Closed Call with Email
You must also have reopen closed calls enabled on the Analysts security role and the User security role.
The Self Service Portal must also have Reopen Closed Calls enabled in the Self Service Portal Administrative settings.
If you send an email with all the following conditions met, ASM will reopen the call in ASM Core and add the details of the email as a note to the call (the analyst or group assigned to the call depends on the settings chosen in the Email Settings):
The call number is in the subject line
The Subject is in a recognized format
The specified call is closed
And the Reopen Closed Calls option is selected on the incoming email server
Approving Tasks with Email
To approve an Approval Task through an email, you can:
Send an email to the ASM Core incoming email account with the following subject:
[APPROVE#xyz]
xyz represents the number of the Approval Task you want to approve.
The square brackets are required. For example: [APPROVE#5837]
This includes standard Approval Tasks as well as User Approval Tasks.
Click the Green Approve Button on the email message.
When you click the Approve button, a new email will be launched, correctly formatted.
Enter your comments, if there are any, and send.
Do not change the Subject line
If a task has been successfully approved through incoming email, a return email with the subject “Task <Task Number> has been successfully approved” is sent (where <Task Number> is the reference number of the Approval Task).
The workflow in that request will then proceed as designed based on the approval or rejection of the approval task.
What if the email address in not recognized? If the email address is not recognized, the Approval Task is not approved and a return email is sent, stating that the sender has not been identified.
What if the Email address comes from an analyst or user who is not authorized to do Approvals? If the sender lacks approval rights as part of their Workflow Management security role or does not have Take Over Approvals, a return email with the following message will be sent: “Reason: Insufficient Permission”.
Rejecting an Approval Task with Email
To reject an Approval Task through an email, you can:
Send an email to the ASM Core incoming email account with the following subject:
[REJECT#xyz]
xyz represents the number of the Approval Task you want to reject.
The square brackets are required. For example: [REJECT#5837]
This includes standard Approval Tasks as well as User Approval Tasks.
Click the Red Reject Button on the email message.
When you click the Reject button, a new email will be launched, correctly formatted.
Enter your comments, if there are any, and send.
Do not change the Subject line
If an Approval task has been successfully rejected through incoming email, a return email with the subject “Task <Approval Task Number> has been successfully rejected” is sent.
What if the email address in not recognized? If the email address is not recognized, the Approval Task is not rejected and a return email is sent, stating that the sender has not been identified.
What if the Email address comes from an analyst or user who is not authorized to do Approvals? If the sender lacks approval rights as part of their Workflow Management security role or does not have Take Over Approvals, a return email with the following message will be sent: “Reason: Insufficient Permission”.
The body of the incoming email is added to the history of the specified task or approval.
If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the task or approval.
If there are any attachments to the email, they are attached to the task or approval as objects and can be accessed from the Object Explorer option on the Task or Approval Details window.
Finally, a note icon is added to the specified task or approval in the Tasks Outstanding window to indicate to the handling analyst that the task has been updated.
When ASM Core has updated the task or approval, a return email message is sent with the subject “Task/Approval <Task/Approval Number> has been updated”, where <Task/Approval Number> is the reference number of the task or approval.
Updating a Request with Email
A request can be updated by incoming email. To update an existing request by email, send an email with one of the recognized subject lines.
The body of the incoming email is added to the history of the specified request.
If the incoming email is a reply to an outgoing email from the system, and Truncate Incoming Emails is selected in System Administration, only the reply portion of the email is added to the history of the request.
If there are any attachments to the email, they are attached to the request as objects and can be accessed from the Object Explorer option on the Request Details window.
Finally, a note icon is added to the specified request in the Requests Outstanding window to indicate to the handling analyst that the request has been updated.
When ASM Core has updated the request, a return email message is sent with the subject “Request <Request Number> has been updated”, where <Request Number> is the reference number of the request.
If ASM receives an incoming email with a subject heading used to update a request, but it does not recognize the request number specified in the subject line, it will log a new call.
Viewing a Request Summary with Email
A support analyst can check a summary of their requests by sending an email to a ASM Core incoming email account with the following subject:
[MyRequests]
A return email is sent to that support analyst with a summary of all the requests they are working on, have forwarded, or have been forwarded.
Viewing a Task and Approval Summary with Email
A support analyst can check a summary of their tasks and approvals by sending an email to a ASM Core incoming email account with the following subject:
[MyTasks]
[MyApprovals]
A return email is sent to that support analyst with a summary of all the tasks and approvals they are working on, have forwarded, or have been forwarded.
