A consultant is customizing a sales accelerator sequence for a team selling to mid-market prospects. Before the first call step, the manager wants reps to see a summary of the prospect's recent LinkedIn activity and shared connections, pulled from Sales Navigator, directly in the sequence step's guidance so reps don't have to leave Dynamics 365 Sales to look it up. Which approach extends the sequence correctly?
Select an answer to reveal the explanation.
Short Explanation
Picture what the rep actually sees at that step in the sequence. The manager wants a summary sitting right there, not a delay, not a detour to another channel, and not a raw link the rep still has to click through and read themselves. The Sales Navigator integration already renders that relationship and activity summary right inside the platform, so slotting a step for it ahead of the call gives reps exactly the at-a-glance context they need without ever leaving the tool they're working in. Just pausing the sequence doesn't produce any data at all, it only buys time for someone to go look manually, which is the very friction the manager is trying to remove. Swapping the call for an email misreads what the insight card can attach to. And a scraped link dumped into a text field forces the rep to do the reading and summarizing themselves. The built-in relationship card is the piece designed to do exactly this job.
Full Explanation
The correct answer is B. The LinkedIn Sales Navigator integration surfaces relationship and insight cards, including shared connections and recent activity, directly inside Dynamics 365 Sales, so adding that card as a step ahead of the call keeps reps in the flow of the sequence while still giving them the context the manager wants. Option A is incorrect because a wait step only delays the sequence; it does not pull any LinkedIn data into view, and it slows the entire outreach cadence for no functional benefit. Option C is incorrect because Sales Navigator insight cards are not limited to email templates and can be surfaced alongside call steps, so replacing the call step is unnecessary and would change the sequence's intent. Option D is incorrect because scraping a public profile and pasting a link into a free-text field is both a fragile, unsupported approach and gives reps only a link to click, not the summarized relationship and activity data the manager actually asked for. The supported integration path delivers the summary in place, which is what the requirement calls for.