Event Server module supports automatic sending of alert emails based on respondent level data. It can be used in client satisfaction surveys for quickly and automatically detecting dissatisfied clients or to track low aggregated scores quickly. 

Two types of Events exist in Dapresy Pro:

  • Events based on Respondent level: the thresholds are defined on a respondent level. E.g. if an answer on a questions is below/above a certain value the Event is triggered and an email sent out.
  • Events based on results: the thresholds are defined on an aggregated level. E.g. if the % (or mean value) result of answer is below/above a certain value the Event is triggered and an email sent out.



If a client (respondent) is dissatisfied an email can be sent out to a manager within the company with respondent information such as open-ended comments, background information, and contact details. In a project, multiple Events can be created and each one has a defined condition (which result should trigger the Event email), a list of recipients and a defined content to include in the email.


Here is an example of email:

The client(s) below will defiantly not recommend our company to family and friends. Please follow up those customers by using our internal policies.
Name: James Andersson
NPS score: 1
Negative comments: Lorem ipsum….
Phone number: XXX XXXX
Email address: XXX@XXX
Response date: 20130625
Travel date: 20130623

Name: Lars Karlsson
NPS score: 2
Negative comments: Lorem ipsum….
Phone number: XXX XXXX
Email address: XXX@XXX
Response date: 20130624
Travel date: 20130620
Best Regards
The CSI Team”


Note: The Event Server is not included in the standard license hence no Administrator user has access right to it. For prices please contact your account manager or sales@dapresy.com


The Events emails are sent out automatically every time new data is activated in the project. 


A respondent will be included in one Event email only and not every time a new email is being sent out. The logic is based on the Respondent ID so if the Meta data transformation is used for adding the Respondent IDs to the data sets an Event email will be sent out twice for the same respondent if the same data set is imported twice. To make sure the same Event email is not sent out twice for the same respondents include a Respondent IDs in the uploaded data file.

The Event Server module is located in the Project Settings tab (in the project administration pages). In the page new Events are created and it is also possible to view the history of all Events. The image below shows where to find the Event Server page.




To create an Event the following must be defined:


  1. The Condition – what should trigger the Event
  2. A Mail template – which information should be included in the email
  3. A list of recipients – who should get the Event emails.


The Conditions and Mail templates are being created as separate items, when creating the Event one or several Conditions and one Mail template is connected to the Event. This logic makes the setup of multiple events efficient.