[object Object]

A sales leader rolls out Sequences across three teams to standardize prospecting. Six weeks later, the marketing team flags that domain reputation has dropped two points and bounce rates are climbing. The sequences were working as configured, and the configuration was sending six templated emails to every contact regardless of engagement. Sequences are powerful and unforgiving. The discipline lives in the design.

What a Sequence Actually Controls

A sequence is an ordered list of activity steps with timing and branching applied to records, usually leads or opportunities. Each active sequence assigns the next step to the record owner with a due date. The sequence does not send the email itself. It puts a task on the rep’s day and offers them a templated draft to send.

This is the part new admins miss. Sequences are reminders with templates, not automation. If your reps mass-complete the steps without sending the underlying activity, the sequence still progresses and the metrics still light up green.

Designing for Engagement Branching

Linear sequences without branching are spam disguised as cadence. Use the engagement branch to fork on whether the contact has opened, clicked, or replied to a previous step.

Step 1: Email A (intro)
Step 2: Wait 2 days
Step 3: Branch on opened
   Yes -> Step 4: Phone call
   No  -> Step 4: Email B (different angle)
Step 5: Wait 3 days
Step 6: Branch on replied
   Yes -> End sequence
   No  -> Step 7: LinkedIn touch

This shape respects the prospect signal. A flat eight-email sequence does not.

Connecting Sequences to Segments

The cleanest assignment model uses segments, not manual attachment. Create a segment based on a saved view filter and bind the sequence to it. As a record enters the view, it picks up the sequence. As it exits, the sequence pauses or ends based on your config.

<fetch>
  <entity name="lead">
    <filter>
      <condition attribute="leadqualitycode" operator="eq" value="1" />
      <condition attribute="industrycode" operator="eq" value="3" />
      <condition attribute="statecode" operator="eq" value="0" />
    </filter>
  </entity>
</fetch>

This filters hot leads in Manufacturing that are open. The sequence applies automatically and the rep does not have to remember to attach it.

Activity Volume Limits

The platform throttles email activity per user per day to protect the sending domain. Defaults vary by tenant, but plan for 200 sequence-driven emails per rep per day as a working ceiling. If your sequence design implies more, either spread the steps over more days or split the rep load. Hitting the throttle silently queues the activity and the next-step due date drifts.

Measuring What Matters

The default sequence dashboard shows active records, completed records, and step completion rate. None of these tell you whether the sequence creates pipeline. Build a custom report that joins sequence membership to opportunity created and amount won.

<fetch aggregate="true">
  <entity name="opportunity">
    <attribute name="actualvalue" aggregate="sum" alias="won" />
    <attribute name="opportunityid" aggregate="count" alias="cnt" />
    <link-entity name="lead" from="leadid" to="originatingleadid">
      <attribute name="msdyn_segmentid" groupby="true" alias="seg" />
    </link-entity>
    <filter>
      <condition attribute="statecode" operator="eq" value="1" />
    </filter>
  </entity>
</fetch>

This is the report that tells you which sequence is worth keeping.

Pausing for Out of Office

Sequences do not natively detect bounces or out of office replies. Use a Power Automate flow on Email Activity creation that scans the body for the standard OOO phrases and pauses the parent sequence for the duration. Otherwise reps follow up against an empty mailbox for two weeks.

What to do this week

Audit every active sequence for at least one engagement branch and a defined exit on reply. Build the pipeline-attribution report above and rank your sequences by won amount per record, then retire the bottom third.

[object Object]
Share