Outreach · Weaves
Multichannel sequences that react.
A Weave decides who gets what, when, and what happens after a reply, a call or a signal. Email, calls, LinkedIn and checks on one map.
The problem and how Workloom solves it
The problem
A fixed cadence keeps going after the reply.
Most sequences only know how to stop. They email someone who booked a demo yesterday, or call someone who asked to be left alone.
With Workloom
Every step knows what happened.
A Weave branches on replies, calls and signals, respects one contact limit across all your Weaves, and hands decisions it isn’t sure of to a person.
How it works
Weaves, step by step.
Describe it, or build it
Write the play in a sentence and Wren drafts the map, or build it step by step. Try it on your list before it goes live.
Drafted by WrenEmail logistics VPs who are hiring SDRs, call two days later, then a LinkedIn note.
Checks before contact
A step can check first: verify the email, confirm the person still works there, or look for a job change, new leader, hiring or funding.
Check · still at companyLeo ParkconfirmedNextEmail · day 0One limit across every Weave
Touches per week are counted across all Weaves, and quiet hours follow the prospect’s time zone. A held step waits; it never skips.
Contact policyTouches per week3Quiet hours20:00 to 08:00 localReplies routed
Interested opens a deal, out of office waits for their return, and unsubscribe always stops. A reply Wren isn’t sure about goes to a person to decide.
Reply · Priya NairRead asInterestedThenDeal opened · owner Sam
Questions
The questions that come up on every demo.
What if someone is in two Weaves?
Do checks cost credits?
Can a partner operate a Weave for us?
Related