Sales Sequence Management
Administrative workflows controlling enrollment, unenrollment, and routing to sales sequences
| Metric | Value |
|---|---|
| Workflows | 10 |
| Priority | high |
| Grouping Confidence | 90% — All workflows focus on sequence lifecycle management with clear administrative patterns |
| Consolidation | Create unified sequence management with enrollment criteria evaluation and compliance-based unenrollment rules |
Workflows in this Group
| Workflow | Trigger | Outcome | Type | Complexity |
|---|---|---|---|---|
| Add to sequence (events) | Event attendee contact meets criteria for outbound sequence | Enroll contact in automated outbound sequence | Routing | medium |
| Add to sequence (events) - from CSM | Customer Success Manager identifies a contact who should be enrolled in an events-related sales sequence | Contact is automatically enrolled in a predefined sales sequence for event-related outreach | Routing | low |
| Add to sequence (webinar) | Contact registers for or shows interest in a webinar and should receive follow-up sales outreach | Contact is enrolled in a webinar-specific sales sequence for nurturing | Routing | low |
| Admin_Unenroll from Sequence | Administrator or system determines a contact should be removed from active sales sequences | Contact is unenrolled from sequences and related tasks are marked complete | Enforcement | medium |
| Admin_Unenroll on Call Outcome | Call outcome indicates contact should be removed from active sales sequences | Contact is unenrolled from sequences, tasks marked complete, and branching logic applied based on email campaign | Enforcement | high |
| Admin_do not enroll in sequence | Administrator identifies contacts that should be prevented from sequence enrollment | Contact is blocked from sequence enrollment and related tasks are completed | Enforcement | medium |
| ADMIN_ BDR call sequence | Contact reaches a stage where BDR should initiate a calling sequence | BDR receives structured guidance or automation for systematic calling approach | Enforcement | medium |
| ADMIN_add to re-enroll list | Contact needs to be added to a re-enrollment list for workflow management | Contact is systematically added to and removed from re-enrollment management lists | Enforcement | medium |
| Inbound to Outbound - Email Sequence and BDR Assignment | Inbound lead needs to be converted to outbound prospecting approach | Assign BDR and enroll prospect in outbound email sequence | Routing | medium |
| Admin_Inbound RB2B to Outbound Sequence (BDR) (cloned) | RB2B (Reveal Bot to Business) identified prospect needs outbound follow-up | Enroll RB2B-sourced prospects in BDR outbound sequence | Routing | low |
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
- Heavy reliance on extensions suggests HubSpot sequence limitations requiring external tools
- Multiple similar workflows (Add to sequence events vs events from CSM) indicate poor consolidation
- Re-enrollment workflow using delays and extensions is a clear platform workaround
- Administrative unenrollment scattered across multiple workflows instead of unified rules
- No clear sequence eligibility framework - enrollment appears ad-hoc
- Task status updates mixed with sequence management creates maintenance complexity
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 Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
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:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Sequence_Eligibility_Status__c | Controls whether contact can be enrolled in sequences | both | N/A | Yes | Consolidates logic from multiple admin workflows |
| Lead_Source_Channel__c | Determines which sequence type is appropriate | read | Various source fields | No | Map from HubSpot source tracking |
| Last_Sequence_Enrollment__c | Prevents duplicate enrollments and manages re-enrollment timing | both | N/A | Yes | Replaces complex re-enrollment workflow |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
Sequence Lifecycle Manager
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | high |
| Reusable | Yes |
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:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Sequence_Hold_Reason__c | Tracks why sequence was paused or stopped | write | make_hold | No | Enhanced from existing hold field |
| Last_Call_Outcome__c | Determines sequence continuation based on call results | read | Call outcome fields | No | Standard call logging |
| Sequence_Status__c | Current state of contact in sequence lifecycle | both | N/A | Yes | Replaces task status tracking |
Interactions With Other Recommended Automations: _Not documented. This should be populated for multi-flow domains._
BDR Assignment and Routing
| Build Property | Value |
|---|---|
| Flow API Name | N/A |
| Flow Type | N/A |
| Target Object | N/A |
| Execution Mode | N/A |
| Priority | medium |
| Reusable | Yes |
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:
| Field | Purpose | Usage | HubSpot Source | Net New? | Migration Note |
|---|---|---|---|---|---|
| Assigned_BDR__c | Links contact to responsible BDR | write | Owner assignment | No | Enhanced BDR-specific assignment |
| BDR_Assignment_Date__c | Tracks when BDR assignment occurred for SLA tracking | write | N/A | Yes | New 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
- Build Sequence Eligibility Status field and populate from existing workflows
- Implement Sequence Lifecycle Manager to handle unenrollment scenarios
- Build Sequence Enrollment Orchestrator with eligibility framework
- Implement BDR Assignment and Routing for territory management
- Migrate sequence configurations to Salesforce Sales Engagement
- Test and validate sequence enrollment and lifecycle automation
- 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 --> R[Monitor Progress]</code></pre>