Outreach touch 2

What it does

The follow-up, for rows touch 1 reached on an earlier day. 68% of positive replies arrive after this one.

It runs against one profile, through that profile's own proxy and with its own cookies — so the pages load the way that account's owner would see them. It opens no page at all, which means it can be run against a profile whose session you would rather not disturb.

The 14 steps

The real tree, read out of the pack the launcher ships. Indentation is nesting: the steps under a loop run once per row, and the ones under a branch run only when the condition above them holds. Every {{…}} is a value filled in at run time — from the row being walked, from a setting on the run, or from the profile itself.

Each of those is one of the step types on the automation reference, with the same fields the editor shows and the same fields an agent is handed over the local API.

The tables it uses

These load with the recipe. A dataset is a typed table your workspace owns — the columns are named and typed up front so the steps can address them, and every one of them is yours to rename, extend or fill from a file afterwards.

Re-running updates the row it already wrote rather than adding a second one. That is what the match column in the save step is for, and it is the difference between a status check and a table that doubles in size every pass.

What it asks you for

Settings are filled in when the run starts, and every profile can hold its own values — which is how one workflow serves a whole folder of accounts.

credibility

Who you are, and why this is not spam · textarea · required

One or two sentences with a number in them. This is the part that answers "why is a stranger writing to me", and a number is what answers it — an adjective does not.

offer

The offer · textarea · required

A quantified result, a tight window, and the risk taken off them. All three: a result with no timeframe is a hope, and a timeframe with no risk reversal is a demand.

ask

The ask · textarea · required

Two concrete times, not "let me know what suits". Every extra reply a meeting needs before it exists is a place the thread dies.

signoff

Sign-off · text

Optional, and short. "sent from my phone" is a real signal that a real person typed this; a deliberate typo is not — it reads as careless far more often than it reads as human, and it cannot be taken back.

pool

Mailbox pool · text

The name of a pool under Mail. The least-used mailbox in it that still has allowance today sends each message. Leave empty and pick a single mailbox on the step instead — one of the two has to be set before the first run.

Loading it

In the launcher, open Automations, choose Load a starter pack, and pick Outbound email. Untick anything you do not want. The tables land first, then the workflows, then a project called Outbound that links them together.

What arrives is an ordinary automation row. Open it in the editor, change a step, rename it, delete it — nothing in the app treats it as special afterwards, and loading the pack a second time makes a fresh copy rather than overwriting the one you edited. Tables are the opposite: an existing table of the same name is reused and keeps its rows.