Outreach
Personalised follow-up sequences in Funnel. Each message is written only from what Venom knows about the person, sent by email or WhatsApp Business or handed to you to send from your own phone, and stopped the moment they reply.
Outreach is a tab in Venom Funnel for following up with people in a planned way. You build a sequence: a few steps, each on a channel, with a wait between them and a short brief of what the step should say. Then you enroll people in it, one at a time or a whole event's worth. For each person, Venom drafts every message from the facts it has on file, sends the ones a channel allows it to send, queues the rest for you to send with one tap, and stops as soon as the person replies.
An example: after a conference, select the 20 people you met there and enroll them in "Post-event follow-up". Each gets a first email that mentions where and when you met and what you talked about. If there's no reply after 4 business days, a WhatsApp nudge follows. A week later, a last email in the same thread. A reply on any channel ends that person's sequence and logs the reply in People.
Outreach is the Outreach tab in Funnel's top bar. Everything on this page also works through the API and the MCP tools.
In Funnel
The sequence list (/funnel/outreach) shows each of your sequences with its purpose, status and steps, and its
numbers: enrolled, active, replied (as a share of the people contacted), meetings, opted out and bounced. A sequence
with drafts waiting says how many. Above the list, today's work: drafts to approve and steps to send yourself. An org
admin also sees other members' sequences and their numbers, but not their drafts.
Start with New sequence, or from one of three templates:
| Template | Steps |
|---|---|
| Post-event follow-up | an email on day 0, a WhatsApp nudge you send on day 4, a last email in the same thread on day 10 |
| Cold intro | an email on day 0, then replies in the same thread on days 3 and 8 |
| Catch-up | one WhatsApp message you send yourself |
The builder (/funnel/outreach/{id}, and /funnel/outreach/new for a new one) lists the steps top to bottom,
each with the day it goes out counted from enrolling. For each step you pick:
- the channel. The picker says which channels are connected in Comms, which are not connected yet (nothing is sent on those until they are), and which you send yourself;
- the wait in days after the previous step, and whether it counts business days only;
- the brief: what the step should say;
- for email, a subject hint and whether to reply in the previous email's thread;
- for WhatsApp, an approved template from Comms (a cold first message needs one).
Drag a step to move it, or focus it and press Alt+↑ or Alt+↓. The arrow buttons do the same. Below the steps are
the sequence's settings: approval, tone, the send window (weekdays and hours), the daily cap, and what stops it besides
a reply (a booked meeting, or the deal reaching stages you tick). Fields with a problem say what is wrong when you save,
with the same rules the server applies.
Save keeps it as it is, Activate starts it, Pause holds every draft and send, and Archive stops everyone in it for good. Once it is saved, Preview drafts each saved step for a person you pick, with the facts it used; it saves and sends nothing, and counts toward the daily draft limit. The enrollments table at the bottom shows each person's status, step, next send and stop reason, with pause, resume and stop.
The queue (/funnel/outreach/queue) shows one draft at a time: the person, the sequence and step, the channel and
when it is due, the facts the draft used as chips (hover or focus one to see where it came from), and the subject and
body. Click the text, or press e, to edit it. A draft marked plain is the fallback built from the brief because
the model's drafts failed the facts check: read it before you approve.
| Key | What it does |
|---|---|
a |
approve (with your edits) |
e |
edit |
s |
skip this step; the sequence moves on |
j, k |
next and previous draft |
x |
stop this person's sequence |
The To send yourself tab of the queue (/funnel/outreach/queue?kind=manual) has the same steps as People's Today,
with the same buttons (below): open your app with the text, copy it, mark it sent, or snooze it a day. A snoozed step
moves to the end and says until when. The queue works at phone width.
Enrolling (/funnel/outreach/enroll) takes a list of people into one of your sequences. Open it from:
- the People list: select people (
xor the checkboxes) and choose Add to sequence; - an event's page in People: Follow up with N people takes everyone you met there (the end of that event's debrief has the same link);
- a person's page: Add to sequence in the Outreach section, which also shows the sequences they are in;
- a deal in Funnel: Start sequence enrolls the deal's people with the deal, so the deal reaching a stop stage, or being won or lost, ends it.
Pick the sequence and the consent basis. From an event the basis starts on "Met in person"; otherwise you choose one, and bases that don't allow the sequence's channels are marked. Before you confirm, it lists how many will be enrolled and who will be skipped and why: opted out, a basis that doesn't allow a channel, no address for a channel, already in the sequence, or not someone you can see. You can add more people by name.
Badges. A deal card on the board, the deal's page and a person's page show a small badge for each of your live sequences with them, such as "Step 2 of 3, next Tue".
Channels
| Channel | How it is sent | Automated |
|---|---|---|
| From your own mailbox (an app password first; Google and Microsoft sign-in later) | Yes | |
| WhatsApp Business | Through Comms from your business number; a cold first message uses an approved template | Yes |
| SMS | Through Comms | Yes |
| Personal Telegram | Your own account, through the Venom daemon on your machine; low volume, approved drafts only | Yes, limited |
| Personal WhatsApp, Telegram, LinkedIn, email | Tap-to-send: the draft waits on Today, one tap opens your app with the text filled in | No, never |
| Task | A to-do for you, such as a call | No |
Venom never runs an unofficial WhatsApp client and never automates or scrapes LinkedIn. Both break those services' terms and can get your personal account banned. LinkedIn details come only from what you gave People yourself, such as screenshots or your LinkedIn data export.
A sequence
| Setting | What it does |
|---|---|
| Purpose | cold (first contact), followup (after meeting someone) or catchup (keeping a relationship warm) |
| Approval | every (the default: you approve each draft), first (only each person's first message), none, or timed (each draft waits in your queue, then sends by itself; see Timed approval) |
| Hours before it sends | timed only: how long a draft waits before it sends by itself, 1 to 168 hours (a week). Default: 24 |
| Enroll automatically | Off by default. Enrolls people who get a tag or match a saved Reach view; see Enrolling automatically |
| Tone | A line on how the messages should sound, up to 300 characters |
| Stop on | A reply always stops. Optionally a booked meeting, or the deal reaching a stage you pick |
| Send window | The weekdays and hours messages may go out, in the recipient's time zone (yours when theirs is unknown). Default: Monday to Friday, 09:00 to 17:00 |
| Daily cap | At most this many sends a day for the sequence. Default: 40 |
A sequence has 1 to 12 steps. Each step has a channel, a wait in days after the previous step (business days by default), a brief of up to 1,000 characters, and for email an optional subject hint and the choice to reply in the previous email's thread. The first step can't be a thread reply.
Send times are spread over up to 45 minutes after the window opens, so 20 people don't all get a message in the same minute. The spread is fixed per person, so a schedule doesn't change when it is recalculated.
Timed approval
With approval timed, each draft on an automated channel (email, SMS, WhatsApp, Telegram) waits in your approval queue
with a time: "Sends by itself in 5 hours". The time is when the draft was ready plus the sequence's hours (24 by
default). Until then you can approve it early, edit it and approve it, skip it, or press Hold. Hold removes the
timer: the draft stays in your queue and waits for you like any every draft. Tap-to-send steps and tasks are never
sent by themselves.
When the time passes, the sweep approves the draft for you (the audit log records the approval as
system:outreach:timed, with the run, enrollment and sequence ids only) and it goes out on the same path as any
approved step: inside the send window, under the daily cap, after the stop signals and Comms' rules. If you change the
sequence away from timed, waiting drafts lose their timers and wait for you. Drafts made before you switched a
sequence to timed have no timer.
WhatsApp outside the 24-hour window. WhatsApp allows a free-form message only within 24 hours of the person's
last message to you; outside it, only an approved template. A WhatsApp step with no template, to someone who hasn't
written in the last 24 hours, is never sent by itself, under timed or none: it waits in your queue with "Needs an
approved template or a reply from them first". Pick a template for the step, or approve it yourself. Note that a reply
from them also stops the sequence (a reply always stops it), so in practice a step like this goes out only when you
approve it or give it a template.
Enrolling automatically
A sequence can enroll people by itself. In the builder, Enroll automatically takes:
- Source: people with a tag in People, or a saved Reach view of yours (People → Reach). The view is run without a model call, the same way Reach's own list runs it.
- At most per day: new enrollments a day, 1 to 100. Default: 10. The day is your org's day in Comms' time zone.
- Only people added after it is turned on: on by default. Turned off, people who already match are enrolled too, a few a day.
- Consent basis: recorded on each enrollment, and it has to allow every step's channel.
Every few minutes the sweep checks each active rule and enrolls matches with the same checks as enrolling them
yourself: people you can see in People, their consent basis, opt-outs, an address for each step's channel. Someone who
is or ever was in the sequence is never enrolled again, and nothing is enrolled while the sequence is paused, a draft or
archived. Only the sequence's owner's rule runs, as the owner. Each enrollment is marked auto in the builder's
list and gets an audit row (outreach.auto_enrolled, actor system:outreach). The card shows how many it enrolled
today. Turning the rule off keeps its settings; turning it on again or changing its source starts "only people added
after" from that moment. If the saved view is deleted, the rule turns itself off.
Sharing a sequence with a team
A sequence is yours alone until you pick a team under Shared with in the builder. The members of that team, and of the teams above it, then see the sequence in their list ("shared with a team") and can enroll their own people in it. A member who is only in a subteam or a sibling team can't. You pick one of your own teams or a subteam under one.
- Each member runs their own enrollments. The member who enrolls someone owns that enrollment: the drafts are written from what they know about the person, wait in their queue, and only they approve, pause or stop them.
- Messages go out as the member who enrolled. Each enrollment sends from the Comms sender its member named for
the channel when enrolling through the API or MCP (
sender), or else the org's default sender for the channel. A Telegram step (your account) goes from the enrolling member's own Telegram, through their own daemon. It never sends from the sequence owner's sender or as the owner. - Only the handles you can see. A contact someone else owns and shared with you shows you none of their handles
in People, and Outreach follows the same rule. Your enrollment reaches the person only on an address you already
have on a contact of your own (the same email, number, Telegram or LinkedIn; a phone and a WhatsApp number with the
same digits count as one). It never uses the owner's private handles, even when they come first. If no address you
can see fits a step's channel, enrolling skips the person with
no_address. If your own copy is gone by the time a step is due, the step is skipped and the reason is shown on it ("no phone address you can see for this person"). The sequence then moves on. Tap-to-send buttons on Today and in the queue only show addresses you can see. Two things still check every handle on the contact, because all they can do is hold a message back: an opt-out on any of the person's numbers keeps you from enrolling them, and a reply from any of their addresses stops your enrollment. - Only the owner changes it. The steps, settings and team stay the owner's. A teammate sees the builder read-only and an enrollments table with only their own rows actionable.
- Unsharing (picking Not shared) hides it from the team at once. Enrollments already running keep going, under the members who made them.
Email steps go out from your own mailbox, connected in Settings → Comms → Mailboxes with an app password (see Email from your own mailbox). What that means for a sequence:
- From you. The email comes from your address with your name and signature, and replies land in your inbox. No tracking pixel, no rewritten links.
- Paced. One email at a time, 2 to 7 minutes apart. A new mailbox starts at 10 a day and adds 5 a day up to its cap (40 by default), on top of the sequence's own daily cap.
- Threads. A step set to reply in the previous email's thread is sent with
In-Reply-To,ReferencesandRe:. - Replies stop it. Venom reads the mailbox's new mail headers every few minutes. A reply to one of its emails, or mail from the address of someone enrolled, is a reply and stops that person's sequence. Out-of-office replies don't count. Other mail is never read past its headers.
- Bounces stop it. A bounce marks the person's email address as bad and stops their sequence.
- Unsubscribe. Every email ends with "Don't want these? Unsubscribe." and carries the one-click unsubscribe headers mail apps show. Unsubscribing adds an opt-out, which stops all outreach to that person.
Safety rules
- Facts only. A draft may use only facts on file in People and Funnel, and the facts it used are shown next to every draft.
- Approval first. Drafts wait for your approval unless you change the sequence's setting. With
timed, they wait for the sequence's hours and then send by themselves unless you hold them. - A reply stops it. A reply on any channel stops that person's sequence, including on a manual channel once you mark it.
- Opt-outs are final. An opt-out on any channel stops all outreach to that person, in every sequence, and nothing overrides it.
- A bounce stops it. An email that bounces stops that person's sequence.
- A consent basis for everyone. When you enroll people, you record why you may contact them: met in person, introduced, inbound, existing customer, legitimate interest, or consented. Legitimate interest covers business email and a LinkedIn message you send yourself, nothing else. A cold message on WhatsApp, SMS or Telegram needs met in person, introduced, inbound or consented. People whose basis doesn't allow a sequence's channels are skipped, with the reason.
- Only addresses you can see. Outreach sends only to handles the enrolling member can see in People: every handle of a contact they own, and for a contact shared with them, only the addresses they hold on a contact of their own (see Sharing a sequence with a team).
- Private drafts. Drafts and the facts behind them are visible only to the member who enrolled the person (the sequence's owner, or a teammate on a shared sequence), the same as the notes in People they come from.
- Nothing until you connect it. Venom doesn't touch a mailbox, a Telegram account or a messaging provider until you connect it.
How drafts are written
Each message is written for one person from the facts Venom has on file, and only from those. The facts it used are listed next to the draft, so you can check it at a glance before you approve it.
The facts. Venom reads them as the member who enrolled the person (the sequence's owner, unless a teammate enrolled them in a shared sequence), with People's usual visibility:
| From | Facts |
|---|---|
| People | Name, first name, role, company, location, tags |
| People, your own contacts only | How you met (a linked person reads as their name), the event you met at with its dates and place, who introduced you, your last 5 interactions with their dates, and the context card |
| Funnel | The deal's title, stage, products and newest to-do (when the person was enrolled with a deal) |
| You | Your name, role, company and signature |
Notes in People are never used. For a person someone else owns that you can see, only the first row applies, as in
People itself. Your role and company come from the companies you listed for yourself in People. Your name and
signature come from the org's settings (settings.outreach.senders.<your user id> with name and signature); without a
name, the part of your email address before the @ is used.
The prompt. The model gets the step's brief, the sequence's tone, the channel's limits, where the step falls (the first message, a follow-up, or the last one, which says kindly that it's the last note), the earlier messages to this person so a follow-up doesn't repeat them, and the facts list. It answers with the subject, the body and the facts it used.
| Channel | Limits |
|---|---|
| Email (sent or tap-to-send) | A subject up to 60 characters (none needed for a reply in the thread), a body of 40 to 150 words |
| WhatsApp, Telegram | Up to 500 characters, no subject |
| SMS | Up to 320 characters, no subject |
| LinkedIn note | Up to 300 characters |
| Task | One line, up to 200 characters |
For a WhatsApp step with an approved template, the model fills the template's variables from the facts instead of writing free text.
The checks. Before a draft reaches you, Venom checks:
- the answer's shape and the channel's limits;
- that every fact it says it used exists;
- that no placeholder is left in, such as
[Name],{{company}}or<company>; - the same things People's follow-up drafts refuse: lists, markdown, stock openings and sales language;
- the facts check: every capitalised name, number, month and link in the subject, the body and each template variable must appear in a fact, in your profile, or in your own words (the brief, the tone and the earlier messages). Greetings, weekdays and everyday words are allowed.
If the answer fails, the model gets one more try with the problems listed. If that fails too, the draft is a plain message built from the brief, their first name and your name, marked plain so you edit it before sending.
Booking links. When Venom Calendar adds a booking link for the person, a draft may write {{booking_link}} and the
link goes there. Without a link on file, {{booking_link}} is a placeholder and the draft is refused.
Cost. Drafts go through your org's own gear (its summary model, else its main model) with an internal key named
"Venom Outreach", so they show in Requests like any other call. Each org has a daily limit for drafts,
settings.outreach.ai_cap_usd, $2 by default, counted from that key's spend today (UTC). At the limit, drafts wait
until the next day and say why. Previews in the sequence builder count too.
How a sequence runs
Every minute the cloud's sweep works through what is due, for up to 4 seconds; anything left waits for the next minute.
- Enroll. Each person gets their first step's time from the step's wait, moved into the send window. People are
skipped, with the reason, when you can't see them in People (
not_found), they are already in the sequence (already_enrolled), they opted out on any channel (opted_out), their consent basis doesn't allow one of the sequence's channels (no_consent), or they have no address for a step's channel (no_address). - Draft. When a step is due, it is drafted from the facts on file.
- Approve. With approval
every, each draft waits in your approval queue; withfirst, only the first step does; withnone, drafts go straight out; withtimed, each draft waits with a time and sends by itself once it passes, unless you hold it. Tap-to-send steps and tasks never need approval: they wait on your manual queue (Today) until you mark them sent. - Send. An approved step goes out through Comms inside the send window and under the daily cap, which counts your sends across your sequences per day. Steps over the cap wait for the next day's window. Comms' quiet hours and opt-outs still apply on top. Each sent message is logged on the person's timeline in People (the first 280 characters).
- Next step. The next step's time is counted from the send, in the recipient's time zone (guessed from their phone number, else your org's default zone in Comms).
A message is sent at most once: Comms keeps it under the key outreach:<run id>, so a sweep that crashes after the send
finds the message instead of sending it again.
What stops a person's sequence:
| Signal | Stop reason |
|---|---|
| A message from them on any channel Comms receives (WhatsApp, SMS, Telegram), matched to their People handles | reply (the reply is logged in People) |
| STOP, or any opt-out | opted_out, in every sequence they are in |
| A message that bounced or was undeliverable | bounced |
| The deal reaching a stage in the sequence's stop list, or won or lost | deal_stage |
| A meeting booked with them, when the sequence stops on meetings | meeting |
| You stop it, or archive the sequence | stopped, archived |
You can also pause and resume one person, skip a step (the sequence moves on), and mark a reply that came on a manual channel.
Steps you send yourself
Personal WhatsApp, LinkedIn, personal Telegram and email without a connected mailbox are never automated. When one of these steps comes due, Venom writes the draft and puts it on People's Today page, in an Outreach section above your follow-ups. Each card shows the person, why it is there ("Post-event follow-up, step 2 of 3"), the facts the draft used and the message, which you can edit.
| Step | The button | What it does |
|---|---|---|
opens wa.me with the text filled in, from their WhatsApp number or phone |
||
| Telegram | Telegram | copies the text and opens their chat (Telegram can't prefill a message to a user) |
| copies the text and opens the profile you gave People. A message over 300 characters gets a warning, because that is the limit for a connection note | ||
| opens your mail app with the subject and body filled in | ||
| Any | Copy | copies the text and nothing else |
Pressing an app button marks the step as sent: Venom logs your message in People as an outgoing interaction, with the text as you edited it, and schedules the next step. If the person has no handle for the channel, the button is greyed out with the reason; copy the text, send it where you reach them and press Mark sent. Done does the same for a task step.
- They replied records a reply you saw in your own app. It stops the person's sequence and logs their reply.
- Skip drops the step and the sequence moves on.
- Snooze hides the step until tomorrow.
- With a card focused,
jandkmove between cards,dedits the draft,xmarks it sent andssnoozes it.
A reply you log in People by any route (the app, an MCP tool, Telegram capture) also stops the person's sequences, as long as it is from them: a message, email or call logged as "from them" or "both", or a meeting. Something you logged as outgoing, and a private note, never stop one. Venom never opens an app or sends anything by itself: only your tap does.
Catch-ups and event follow-ups
Keeping in touch with people you already know runs on the same engine as a sales sequence.
Catch-ups. Make a sequence with the purpose catch-up: often a single step, such as a WhatsApp message you send yourself. Then, on a person's page in People, under Keep warm, set When the cadence comes due to that sequence. The choices are:
| Choice | When their cadence comes due |
|---|---|
| Remind me on Today | the plain keep-warm reminder, as before |
| Org default | the org's default catch-up sequence, if one is set (below) |
| Catch-up: name | one of your own catch-up sequences |
The cadence is the one from keep-warm: the person's own cadence, else their circle's. When it comes due, Venom enrolls the person once for that due date, however often the sweep runs. The draft gets one more fact: how long since you last talked and what about, for example "It's been 6 weeks since you last talked (28 September 2026), about: the pilot in Jakarta". A step you send yourself lands on Today like any other Outreach step, and while the person is in a catch-up, the keep-warm picker leaves them out so they don't show up twice. The Draft a follow-up button on the panel still works as before.
When the step is done (you tap it on Today, or Venom sends it), or the person replies, People logs it as an interaction. That moves their last touch, so the cadence starts again from there. A reply also ends the enrollment, as in every sequence. If enrolling would skip the person (no handle for a step's channel, an opt-out, or no consent for that channel), the panel says why, and Today shows the plain reminder instead.
Venom records the consent basis it can show: met in person if you met at an event or logged a meeting, else inbound if they wrote to you first, else legitimate interest, which allows only email and LinkedIn steps.
The org default. An org admin picks it in Funnel, Settings, Catch-ups (settings.outreach.default_catchup_sequence).
People with no choice of their own use it. A sequence belongs to one member, so the default reaches that member's people.
Other members pick a catch-up sequence of their own, or keep the reminder.
Event follow-ups. Follow up with N people, on an event's page in People and at the end of its debrief, opens
enrolling (/funnel/outreach/enroll?event={id}) with everyone you met there selected and the consent basis met in
person; add &sequence={id} to pick the sequence too. funnel_outreach_event_preview gives the same list to an agent.
The event reaches every draft as a fact ("Met at: HK Fintech Fest") through the person's met-at event or an interaction
logged there. Each person shows why enrolling would skip them. Give it a sequence to check that
sequence's channels; without one, a person with no handle at all is marked no_address.
The MCP tools are funnel_outreach_catchup_get and funnel_outreach_catchup_set (a person's choice: default,
reminder or a sequence id) and funnel_outreach_event_preview (event, optional sequence). Setting the org default
is for an admin in the app. Their REST twins are GET and PUT /api/v1/funnel/outreach/catchups/{person} and
GET /api/v1/funnel/outreach/events/{event}.
API and MCP
The REST API takes an org API key: a member's own key acts as that member, a team key acts for the org. Its OpenAPI
document is services/nodejs-cloud/contracts/outreach-openapi.yaml (every route below, with the request and answer
shapes from contracts/outreach-v1.schema.json).
| Route | What |
|---|---|
GET, POST /v1/outreach/sequences |
list sequences (yours and those shared with your teams), create one (teamId: a team id or key to share it with) |
GET, PUT, DELETE /v1/outreach/sequences/{id} |
read, replace or archive one |
GET /v1/outreach/enrollments?sequence_id=, POST /v1/outreach/enrollments |
list a sequence's enrollments, enroll people (sequenceId, personIds, dealId, consentBasis, and sender: {channel: senderId} to send from your own Comms senders) |
POST /v1/outreach/enrollments/{id} |
pause, resume or stop one enrollment (action) |
GET /v1/outreach/queue?kind=approval or kind=manual |
drafts to approve, or steps to send yourself |
POST /v1/outreach/runs/{id}/approve, POST /v1/outreach/runs/{id}/skip, POST /v1/outreach/runs/{id}/tapped |
approve a draft (optionally with an edited subject or body), skip a step, mark a tap-to-send step sent |
POST /v1/outreach/runs/{id}/hold |
hold a timed draft: it loses its timer and waits for you |
A sequence's body takes approvalDelayHours and autoEnroll ({on, source: "tag" | "view", ref, dailyMax, onlyNew, consentBasis}, or null to turn the rule off and keep its settings). A run in the queue carries autoSendAt,
heldAt and waitReason (whatsapp_template).
The MCP tools are under Funnel (/workspace/mcp/funnel, scopes funnel:read and funnel:write):
funnel_outreach_sequence_list, funnel_outreach_sequence_get, funnel_outreach_sequence_save,
funnel_outreach_person_enroll (with dry_run it only lists who would be enrolled and who skipped; sender picks your own Comms sender per channel), funnel_outreach_sequence_save takes team to share a sequence, approval_delay_hours and auto_enroll, funnel_outreach_enrollment_list (a sequence's enrollments, newest first, paged with cursor and limit; in a sequence shared with your team, only your own), funnel_outreach_enrollment_set, funnel_outreach_queue_list,
funnel_outreach_run_approve, funnel_outreach_run_hold (hold a timed draft), funnel_outreach_run_skip, funnel_outreach_run_mark_sent (the tapped route's twin: you sent a tap-to-send step or did a task yourself, optionally naming the channel you used; Venom sends nothing) and funnel_outreach_draft_preview (one step drafted for one person, as the builder's preview), with REST twins under /api/v1/funnel/outreach. An agent
can't approve a draft unless the sequence sends without approval, and API keys count as agents for this rule: a person
approves in Funnel.
For builders
The wire types are in services/nodejs-cloud/contracts/outreach.ts, with a JSON Schema in contracts/outreach-v1.schema.json
and examples in contracts/fixtures/outreach. The rules above are pure functions in lib/outreach/model.ts:
transition, nextDue, channelKind, consentAllows, validateSequence and sequenceStats. The drafter is
lib/outreach/draft.ts (registered with setOutreachDrafter when the module loads), its facts lib/outreach/facts.ts
(factsFor, and registerFactSource for other products' facts) and its checks lib/outreach/draft-model.ts. Tests
swap the model with setOutreachModel. The engine is lib/outreach/engine.ts (the sweep, applyEvent, the stop signals) with the data layer in
lib/outreach/index.ts; other products call onInbound, onDealStage, onInteraction and onMeetingBooked. The design is ADR 0070.