A field sales team uses a sales accelerator sequence for enterprise prospects. A consultant adds a step that pauses the sequence for seven days once a prospect replies with 'not right now, check back later.' The manager wants reps notified only if the prospect has not engaged again through any channel by day seven, but not to lose the lead from active tracking during the pause. Which configuration meets this requirement?
Select an answer to reveal the explanation.
Short Explanation
The trick here is that the manager wants two things at once: don't bother the rep unless the prospect has truly gone quiet, but also don't let the lead disappear from view during that quiet period. Pulling the lead out of the sequence solves the second problem by breaking the first, since nothing is watching it anymore. Just letting the clock run out and always pinging the rep afterward ignores whatever the prospect actually does in the meantime, so the rep gets notified even when the prospect already answered somewhere else. And having a human manually re-check every lead every week is just manual labor standing in for automation. What actually works is a wait step that keeps watching for any engagement signal during the pause, and only escalates to a reminder if that window closes with nothing happening.
Full Explanation
The correct answer is A. A wait step with an exit condition tied to engagement events keeps the lead inside the sequence, so it remains under active tracking, while letting the sequence branch based on whether the prospect engages again before the seven-day mark. If engagement occurs, the sequence can react accordingly; if not, it routes to a reminder step that notifies the rep exactly when the manager wants it. Option B is incorrect because removing the lead from the sequence means it falls out of active tracking, which the manager explicitly wants avoided. Option C is incorrect because an unconditional resume after seven days ignores engagement entirely, so a rep could be notified (or the sequence could advance) even though the prospect already replied through another channel, defeating the purpose of the pause. Option D is incorrect because manual case-by-case review at scale is exactly the kind of repetitive checking the sequence automation is meant to eliminate, and it does not reliably produce the exit condition the manager described.