Implementing Outbound Email
This article discusses best practices for implementing outbound email. Outbound email is used for reminders and notifications about record state changes, such as support case updates or contract renewal notifications. Routine emails can be sent by the system automatically, or users can manually send emails from the system.
This discussion can help you understand your outbound email options so you can make informed design decisions. For more information about configuring email in Agiloft, please see our email training or our email documentation.
Typical Use Cases
Agiloft includes many options for sending emails. Administrators can control and protect record information by providing appropriate options for automatic and user-customized email.
Automated: When a record is created or updated in Agiloft, the system can send an automatic outbound email that includes a pre-defined recipient, subject, and message body containing data from the record. Automatic emails are triggered by two kinds of rules: scheduled or time-based, and conditional rules which run because of changes made to a record.
- When the Status of an approval changes to Pending Approval, send a request for approval to the Approval Team or the Approver.
- When a new helpdesk case is created, notify the Assigned Person or Assigned Team.
Partially automated: A partially automated outbound email process offers more flexibility and control. For example, you might want to allow power users to send a predefined message to a new recipient, but not allow them to attach a document to that pre-defined message. By using partial automation, the administrator retains control of the quality of company communication, but gives staff enough flexibility to send messages without special permissions or help.
- When contract administrators want to communicate with a separate party regarding a contract, allow them to write a custom message, but filter available recipients to contacts of the other party.
- When a staff member wants to communicate with specific recipient groups, allow them to use pre-defined templates to populate a message body.
Free form: The user is given permission to compose a unique message not based on a template.
Automated Email Notifications
Automated emails are sent by rules in response to record edits or at scheduled intervals. Since this method doesn’t require user interaction, it is most useful when the email doesn’t need to be customized. For instance:
- Record inactivity reminders, SLA compliance notifications, and due date reminders.
- Completion, expiration, publishing, and other status-based notifications.
- Assignment, reassignment, and update emails.
Rules and actions can be configured precisely based on the business and user requirements. Consider how to identify the recipient and any CCs, what information should be included in the body, and how the system will respond to edge cases when designing email rules.
Send Emails with a Rule
To view, edit, or create email actions related to a rule...
- Navigate to Setup [Table] > Rules and edit an existing rule or create a new one.
- Give the rule a name and conditions. These vary depending on the table and rule purpose.
- On the Action tab, click Create Email Action.
- On the General tab, give the action a name and description.
- The Email tab contains all preexisting templates. Choose an existing template or create a new email to send when the rule runs.
To manage or create email templates...
- Navigate to Setup > Email.
- Under Email templates click Go to Rule/Workflow Emails.
- Select the table where the email will be sent from and click Next. From this wizard you can create, copy, or delete all email templates that are used in actions and exist in the selected table.
- Does not require building custom text fields or a creating a separate email template table.
- Ability to streamline communication about precise data by including field variables and record hyperlinks in the body of email templates.
- Ability to restrict email recipients and content to a discrete set of options, ensuring consistent communication.
- Prevents human error by running on an automated schedule.
- Users cannot customize any part of the message or send to other recipients.
- Conditions for rule-triggered, automated emails can be difficult to configure.
- There is less transparency in automatic email processes; users may not know who sent what information to whom or when.
- Rule interactions may post unnecessary messages.
Partially Automated Emails
There are many ways to partially customize an email sent from Agiloft. We will discuss two of the most common configurations below.
Customizable Emails from Process Records
Allowing users to send emails directly from records is a more flexible option than fully automated email. This method lets users create custom messages and subjects and helps them choose recipients and attached files by offering a list of users or files linked to the record. With this method, users can address messages to any recipient in the system and send with an action button. Here is an example of how this setup might look:
In the image above, the Recipient list is set up to provide a list of possible recipients such as contract managers and contacts linked to the contract. Similarly, the Files to Send with Email is a multi-select input listing linked files. The Email to CC field offers a manual way to add extra email recipients, and the subject and body are free-form.
The following section gives step by step instructions for creating this email operation in your own knowledgebase.
Implementation for Sending Email from within a Process Record
Note: If you wish to include the option to add attachments to emails, you must have an attachments table to link to.
To send emails from within records, add the following fields to the desired table:
|Email Subject||Short Text|
|Emails to CC|
Files to Send
Link to single field from other table
Link to single field from other table
|Send Email||Action Button|
- In the layout wizard, create an Email tab and arrange your fields on the layout.
- Note: This particular configuration was built for the Contracts table of a Contract Management system, but can be adapted for other applications.
- Users have full control over the subject, body, and recipients of the email.
- Users are given a list of possible recipients which they can select.
- Requires more setup time, since you need to create fields to hold the subject, body, attached files, and recipients.
- Field variables cannot be included in a custom message body.
- Less automation means more work for the user.
Manually Sent Emails from Predefined Templates
Manually sending email templates with predefined messages and bodies requires a separate table that includes fields for attachments and recipients. This configuration is like Customizable Emails Sent from Process Records, with a few notable differences:
- Instead of text and short text fields for the email body and subject, a drop-down menu with pre-defined email templates is available to auto-populate the text.
- Users can be given permission to customize the templates, or permissions can be restricted to sending alone.
- Because the drop-down auto-populates from existing email templates, a separate table to hold the templates is required.
- Maintains efficiency and quality in company communications while providing some flexibility. To limit user error, fields in the template table can filter templates available in the process table.
- Provides flexibility by allowing users to select and send email templates at any time. You can allow limited modification of email sent with templates.
- Building a new table with email template records adds complexity to your KB.
- You cannot include field variables in email template bodies, which limits flexibility.
Free Form Emails
With the email icon found on the action bar, users can select multiple records from a table view and send email in mass format. This method provides the flexibility to modify existing templates and choose recipients, similar to sending emails from process records. You can choose to import from a template or write the content manually, thus giving users the ability to send fully customizable or partially automated emails from a table view.
Sending Emails with the Email Icon
- From your table view, select a record (or many records) to email. Mouse over the printer icon.
- Click Send Email or choose a template.
- In the Template wizard you can write the email from scratch, send it from a pre-defined template, or start with a template and make customizations from that.
- To populate from an existing template, select the users you want to email and mouse over the email icon.
From the drop down, either select a template or choose Manage Templates. Existing templates are found in the space illustrated below.
The template appears in the email wizard after it is selected, allowing users to make edits specific to their needs.
- With appropriate permissions, users can edit any part of an email sent with a template, providing maximum flexibility.
- Field variables and hyperlinks can be included.
- You do not need an extra table with custom fields unless staff need to make modifications.
- Navigating the Templates wizard found under the email icon is a less intuitive process than filling out standard email fields.
- Users must be trained and given specific permissions to access and use email templates.
When gathering requirements, these questions will help you determine the best email solutions based on the user requirements:
- What kinds of emails do you want to send automatically?
These might include notifications about record creation, update notifications, or time-based (due date) notifications.
- What kinds of emails will users need to send manually?
These might include emails unrelated to record changes or schedules, such as irregular or personal communications.
- Will users write to recipients not held by fields in the record?
If so, you must create a field to hold the recipient email addresses. If this field is multi-choice rather than free form, you can use a filter to make finding email addresses more convenient. For example, you could restrict available email addresses to those associated with a given company.
- Will users write or modify the body of email templates spontaneously?
If so, you will need a field to hold this text. Email templates may be held either in a simple list in the process table or in a separate source table, and pulled into the process table as a linked set. The advantage of the latter is that you can create filters to make finding the templates easier.
Since filters are dependent on fields in a source table, the fields for a filter must exist in the source table before you create the filter. For example, if you want to restrict templates available in the process table to those for a certain Contract Type, you must have an existing Contract Type field in the source template table.
- Do users need to specify attached files?
If so, you must create a field to hold the available attachments.
- What is the role of the user and how advanced is their technical knowledge?
Partially modifiable, automated templates are convenient, but complex interfaces with many fields and options can be overwhelming. If your users have less technical experience, more automation may be preferable.
- Does email need to include record data in body?
If so, a template with record hyperlinks and variables will transfer this information most conveniently.
Email within Applications
Individual applications present unique requirements and challenges for configuring email preferences. Below we have described a few common examples of how emails can be used within help desk, contract management, and document management systems.
Certain kinds of email are useful for tickets in the Help Desk application:
- Assignment notifications to the Assigned Person or the Assigned Team.
- Notes To/From Customer field update notifications to the Submitter.
- Notes To/From Customer field update notifications to the Assigned Person or Assigned Team
- Completion notifications to the Assigned Person or Assigned Team.
Because these outbound email notifications are standard, sent to recipients already in the record, and triggered by record creation or modification, it is best to automate them.
It is possible to automate many notifications in the Contracts table, but users often need to send a specific contract document or non-standard message, frequently to addresses not stored in the system. To accommodate those needs, there are more email fields and filters in the Contracts table. Available recipients can include External Contact(s) to Email or Internal Contact(s) to Email, depending on whether the Recipient(s) field contains External Party Contacts, Internal Party Contacts, or both.
This means that some automation is possible, but you will most likely need to give your users the flexibility to make decisions.
In the following examples, customized emails were required, but most were based on reusable templates. This is a useful option because it preserves the quality of the material by providing a template for users to start with, but still allows the flexibility to make decisions and customize according to vendor or file type.
Reusable templates also save time by eliminating the necessity for users to rewrite a standard email every time.
- Typical Use Cases
- Automated Email Notifications
- Partially Automated Emails
- Free Form Emails
- Key Questions
- Email within Applications