Sales Sequence Management

Administrative workflows controlling enrollment, unenrollment, and routing to sales sequences

MetricValue
Workflows10
Priorityhigh
Grouping Confidence90% — All workflows focus on sequence lifecycle management with clear administrative patterns
ConsolidationCreate unified sequence management with enrollment criteria evaluation and compliance-based unenrollment rules

Workflows in this Group

WorkflowTriggerOutcomeTypeComplexity
Add to sequence (events)Event attendee contact meets criteria for outbound sequenceEnroll contact in automated outbound sequenceRoutingmedium
Add to sequence (events) - from CSMCustomer Success Manager identifies a contact who should be enrolled in an events-related sales sequenceContact is automatically enrolled in a predefined sales sequence for event-related outreachRoutinglow
Add to sequence (webinar)Contact registers for or shows interest in a webinar and should receive follow-up sales outreachContact is enrolled in a webinar-specific sales sequence for nurturingRoutinglow
Admin_Unenroll from SequenceAdministrator or system determines a contact should be removed from active sales sequencesContact is unenrolled from sequences and related tasks are marked completeEnforcementmedium
Admin_Unenroll on Call OutcomeCall outcome indicates contact should be removed from active sales sequencesContact is unenrolled from sequences, tasks marked complete, and branching logic applied based on email campaignEnforcementhigh
Admin_do not enroll in sequenceAdministrator identifies contacts that should be prevented from sequence enrollmentContact is blocked from sequence enrollment and related tasks are completedEnforcementmedium
ADMIN_ BDR call sequenceContact reaches a stage where BDR should initiate a calling sequenceBDR receives structured guidance or automation for systematic calling approachEnforcementmedium
ADMIN_add to re-enroll listContact needs to be added to a re-enrollment list for workflow managementContact is systematically added to and removed from re-enrollment management listsEnforcementmedium
Inbound to Outbound - Email Sequence and BDR AssignmentInbound lead needs to be converted to outbound prospecting approachAssign BDR and enroll prospect in outbound email sequenceRoutingmedium
Admin_Inbound RB2B to Outbound Sequence (BDR) (cloned)RB2B (Reveal Bot to Business) identified prospect needs outbound follow-upEnroll RB2B-sourced prospects in BDR outbound sequenceRoutinglow

Key fields: hs_task_status, os_last_email_campaign_name, make_hold

Dependencies: External sequence platforms, Sales engagement tools

Domain Summary

Complex collection of administrative workflows managing enrollment and unenrollment in sales sequences across multiple channels (events, webinars, inbound conversion) with heavy reliance on external integrations. Current architecture shows signs of platform workarounds and redundant functionality that can be streamlined in Salesforce.

Current Problems

Rearchitecture Approach

Consolidate into unified sequence management system leveraging Salesforce's native Sales Engagement capabilities. Replace extension-heavy workarounds with declarative automation that evaluates enrollment eligibility, manages lifecycle events, and enforces compliance rules through a single framework.

Recommended Automations

Sequence Enrollment Orchestrator

Build PropertyValue
Flow API NameN/A
Flow TypeN/A
Target ObjectN/A
Execution ModeN/A
Priorityhigh
ReusableYes

Purpose: Central hub that evaluates sequence enrollment eligibility and routes contacts to appropriate sequences based on source, stage, and exclusion criteria

Trigger: Contact record update (any field that affects sequence eligibility)

Entry Criteria Formula: N/A

Logic Overview: Evaluate enrollment criteria hierarchy: 1) Check exclusion flags, 2) Validate source/channel requirements, 3) Assess lead qualification, 4) Route to appropriate sequence type, 5) Log enrollment decision

Replaces: Add to sequence (events), Add to sequence (events) - from CSM, Add to sequence (webinar), Inbound to Outbound - Email Sequence and BDR Assignment, Admin_Inbound RB2B to Outbound Sequence (BDR) (cloned)

Required Fields:

FieldPurposeUsageHubSpot SourceNet New?Migration Note
Sequence_Eligibility_Status__cControls whether contact can be enrolled in sequencesbothN/AYesConsolidates logic from multiple admin workflows
Lead_Source_Channel__cDetermines which sequence type is appropriatereadVarious source fieldsNoMap from HubSpot source tracking
Last_Sequence_Enrollment__cPrevents duplicate enrollments and manages re-enrollment timingbothN/AYesReplaces complex re-enrollment workflow

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Sequence Lifecycle Manager

Build PropertyValue
Flow API NameN/A
Flow TypeN/A
Target ObjectN/A
Execution ModeN/A
Priorityhigh
ReusableYes

Purpose: Handles unenrollment, completion, and status updates for contacts in active sequences based on outcomes and administrative rules

Trigger: Activity completion, call outcome update, or administrative flag change

Entry Criteria Formula: N/A

Logic Overview: Process lifecycle events: 1) Evaluate unenrollment triggers (call outcomes, admin flags), 2) Complete related tasks, 3) Update sequence status, 4) Apply hold/exclusion rules, 5) Log outcome reasons

Replaces: Admin_Unenroll from Sequence, Admin_Unenroll on Call Outcome, Admin_do not enroll in sequence

Required Fields:

FieldPurposeUsageHubSpot SourceNet New?Migration Note
Sequence_Hold_Reason__cTracks why sequence was paused or stoppedwritemake_holdNoEnhanced from existing hold field
Last_Call_Outcome__cDetermines sequence continuation based on call resultsreadCall outcome fieldsNoStandard call logging
Sequence_Status__cCurrent state of contact in sequence lifecyclebothN/AYesReplaces task status tracking

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

BDR Assignment and Routing

Build PropertyValue
Flow API NameN/A
Flow TypeN/A
Target ObjectN/A
Execution ModeN/A
Prioritymedium
ReusableYes

Purpose: Assigns BDRs to prospects and manages territory-based routing for outbound sequences

Trigger: Lead qualification or sequence enrollment requiring BDR assignment

Entry Criteria Formula: N/A

Logic Overview: Route based on: 1) Territory/region rules, 2) BDR capacity and specialization, 3) Account ownership, 4) Round-robin for new prospects, 5) Create assignment tasks

Replaces: ADMIN_ BDR call sequence, Inbound to Outbound - Email Sequence and BDR Assignment

Required Fields:

FieldPurposeUsageHubSpot SourceNet New?Migration Note
Assigned_BDR__cLinks contact to responsible BDRwriteOwner assignmentNoEnhanced BDR-specific assignment
BDR_Assignment_Date__cTracks when BDR assignment occurred for SLA trackingwriteN/AYesNew field for assignment tracking

Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._

Cross-Flow Interaction Model

Interaction handoffs were not provided. Add flowInteractionModel entries so build sequencing and contracts are explicit.

Migration Sequence

  1. Build Sequence Eligibility Status field and populate from existing workflows
  2. Implement Sequence Lifecycle Manager to handle unenrollment scenarios
  3. Build Sequence Enrollment Orchestrator with eligibility framework
  4. Implement BDR Assignment and Routing for territory management
  5. Migrate sequence configurations to Salesforce Sales Engagement
  6. Test and validate sequence enrollment and lifecycle automation
  7. Deactivate HubSpot workflows and extensions

Architecture Diagram

graph TD

A[Contact Update] --> B{Sequence Eligible?}

B -->|Yes| C[Enrollment Orchestrator]

B -->|No| D[Update Exclusion Status]

C --> E{Source Channel?}

E -->|Event| F[Event Sequence]

E -->|Webinar| G[Webinar Sequence]

E -->|Inbound| H[Inbound Conversion]

E -->|RB2B| I[RB2B Sequence]

F --> J[Assign BDR]

G --> J

H --> J

I --> J

K[Call Outcome] --> L[Lifecycle Manager]

M[Admin Flag] --> L

L --> N{Unenroll Needed?}

N -->|Yes| O[Complete Tasks]

N -->|No| P[Continue Sequence]

O --> Q[Update Status]

P --&gt; R[Monitor Progress]</code></pre>