OUTBOUND CONTROL

Every prospect gets one thread, one pipeline, and one campaign state.

Your sequence tool, inbox and pipeline keep breaking the handoff between steps.

Outbound breaks when each tool owns only one handoff. Workloom keeps sequences, channels, testing and each prospect's pipeline together. The mechanics sit on infrastructure Workloom owns. Composition methods are covered in [voice] and [ai]. [Platform] keeps campaign state visible. Replies stay inside original threads and can move a prospect forward without manual stage changes.

threads
original thread per prospect reply headers carried
composition
four writing methods personalized to templated
testing
sequence and step A/B winner promoted
pre-flight
suppression rules run projection checked
pipeline
reply-driven movement campaign switch
ONE THREAD

One thread per prospect

Keep the message, channel and prospect state tied together.

A campaign can run as tiers, each with its own sequence, or as one flat sequence. The four composition methods run from fully personalized through templated with a written opener. The [voice] and [ai] pages cover the inputs behind that composition.

Follow-ups always reply inside the original thread. They carry the reply headers and the provider thread id, so the next message belongs to the conversation that started it. Sending infrastructure is part of the system, not a handoff to another vendor. See the underlying [infrastructure].

Fig 1  ·  enrollment to booked meeting flow
ENROLL
COMPOSE
SEND
REPLY
TRIAGE
PIPELINE
MEETING
TESTING

Testing that actually concludes

A test should pick a winner, not become permanent campaign furniture.

A/B testing works at the sequence level and per step. Once the sample is big enough to mean something, the winner gets promoted. That keeps the decision attached to the place where the message runs.

Before launch, suppression rules, a 30-day send projection and an eight-category pre-flight run. The campaign doesn't start until those checks have had their turn.

Fig 2  ·  the channels in one outbound stack
EmailFrom mailboxes Workloom provisioned and warmed
PhoneNumbers Workloom holds, dialed through our own dialer
LinkedInConnection requests and messages
WhatsAppThreaded alongside every other channel
TelegramThreaded alongside every other channel
PIPELINE

The pipeline moves itself

Replies can change a prospect's place without another manual handoff.

When a prospect replies, the prospect moves along the pipeline on its own. That behavior is controlled per campaign, so you can turn it off when a team needs to review or manage movement manually.

Sequences, channels, tests and pipeline state remain in one campaign view. The [platform] shows the path from enrollment through the next stage, without forcing the operator to reconcile separate tools.

Fig 3  ·  channel coverage by prospect status
EMAILOWNED INFRASTRUCTURE
PHONEOWNED NUMBERS
LINKEDINCONNECTED
WHATSAPPCONNECTED
TELEGRAMCONNECTED
Questions

What operators ask first

Can a campaign use tiers instead of one flat sequence?

Yes. Campaigns can run as tiers with their own sequences or as a single flat sequence.

Where does A/B testing run?

A/B testing runs at the sequence level and per step. A winner is promoted once the sample is big enough to mean something.

Can replies move prospects automatically?

Yes. Replies move prospects along the pipeline on their own. A per-campaign switch turns that behavior off.

See the outbound loop

See how one system handles enrollment, threads, testing and pipeline movement.

Book a call