Currently, the only action after the participant entry is to send an email or create a CTA. I'd like to be able to have any action after entry to have better control over the program flow - specifically wait/conditional wait steps, since those can be configured on fields and not just email activity.
Journey Orchestrator - Allow any action after Participant entry
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
By the way, not sure if this is relevant for your use case but I do want to make sure you know about the Calculated Field capability within Conditional Wait steps. This allows you to query any data (live) as part of making a decision about the flow of the Program.
Consider wanting to be able to send based on time zone.
Present:
Program A x 3, each with its own run time and more complex querying to filter in/out the contacts from relevant countries
Proposed: I bring in all contacts that meet my criteria and immediately enter a conditional wait step:
[Country = A] --> Send Email
[Country = B] --> Wait 6 hours --> Send Email
[Country = C] --> Wait 12 hours --> Send Email
Present scenario leaves a lot of room for error in the original designing as well as edits because they have to be made consistently across all program variations (ask me how I know 😉 ).
Right now, a Conditional Wait step (for a No path) can only be followed by sending an email, creating/closing a CTA, Continue, or End. Why can't a conditional wait step (No path) lead to another conditional wait step? Or a wait step? As in, why does the type of path dictate what the available options are? Any action should be available after any step/path.
Looking at the example in my response to Karl 3 different paths is not actually possible without a lot of extra steps and wait timers.
*Edited for clarification