The Mail Report is a feature in the survey menu that provides an overview of all emails sent during a survey. It helps manage large numbers of emails in bigger projects and offers various editing options for email dispatch processes.

The Mail report, which is located in the survey menu, gives an overview of all e-mails that were sent during the survey. The Mail report is designed to assist you in properly managing the large numbers of e-mails needed for bigger projects. The mail report displays all mails in the outgoing queue, sorted by sending operations. You have the following editing options:

  • View: Allows you to display a mail that has been selected from the respective dispatch process at random with the wildcards replaced.
  • Release: Allows you to release and execute a dispatch process with “Hold” status.
  • Hold: The mail dispatch is interrupted, e.g. if a questionnaire requires re-editing.
  • Delete: Mails are removed from the queue. In EFS Panel installations, this work process includes the option of saving the recipients of the deleted e-mails in a separate group.

If you delete emails, our support team can no longer determine who has already received a mail and who has not in subsequent support requests.

E-mail

Every time you send one or more e-mails from participant administration, an entry is made in the report. This enables you to subsequently check whether, for example, a certain group or individual has already received an e-mail. You may view the complete mail (with placeholders) by clicking on Mail. In the overview list, the following information is displayed for the different sending processes within the respective project:

  • Mailing: internal mailing ID. The link displayed will provide you with detailed information on the specific process.
  • Subject: e-mail subject. The link displayed will provide you with detailed information on the specific process.
  • User: user who performed the dispatch.
  • Date: time and date of dispatch.
  • Total: a total of all e-mails.
  • Queued: a total of all e-mails generated for immediate or future dispatch. Queued emails may be held, resumed, or canceled.
  • Sending: total of all e-mails delivered to the dispatching mailing server yet to be delivered to the respective recipient(s). Please note this process might take up to several days.
  • Sent: The number of e-mails that were successfully delivered to the receiving mailing server.
  • Rejected: a total of all e-mails rejected and classified as spam-mail.
  • Delivery failed: a total of e-mails that could not be delivered due to trouble on the part of the recipient address.
  • Not reachable: a total of all e-mails that could not be delivered because the recipient‘s address or the domain does not exist.
  • Canceled: The number of e-mails canceled.

If you click on the ID of a dispatch process in the “Mailing” column, you will see detailed information on all individual processes.

SMS

Every time you send one or more SMSes from participant administration, an entry is made in the report. This enables you to subsequently check whether, for example, a certain group or individual has already received an SMS You may view the complete mail (with placeholders) by clicking on the SMS tab.

In the overview list, the following information is displayed for the different sending processes within the respective project:

  • Mailing: internal mailing ID. The link displayed will provide you with detailed information on the specific process.
  • Subject: SMS subject. The link displayed will provide you with detailed information on the specific process.
  • User: user who performed the dispatch.
  • Date: time and date of dispatch.
  • Total: a total of all SMSes.
  • Queued: a total of all SMSes generated for immediate or future dispatch. Queued SMSes may be held, resumed, or canceled.
  • Sending: total of all SMSes delivered to the dispatching mailing server yet to be delivered to the respective recipient(s). Please note this process might take up to several days.
  • Sent: The number of SMSes that were successfully delivered to the receiving mailing server.
  • Delivery failed: a total of SMSes could not be delivered due to trouble on the part of the recipient address.

If you click on the ID of a dispatch process in the “Mailing” column, you will see detailed information on all individual processes.

To send SMS notifications via EFS, you need the SMS Extension module.

Viewing Archived Mails

Most of the emails sent from EFS are archived and can be viewed for six months:

  • Personalized surveys, employee surveys, multi-source feedback, panel surveys, and master data surveys feature an overview of all sent emails.
  • In personalized surveys, employee surveys, and multi-source feedback, the mails are listed in the detailed view of the respective participant.
  • In panel and master data surveys, the mails are listed on the Contacts by System mail tab in the detail view of the respective panelist.
  • With the appropriate rights you can view all project-specific mail processes of the installation in a centralized manner

In the long run, the data volumes involved in the sending of emails will put an unnecessary strain on the installation’s performance. Once the project is over, the archived emails are usually not needed ever again. The mail archives will therefore be cleaned automatically at regular intervals: Archived mail will be deleted six months after dispatch (depending on the size of the installation this may be executed earlier).

FAQ

What happens if I delete emails from the queue?

If you delete emails, the support team can no longer determine who has already received a mail and who has not in subsequent support requests.

How long are archived emails kept?

Archived emails are typically kept for six months after dispatch. However, depending on the size of the installation, they may be deleted earlier to maintain system performance.

Do I need any special module to send SMS notifications?

Yes, to send SMS notifications via EFS, you need the SMS Extension module.

Leave a Reply

Your email address will not be published. Required fields are marked *