Batching Message and Task notifications

Dado offers two options for how notifications are sent for tasks and messages: once per Participant and once per Cohort. In both cases, multiple tasks/messages are combined together and sent in a single notification, to reduce the 'noise' for recipients – but the way they are combined differs.


Contents


How Dado batches together Messages and Task notifications by default

By default, Dado will send a single email and/or single Slack/Teams notification for all messages and tasks which:

  • are assigned to the same person
  • are sent/start on the same date and time
  • relate to the same employee's experience (eg: they all are part of the Onboarding experience for Walter Mitty)

This means that an employee enrolled in a training Experience that starts with a message and two tasks will receive a single email containing all three.


Similarly, reminders for tasks are batched together so that all task reminders for the same person that are due to send on the same date and time, are sent in a single email and/or single Slack/Teams notification.


This batching reduces the number of emails/notifications employees receive, reducing 'noise' in their inboxes and increasing their ability to respond in a timely manner.


How to send a combined Message/Task notification for all Participants in a Cohort

In some situations, sending a single task notification for each employee's experience can be overwhelming. For instance:

  • A training supervisor must give feedback on the progress of every trainee
  • An HR team member must review the background check results for every new hire
  • An IT team member must submit a tracking number for every laptop sent out to new hires

For these scenarios, Dado offers a different way to batch together notifications to the default setting.

Default 'Per Participant' batching: all tasks and messages a) sent to the same person, b) in reference to the same employee's experience, and c) starting at the same date and time will be sent in a single notification

  • eg: a message and 2 tasks scheduled for 9am on Monday, sent to the manager of a new hire, will be sent in 1 email
  • if the same manager has 2 new hires starting on the same day, 1 email will be sent for each new hire


Alternative 'Per Cohort' batching: similar messages/tasks for all Participants that start at the same date and time will be sent together

  • eg: the tasks for IT to submit a tracking number for every new hire starting work on Jan 15th will be sent in one email
  • if IT has another task for the same Jan 15th cohort, that starts at the same date and time, it will be sent in a separate email


How to switch a Task/Message to be sent in Per Cohort batches

The setting to toggle between these two kinds of batching is found in the 'Assignee and Sender' settings of Tasks and the 'Sender and Recipient' settings of Messages.

Per Cohort batching is only available for Supporting Actors – not for the Participant. Select a Supporting Actor as an Assignee/Recipient, and you will see batching options appear below:

When to use Per Cohort batching

We advise using Per Cohort batching for any Supporting Actor who does tasks for more than 2 Participants at a time. Examples of this would be:

  • IT Teams arranging access/hardware for New Hires
  • Trainers running training programs for groups of employees
  • Managers doing performance reviews for multiple direct reports at the same time

How do reminders work with Per Cohort batching?

Pre- or post-deadline reminders will obey the same batching rules as the initial task notification.

If Per Cohort batching is selected, all reminders for the same task with the same deadline will be sent in a single notification.

As per usual, reminders will only be sent for tasks that have not yet been completed.

Still need help? Contact Us Contact Us