Often we are faced with steps in a sequence where we need to wait for something to happen that cannot be directly attributed to the current campaign context. For example, if we are waiting for someone to call, send us a text message, etc. Thus we have introduced a 'wait for next' workflow decision.
This decision is designed to look for prospect activities that happen after the contact enters the wait state. Thus you can look query for a specific history type, wait for this to happen, and the prospect will move through the 'true' path.
If the contact activity is detected within the defined wait time period, we are often interested in some attribute of the detected activity. Thus you can use the contact history query: Most Recent = true
The example above could wait for the next incoming call from the contact then take action if the call was longer than 120 seconds. Make sure you are using global context if the history item cannot be associated with the campaign directly.
Learn about using dynamic fields to access elements of the history item that just happened.
Please sign in to leave a comment.