Wait Flow Action Token

[Anonymous]

Idea is to create a Wait Flow Action Token that includes duration (and all the other options you get in the Wait flow step at the Smart Campaign level), then enable the Wait flow step to use this new token. Right now, the only token you can use in the Wait flow step, is Date.

A Wait Flow Action Token like this would make it MUCH easier to set up nurture flows that have multiple Wait steps that are all the same duration, e.g. "5 days and wait must end on Mon-Fri at PDT."

A Wait Flow Action Token would also help save time re: testing. Right now, for example, when we compress wait times to 1 hour for testing purposes, we have to go back in after testing is done and change the Wait steps in 12+ Smart Campaigns.

With a Wait Flow Action Token we could set it once at the program level and it'd be done, and later if we decided to change all the wait times then we'd only have to change the Wait Flow Action Token.

[Anonymous]

You should check out the new engagement engine feature.  It makes all of this so much easier!

http://community.marketo.com/MarketoDeepDive?id=kA5500000008QlPCAU

[Anonymous]

Thanks Cheryl, for showing us this new engagement engine feature, but it is not what we need. What we need is, a way to have full control over wait steps at the program level, including Duration, because Duration includes minutes and hours. In the new engagement engine feature, Cadence does not include Duration.

Reason #1 for this request is, if we have a 6-month nurture flow, we absolutely do not have time to test it over a series of days; we employ 30-minute and 1-hour wait step durations so we can get everything tested in a single day.

Reason #2: on a more complicated program with multiple flows based on user input, wait step Durations can be as little as 1 hour and are frequently the same throughout the program.

[Anonymous]

Moreover, in some cases, duration can be different depending on what section of the flow users are in. In some sections, users can be in 1-hour duration; in other sections wait step duration can be 6 hours. So you see, Cadence does not cover that. Need more granular control at the program level, and a Wait Step Token could allow that.

[Anonymous]

I understand it may not work for you, however, regarding your first reason, we built a testing feature inside engagement to allow you to run a test without having to change the wait steps as you described.  As for your second reason, a more complicated flow as you described would not be supported in engagement.