Skip to main content
Multichannel outreach means coordinating communication across more than one channel in a single journey. In Sequencing V2, the currently supported channels are email and LinkedIn, so you can combine both in one workflow instead of running separate campaigns. Compared with V1 (which is mostly linear and email-first), V2 supports more custom outreach flows. You can adapt each contact path based on outcomes, choose different channel actions at different points, and build workflows that better match real engagement behavior.

​
DAG abstraction

A DAG (directed acyclic graph) is a directed graph where nodes are connected by one-way edges and no path can return to an earlier node (no cycles). In V2, this abstracts outreach into reusable workflow building blocks instead of a fixed linear sequence. At runtime, each contact moves forward through one path in that graph based on condition outcomes.
  • Root node: the single start point of every multichannel sequence graph.
  • Nodes: executable steps or evaluations in the sequence graph.
  • Condition nodes: decision points (for example, whether a contact replied within a wait period) that choose the next path.
  • Branches: routing paths between nodes.
  • Actions (Action nodes): channel operations such as send email, connect on LinkedIn, send LinkedIn message, or wait.
In execution and tree views, a path can also end when a branch has no next node (terminal end state). When you create a multichannel sequence, Salesforge automatically creates the Root node for you. If you want to see that creation flow through the public APIs, including action and condition discovery, sender-profile assignment, optional validation, enrollment, and launch, see Create a multichannel sequence. In this example, the Yes path from the replied condition is not connected to another node. It can terminate by leaving to_node_id empty on that branch.

​
Workflow building blocks

V2 workflows are assembled from catalogs of available actions and conditions.
  • Actions define what the system does next (for example email send, LinkedIn connect, LinkedIn message, or wait).
  • Condition nodes define how the workflow decides the next path after a measurable outcome.
  • Branches connect those blocks into contact journeys.
This model lets you create simple or advanced flows without changing the core sequence concept.

​
Sequence settings

Sequence settings define how the sequence behaves once the workflow structure is in place. On the public multichannel sequencing surface, the exposed settings are focused on email presentation, sender behavior, opt-out presentation, and opportunity attribution. The underlying multichannel-api service has a broader internal settings model, but the public configuration surface for sequence creation and update is centered on the settings below.

​
Tracking and message presentation

  • Open Tracking: tracks email opens for the sequence.
  • Plain-Text Emails: uses a plain-text style email presentation for the sequence.
Example: a team that wants a simpler email format may enable Plain-Text Emails, while a team measuring top-of-funnel engagement may enable Open Tracking.

​
Sender behavior and recipient copy rules

  • ESP Matching: applies provider-matching behavior for outbound email delivery.
  • CC and BCC: when enabled, the sequence can include CC and BCC recipients.
  • CC Recipients: when enabled, defines the CC recipient list.
  • BCC Recipients: when enabled, defines the BCC recipient list.
Example: a team might use BCC Recipients to archive outbound mail in a shared mailbox, or enable ESP Matching when sender-routing policy needs to stay aligned with mailbox provider behavior.

​
Compliance and opt-out behavior

  • Opt-out Text: when enabled, defines the wording shown for the opt-out text.
  • Opt-out Link: when enabled, adds an opt-out link to the message.
  • Opt-out Link Text: when enabled, defines the label shown for the opt-out link.
Example: a sequence can show a short custom sentence such as “If this is not relevant, feel free to opt out” and pair it with a clearer link label such as “Unsubscribe from this sequence”.

​
Opportunity tracking behavior

  • Opportunity Tracking: applies opportunity-oriented attribution to the sequence.
  • Opportunity Value: when enabled, assigns a value used for opportunity tracking.
Example: if a team wants sequence outcomes to carry a nominal business value, it can enable Opportunity Tracking and assign an Opportunity Value for reporting consistency.

​
Update model

V2 settings updates are partial: you can update only the fields you want to change while leaving other settings as they are. In practice, this means you can adjust one part of sequence behavior, such as opt-out text or CC/BCC handling, without resubmitting the full settings object.

​
Operational context

​
Scheduling and timezone

Each sequence runs within schedule windows and a sequence timezone. This controls when sends are allowed, independent of workflow logic.

​
Sender profiles in multichannel execution

Sender profiles are required execution identities for multichannel workflows. They align mailbox and LinkedIn sender context so channel actions can run consistently. See Sender Profile for the concept overview.

​
Enrollment and validation flow

Contacts are enrolled into the sequence, and validation can be used as a readiness step before active outreach. This helps maintain quality before contacts enter live execution. For a concrete public API walkthrough of optional validation and multiple enrollment patterns, see Create a multichannel sequence.

​
Sequence lifecycle

V2 sequences use a small lifecycle model that describes whether the sequence is being prepared, running, temporarily stopped, or finished.
  • Draft: the sequence is still being configured. This is the planning state for workflow structure, schedules, sender assignment, and settings.
  • Active: the sequence is live and can continue processing enrolled contacts according to its workflow, schedule, and sender configuration.
  • Paused: the sequence remains defined, but execution is temporarily stopped until it is resumed.
  • Completed: the sequence lifecycle has been finished and is no longer running as an active sequence.

​
Contact lifecycle outcomes

Each enrolled contact also has its own lifecycle status. This is more granular than the sequence lifecycle because contacts can finish for different reasons even while the overall sequence remains active. In the current model, Active and Paused are in-progress states. The remaining statuses are treated as terminal outcomes.
  • Active: the contact is currently enrolled and can continue moving through the workflow.
  • Paused: the contact is temporarily stopped and is not progressing until reactivated.
  • Completed: the contact reached the end of its intended path without another terminating outcome taking precedence.
  • Failed: the contact could not continue because of an execution or processing failure.
  • Replied: the contact replied, so the sequence stops further automated progression for that contact.
  • Out of Office: an out-of-office response was detected and the contact is moved into that outcome state.
  • Unsubscribed: the contact opted out and should no longer receive sequence outreach.
  • DNC: the contact is marked do-not-contact and is not eligible for further outreach in the sequence.
  • Bounced: an email delivery bounced, so the contact is moved into a delivery-failure outcome.
  • Bounce Shield: the contact was stopped by bounce-protection logic intended to reduce delivery risk.

​
Practical implementation path

  1. Define the outreach goal and the main positive/negative outcomes.
  2. Create the sequence, configure timezone and schedule windows.
  3. Add action nodes and condition nodes.
  4. Connect branch paths for positive and fallback outcomes.
  5. Assign sender profiles and enroll contacts.
  6. Launch and monitor outcomes by lifecycle state.