Need the ability to schedule JO Conditional Wait & Wait Timers for a specific date/time

+1 for this idea! This functionality is a must to truly leverage automated communication and provide a great customer experience.

Our use case is that we would like to send a thank you email after someone completes a survey. However, we want that email to be sent during normal working hours.

As an example, we would need to create a WAIT timer with the following logic: Wait 2 hours AND when day is a weekday AND time is between 8.30 am and 5 pm.
 

Makes sense. We are planning to add such capabilities in H1 2021.

Hello! I just wanted to follow up on this! We have a few programs that end up triggering emails at all times of the day and night and we would love the ability to limit the send times of an email. 

Following up on this, and adding an additional ask -- would it be feasible to add a “wait until a specific date and time” (not just “wait until a Friday”)? Would also like to know any updates and roadmap plans, since it’s been at least a year since the last update.

Use case:

We send a CSM check-in, and certain emails might need to wait until a specific group of CSMs is available. It’d be much easier to say “wait until mm-dd-yyyy hh:mm:am/pm” rather than “wait 7 days” for planning purposes.

As I build out a pros vs. cons doc re: starting to build our new programs in dynamic JO vs sticking with advanced JO, I wanted to check back in on this. Since we still have a significant number of programs with multiple queries, being able to schedule a conditional evaluate step (or a subsequent wait timer) to wait until a fixed date and time would be massively helpful in allowing us to move forward with our adoption of dynamic JO.

Is this on the roadmap in any capacity?

​@vmallya while thinking on the Action Execution Schedule in Dynamic JO, and the fact that Dynamic JO does not allow for Multiple Queries (like Advanced JO), I had an idea:

Could the Action Execution Schedule be built into the Delay steps?

We can’t currently edit the Action Execution Schedule (and neither can we edit delay steps), but if we were able to schedule Delay steps for a specific

• Number of days
• Range of days we wanted the action to be triggered
• Range of hours we wanted the action to be triggered
• Time zone we wanted the action to be triggered

This ☝ would allow us to have multiple, regional branches for our programs without having to rely on multiple queries.

What would be even better is if we were able to EDIT those delay steps, rather than having relaunch active programs.