Skip to main content

​
What an Autopilot is

An Autopilot is three decisions:
  1. Who gets contacted — a filter over your HubSpot contact properties
  2. What is said to them — a sequence of touches, each written per lead from that lead’s research
  3. When it stops — a reply, a booked meeting, a CRM change
Everything between those decisions happens on its own: the research, the writing, the sending, the pacing, the daily limits and the record in your CRM.
You can run several Autopilots side by side — one for inbound signups, one for a prospected list, one as a catch-all. A lead only ever belongs to one of them at a time.

​
What you need before it can run

​
Which Autopilot gets a lead

Autopilots are checked top to bottom, and the first matching filter wins. Nothing further down ever sees that lead. Use the arrows on the list to reorder — specific Autopilots above, broad ones below.
  • An Autopilot with no filter matches every lead. That is occasionally what you want, as a catch-all at the bottom of the list, and never what you want by accident. The list marks it Catch-all and greys out everything beneath it as Never reached.
  • A fallback Autopilot is checked differently: it is skipped during the normal pass and gets the last look at a lead just before it would be abandoned. It keeps its own filter — a fallback is not the same thing as a catch-all.
  • A lead already in an active sequence is not enrolled a second time.

​
What it costs

One credit per researched lead — the same pool as the API and the Chrome extension. Sending, retrying, skipping and rescheduling are all free. A lead costs nothing when it is:
  • abandoned after matching no filter
  • skipped by Addresses to skip or Excluded domains
  • already researched for this product (with Research each contact only once on, the default)
See Credits.

​
Where everything lives

Build your first Autopilot

Name, filter, channels, voice, the sequence, stop conditions.

What stops a sequence

What ends it, what deliberately does not, and the one CRM gap to know about.

Activity and troubleshooting

Why a message was not sent, where a missing lead went, closing a lead by hand.

Templates

Start from a ready-made Autopilot instead of a blank one.

Analytics

Outcomes, responded rate, and what counts as a win.

Settings

Queue wait time, addresses to skip, dropping messages that fall behind.

​
Frequently asked questions

Nothing is wrong yet — an Autopilot only acts on contacts created after it was switched on. Existing contacts are not swept up. If a new contact was created and still nothing happened, work through Activity and troubleshooting.
Only if your filter lets it. Two guards help: Excluded domains (Settings → Outreach) skips whole companies for good, and a stop condition on a CRM property ends a sequence the moment someone’s lifecycle stage moves. Both are worth setting before the first Autopilot goes live.
No. The first matching filter wins, and a lead in an active sequence is not enrolled again. It can enter a different Autopilot later, once the first sequence has ended and the contact comes back through your CRM.
No. You write the angle for each touch — the instruction — and the message itself is written per lead from that lead’s research. Show example in the builder renders a real one before you commit.
The first email still goes out, because a first message can honestly ask what someone is trying to achieve. Later messages and the other channels need something real to say, and skip rather than send filler — with the reason recorded on the lead’s timeline.
Switch the Autopilots off, or pause the channel: a paused LinkedIn seat or mailbox stops sending while keeping every lead enrolled. Leads resume where they left off.