1. Solution home
  2. Navigation
  3. Settings
Open navigation

Upgraded Notification System

As part of our ongoing commitment to improving our services, we upgraded our notification system in September 2022. This transition was both seamless and successful, culminating in a system that is more reliable and effective. Consequently, we are discontinuing support for the earlier notification system.

  • We've already migrated jobs that had scheduled communications to ensure there is no interruption in your experience. No action is needed from your end for these jobs. 

Example: You have created a job in August 2022, and the archiving date will be in December 2023. In this case, we have already migrated your job to the new notification service. You are all set! 

  • If you would like to send out notifications for a job created prior to September 2022, and it did not have scheduled communications, you will need to transition the job to our updated system manually

Example: You created a job in May 2022, and the archiving day for the job was in September 2022. There are no scheduled notifications left. In this case, the communications are deactivated for this specific job. In case you would like to send additional communication for this job, you would need to manually re-activate the notifications. The good news is that it's just a click: 

If you have jobs created prior to September 2022 with no scheduled notifications, beginning Monday, August 28, 2023, you'll notice a prominent red alert within the Settings tab for these specific jobs.

 

Simply press the Re-activate communications button, and the button will display “Pending” for a moment.


Allow the system to process the request for a moment. 

Then, a red note will appear in green and indicate that the communications have been activated again. 

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article