The time taken for Simpplr's Employee newsletter services to send out the newsletter heavily depends on the contents of the newsletter. For example, if you have more dynamic content and smart blocks, then it will take more time for the newsletter, because Simpplr will need to gather the data from other services and build the newsletter HTML for each individual recipient.

We send newsletters in batches (100 at a time), which means that the recipients will receive the newsletter at different times, and the newsletter will be marked as “Sent” after it’s sent to the last batch of recipients.
We calculate the time taken by the newsletter service to complete the API calls for the other services (listed below) to send out actual newsletter notifications. Typically, the time taken to complete these API calls is almost the same as the time when the recipients receive the newsletter, but in exceptional instances, there can be some delays due to these providers.
- Email - AWS SES
- SMS - Twilio
- Slack - Simpplr notifications service
- MS Teams - Simpplr notifications service
- In-app and push notifications - Simpplr notifications service

Note: Delays caused by the recipient's email service (such as Gmail, Outlook, or a corporate mail server) are beyond our control and are not covered under our service commitment.

Sample data for the time taken newsletter

Below is sample data Simpplr took that indicates typical times it takes to receive a newsletter depending on the number of recipients. Note that your experience may vary depending on the circumstances mentioned above.

Up to 1k recipients: 1 - 2 mins
1k to 5k recipients: 2 - 3 mins
5k to 10k recipients: 3 - 6 mins
10k to 20k recipients: 8 - 12 mins
20k to 40k recipients: 22 - 25 mins

How long does it take for newsletters to reach recipients?

Sample data for the time taken newsletter