A consultant is extending a sales accelerator sequence for an enterprise sales team. When a rep completes the 'Send Proposal' step, the manager wants a corresponding task automatically created in the team's external project delivery tool (not Dynamics 365) so the delivery team can begin onboarding preparation. Sales accelerator does not have a native step type for this. What should the consultant do?
Select an answer to reveal the explanation.
Short Explanation
When a sequence needs to make something happen in a completely different system, the trick is not to bend an existing step type to look like it is doing the job — it is to add a step whose whole purpose is triggering an automated flow that reaches out and does the real work in that other tool. That is the only option here that actually creates the task automatically, without depending on anyone remembering to do it by hand. Pausing the sequence just delays things and still needs a human to follow through manually. Sending an internal chat message keeps everything inside the team's own channel and never touches the outside tool at all. And logging an activity with a descriptive name is just a label — the system on the other end never hears about it unless something is actually built to call it.
Full Explanation
The correct answer is C. Sales accelerator does not ship a native step type for creating records in an external project delivery tool, so extending it to trigger that action requires a custom step configured to call a Power Automate flow, which in turn uses the appropriate connector to create the task in the external system. This keeps the automation triggered automatically at the right point in the sequence, exactly as the manager wants. Option A is incorrect because a Wait step only pauses the sequence and depends on a rep remembering to manually create the task elsewhere, which does not satisfy the requirement for automatic creation. Option B is incorrect because sending a Teams message is an internal notification, not an integration with the external delivery tool, and forwarding a chat message does not reliably or automatically create a tracked task there. Option D is incorrect because a phone call step only logs a call-type activity in Dynamics 365 for tracking purposes; it does not invoke any external system, so labeling it 'Notify Delivery Team' does not make it functionally call the third-party tool.