"Request Next Cast" Flow Step

[Anonymous]

A flow step that sends the next cast of an engagement program for a specific lead. Useful if you're linking programs that have smart lists, so a lead doesn't have to wait until the next cast. 

I'm trying to expand the Engagement Program functionality of the "lead won't be sent the same email twice," but instead making it "lead won't be suggested a piece of content she/he has already downloaded." 

Background: We don't want to send a nurture email about a piece of content if the lead has already downloaded that piece. Given resource download is our primary method of lead capture, a lead has already downloaded AT LEAST one piece of content manually from our site. We would also like to have multiple different emails promoting the same piece of content (use case: different chapters of the same big book of B2B marketing).

How I was hoping to do this: 

• Smart lists to record the leads who have already downloaded each piece of content.
• Separate program for each lead nurturing email. Smart list filter = leads who are NOT in the "already downloaded this content" smart list. 
• Engagement program stream linking the appropriate program for each weekly cast. 

The problem I'm encountering (as is Jason B in this discussion) is that if someone has already downloaded the piece of content, they're just skipped for that cast. It doesn't jump to the next piece in the stream, they just run through the program and nothing happens for that cast. A "Request Next Cast" flow step would solve this problem.


Best,
Edward Unthank
Marketing Operations Specialist
Yesler

[Anonymous]

This is a great idea. There are many possible scenarios where additional filters are needed for a particular piece of content (requiring a program in the stream) and this idea would prevent people from missing out on nurturing if they don't qualify. 

[Anonymous]

I love this idea. This scenario was a struggle even with the old traffic cop. With the flow step you suggest, engagement programs have the opportunity to address this pain point.

[Anonymous]

This statement:  The problem I'm encountering (as is Jason B in this discussion) is that if someone has already downloaded the piece of content, they're just skipped for that cast. It doesn't jump to the next piece in the stream, they just run through the program and nothing happens for that cast. A "Request Next Cast" flow step would solve this problem."  

is actually not true.

To make this work, the lead must be a member of the program.  If the lead is a member of the program already, they will skip to the next piece of content.

If there is a smart list exluding the leads then they will not skip, but in the case of they downloaded the content, there should be a progam listening for this and adding them to the membership of the program.  Then they will automatically skip.  So this idea, we have already.  Jason B's idea where he specifically said he wants to exclude leads as a filter, is an enhancement.

[Anonymous]

Thanks Cheryl,

I was going through this logic puzzle after I posted it and realized the same. I think the underlying problem still exists, but the solution I proposed is inadequate. Thanks for the reply!


Best,

Edward Unthank
Marketing Operations Specialist
Yesler

[Anonymous]

Ed, great work with the Exclusion status solution.

Building on your idea, I just wrote up an Idea for an Exclude from Engagement flow step that would populate a special Program status designed specifically to suppress leads from getting certain engagement content. This seperate program status would solve the reporting challanges around inflated program membership.

Idea: Exclude from Engagement flow step
https://community.marketo.com/MarketoIdeaDetail?id=08750000000JvPqAAK