Skip to main content
Dashboard → Autopilot → the gear icon. These apply to every Autopilot on the account, not to one of them.

​
Queue wait time

2, 6, 12, 24 or 48 hours. Default: 6. Contacts are often created before the data that qualifies them — someone signs up, the contact appears, and the onboarding answers your filter needs arrive minutes or hours later. So a contact that matches nothing yet waits in the queue and is re-checked as its CRM data arrives: every minute for the first quarter of an hour, then less often, until this window runs out. Then it is abandoned — never researched, no credit spent.
If you have a fallback Autopilot, it gets the last look at the lead at the end of this window, and takes it if its own filter matches.

​
Drop messages that fall too far behind

Off, 7, 14, 30 or 60 days. Default: off. When there is more to send than the daily limits allow, messages move forward rather than being dropped. Usually that is right. But a follow-up written for “three days after the intro” landing five weeks later is worse than not landing: it reads as though nobody was paying attention. This is lateness, not age — how far past its planned date a message is. Fourteen days behind plan means the same thing in a two-week sequence and a two-month one. Leads dropped this way end with Fell too far behind its schedule in Activity.
Turning this on is a symptom fix. If messages routinely fall weeks behind, the real answer is a higher daily limit, another mailbox or seat, or fewer leads entering at once — check the capacity bars.

​
Addresses to skip

Both off by default. Each one narrows who your Autopilots contact, and narrowing is a choice — so neither is on unless you say so. Both are checked before anything else, so a skipped lead costs no research and no credit, and appears with its reason in the HubSpot intake log.
Free-provider skipping is blunter than it looks: a founder on Gmail is still a founder. Only switch it on if your product genuinely does not sell to people at a personal address.
Turning either setting on does not touch leads already enrolled, and turning one off does not go back for leads it skipped earlier — those come back the way any lead does, through your CRM.

​
Frequently asked questions

No. A lead in the queue has not been researched — that is the whole point of the wait. Credits are spent at the moment a filter matches.
Only leads that match nothing. A lead matching a filter is researched and enrolled within about a minute, whatever the wait time is set to.
No — all three are account-wide. Per-Autopilot decisions (filter, channels, voice, stop conditions) live in the builder.