Set Event Start Date/Time FAQ


Q1: Can I use the "Set Event Start Date/Time" action for recurring events?

A1: Yes, it's typically possible to use this action for recurring events. You can set the Event Start Date/Time for the first instance and then use a "Go To" action to loop back to the start of the workflow for subsequent instances.

Q2: Can I set multiple Event Start Dates/Times in the same workflow?

A2: You can typically add multiple "Set Event Start Date/Time" actions within the same workflow. Each one could correspond to a different event or appointment, and you could then use corresponding "Wait for Event/Appointment Time" steps to create actions relative to each start date/time.

Q3: What happens if a contact enters the workflow after the Event Start Date/Time has passed?

A3: The behavior depends on your settings for the "Wait for Event/Appointment Time" action. If you set it to "Move to the next step" or "Move to a specific step", the contact would skip past the wait action. If you set it to "Skip all outbound communication actions, till next wait or Event Start Date action", they would skip outbound communication steps until they encounter the next wait or start date/time action.

Q4: Can I use the "Set Event Start Date/Time" action without a corresponding "Wait for Event/Appointment Time" action?

A4: It wouldn't be very useful when you could technically set an event start date/time without a subsequent "Wait for Event/Appointment Time" action. The main purpose of the "Set Event Start Date/Time" action is to establish a point in time that other actions can refer to.

Q5: If my workflow settings are set to respect Contact time zones, how does that affect the "Set Event Start Date/Time" action?

A5: If your workflow management tool supports time zones, you would typically set the Event Start Date/Time in your time zone, and the tool would then adjust it based on each contact's time zone. If the workflow doesn't have time zone information for a contact, it would typically use your account's time zone by default.

Last updated