Sequence step types

What it does

Steps are the things a sequence actually contains. Some create an activity for the seller to do, some run without the seller and change something on the record or send a message, and one just makes the sequence wait. Which mix you choose decides whether the sequence feels like coaching or like being nagged by a robot.

Key facts

Seller-facing activity steps are Email, Send a text message, Phone call and Task. Each creates a real activity the seller completes from the Up next widget or the record timeline.
Task is the catch-all for anything the standard set doesn't cover — book a meeting, send a sample, internal review. No special behaviour is attached.
Automated variants exist for email and text: Automated email activity and Send an automated text message. Both require a template to be selected — it isn't optional as it is on the manual versions.
Automated email has real prerequisites: email templates in place, email engagement configured, the target record resolvable to a primary contact with a valid email, and Send Email as Another User enabled in the Power Platform admin centre.
Set wait time takes days and hours, up to a maximum of 90 days. It cannot be the final step in a sequence — activation will reject it.
Microsoft's own guidance is to put a Set wait time before any automated step. Without it the automation fires the moment the previous step completes, which is how sequences end up sending an email eleven seconds after a call is logged.
A/B test is a step type in its own right. You configure Version A and Version B with templates, an audience split (10 to 90 per cent, defaulting to an even 50-50), a winning metric, an end condition (automatic or a fixed date and time) and a default version to fall back on if no clear winner emerges.
Command steps sit on their own tab and create no activity. There are two. Advance to another sequence hands control to a different sequence; it cannot be the first step, nothing can follow it, and it is always terminal.
Update field writes a fixed value to a field on the connected record. It supports two-option and option set fields, including custom ones, and can sit anywhere in the sequence. Sellers see it on the timeline.
All of the above are generally available, not preview.

When to use / skip

The step palette is small enough that the real decision isn't which steps exist, it's how heavily you lean on the automated ones. Manual activity steps are safe: worst case the seller ignores them and you have a reporting problem. Automated email and text are outbound communications sent under a seller's name with no human in the loop, and they carry every governance question that implies — consent, tone, out-of-office loops, someone leaving the company.

Use automated steps where the message is genuinely mechanical and low-risk: a confirmation after an enquiry, a "here's the brochure" follow-up, a diary-note nudge. Skip them where the message needs to sound like a person wrote it, which in most B2B sales is most of the time.

Command steps are quietly the most useful part of the palette for consultants. Update field lets a sequence maintain qualification state or a status field without a plugin, and Advance to another sequence lets you build short, single-purpose cadences and chain them rather than one enormous unmaintainable canvas.

Configuration decisions

Which steps are automated and which stay manual — decide this with the sales leadership, not in a technical design session, because it's a brand decision as much as a system one.
Which email and SMS templates back the automated steps, who owns them, and whether template changes need a change-control route given they go out unreviewed.
Wait durations between steps, expressed in the client's actual working rhythm rather than round numbers. Two days and four hours beats "3 days" if that's what the process really is.
Whether to build one long sequence or several short ones chained with Advance to another sequence. Chaining is more work up front and far easier to change later.
Which fields Update field is allowed to touch, and whether any of them are also driven by a business rule, flow or plugin. Pick one owner per field.
Whether the LinkedIn steps are in scope at all, which depends entirely on whether Sales Navigator licences actually exist.

Gotchas

Automated email fails silently in the ways you'd expect and a few you wouldn't. The Send Email as Another User setting in the Power Platform admin centre is the one people miss, because it's nowhere near the sequence designer.
Automated email against an account needs a primary contact with a valid email address. Accounts without one just don't send, and the seller sees nothing useful.
No wait before an automated step means it fires immediately. This is the most common cause of "why did the customer get three emails in a minute" in UAT.
Advance to another sequence is terminal. If someone drops it mid-canvas expecting the original sequence to resume afterwards, it won't, and the designer won't warn them in a way anyone reads.
Update field only handles two-option and option set fields. Requests to stamp a date, a lookup or a text field need a Power Automate flow instead, and that's a different support model.

Consultant notes

Walk the client through one automated email end to end in a demo environment before they sign off on using them. Seeing it arrive from a named seller's mailbox changes the conversation.
Insist on a wait step before every automated step as a build standard. Write it into the design document so it survives whoever picks the work up next.
Keep sequences short — five to eight steps — and chain them. Long canvases are what clients point at when they say the system is too complicated.
Check email engagement is configured and healthy before you promise anything that depends on it; several step and condition types quietly need it.
If A/B testing comes up in scoping, ask for the monthly volume first. It usually ends the discussion politely.

Worth another look when new step types land in a release wave, particularly anything that broadens what Update field can write to.