Hey Dina!

Let me see if I can help out with this.

1 - This is not possible directly via Iterable, since the email response is not captured by Iterable, but rather is sent to the sender account you have setup in in your project. However, you may be able to build out some process that might automate some response that sender account handles, which could trigger an event to be sent to Iterable which then launches the user into a workflow. That setup would require some engineering on your part, and some use of our API.



2 - This functionality is something we are working on bringing to the platform; something like Availability Hours. The basic layout would be to setup filter nodes to handle custom events based on their createAt timestamp.

The current limitation is that workflow filter logic cannot adapt easily to many timezones, so while we can filter against a specific time, that time is not always related to the users current timezone (all times are stored in Iterable as their UTC converted equivalent, and then rendered in the user timezone when used in templates).

I hope that helps get you pointed in the right direction! Please let me know if you have any other questions.

Best,

Chris

Dina Clark Number 2 is possible with a bit of a workaround in Iterable workflows. We are using it for a similar reason.

You need to add the below node which adds the hour that a user enters the workflow, then before you trigger a message can filter out the hours you do not want to send this.