You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

SimpleOne provides two-ways interaction via email:

  • sending notification emails about changes in the system (including announcements, events, and changes in records or tables)
  • actions in the system depending on the incoming emails.

In SimpleOne, email processing can be automatic within the system without third-party applications.

In the following articles, you will learn:

  • how to configure email accounts
  • how to create automatic actions in the system (changing or creation of records in specific tables) depending on what email you received
  • how to customize automatic email reply depending on values of specific records and received emails
  • how to keep up users with what happens within the system.

Email Accounts


First of all, you need to create necessary email accounts. They will be involved in receiving and sending emails.

The email account configuration includes the following steps:

  1. Creating an email account
  2. Testing the connection (optional)
  3. Configuring default settings.

Notifications


Notification Rules help automatically send email letters depending on the status of specific records. Notification rules allow to define when to send the letter, who will receive it, and what the letter will contain.

For example, when an incident changes to the Information Needed state, the system sends a letter with a specific topic and body to the caller. That is, notifications define what letter a user will receive after specific changes in the system.

SimpleOne provides a number of out-of-the-box notification rules. Refer to the Available Notifications article to see the preconfigured notifications.

Inbound Email Actions


Inbound Email Actions process incoming emails in two ways:

  • send am automatic reply
  • create, update or delete a record in the system.

Use a script to define how the system will respond to which triggers – they can be a specific letter topic, keywords in its body, or more complex conditions. Unlike Notification Rules, inbound email actions provide a way to interact with records in the system.

For example, while processing an incident in the Information Needed state, the system will insert the body of this letter to the Additional Comment field in the Activity Feed when the caller sends their response. The condition is that the caller's letter contains a defined topic, and the number of the task matches the one in the incident record. That is, inbound email action defines what happens in the system after receiving a letter.


  • No labels