Out-of-office replies: the pause and the re-send
An out-of-office is never treated as a reply. MailFleet pauses the person until the return date they give — or for 7 days when they give none — and then sends the next step; when it answered the last email, that same email goes again once they're back.
Where: Automatic — Replies shows "Out of office" with a "Back <date>" chip ("Paused until <date>" when no date was given); the line under the lead's name in Replies, the lead panel in a campaign's Leads tab and Tasks show "Out of office until <date>" or "Out of office (no return date given) — paused until <date>"
How to do it
- Nothing to set up. Every automatic reply is tagged OOO and labelled "Out of office" in the Replies list, but only a real out-of-office (one that says the person is away) pauses anyone.
- Open the conversation: under the lead's name it reads "Out of office — next step held until Sep 21" (a return date was found), "Out of office (no return date given) — paused until Sep 21" (none was given: 7 days from the day it arrived), or "Automatic reply — not an out-of-office, so nothing is paused" (an automatic reply that doesn't say they're away, such as "we've received your message").
- Check the person in the campaign's Leads tab: the panel shows "Out of office until <date> · their auto-reply gave this date, so the next step and any open task wait for it." — or, with no date given, "Out of office (no return date given) — paused until <date> · their auto-reply gave no date, so the next step and any open task wait 7 days." When their last email is due to go again, the panel's next step reads "The same email again — they were out of office" with the day it goes. Tasks for them show the same wording.
- When they are back and actually reply, the pause ends by itself, nothing is sent again, and the thread shows as a normal reply.
Good to know
- An automatic reply is recognised from wording such as out of office, on leave / annual leave / maternity leave / sick leave, on holiday / on vacation, away until, back in the office, limited access to email, upon my return, automatic reply / auto-response, no longer with the company / has left the company, office is closed, bank holiday. It is checked before anything else, so an out-of-office that happens to contain "remove" or "not interested" is never read as a no. Only an out-of-office — wording that says the person is away and coming back (out of office, on leave, on holiday, travelling, upon my return, back in the office, limited access to email, bank holiday, office closed until) — pauses anyone. An acknowledgement ("we've received your message and will reply within 24 hours", "I'll be back to you shortly", "our office is closed on weekends") and a "no longer with the company" or "this mailbox is no longer monitored" notice are automatic replies too, but they pause no one.
- An out-of-office never counts as a reply: the lead is not marked Replied, the sequence is not stopped, campaign counts don't move, nothing is forwarded to your inbox, and the Reply received, Reply — interested and Lead unsubscribed webhooks don't fire (only a Reply tagged webhook carrying the OOO tag is sent, when that tag is switched on for the campaign). It does show in the queue (and counts in the unread badge) so you can see it.
- The return date is read from phrasings like "until 21st September", "returning Mon 21 September 2026", "back in the office on Thursday", "until 21/09/2026", "September 14-18" / "9/14 through 9/18" (back the day after the range), "until Friday 25th inclusive", "until after the bank holiday", "returning tomorrow", "back next week", "in December" — and from a subject like "Out of office until 21 Sep". Wording the rules can't place but that mentions a day, month or weekday is read once by AI.
- No return date ("I will respond upon my return"): the person is paused for 7 days, counted from the day the out-of-office arrived where they are (their timezone, else the campaign's), and held exactly as a stated date would be. A return date they give later replaces those 7 days, earlier or later; another out-of-office with no date never shortens a date they did give. A return date that has already come by the time it arrives (an auto-reply nobody switched off) means they are back: nothing is paused and nothing is sent again. A date more than 366 days ahead is ignored.
- When an out-of-office arrives, every active step for that person in every campaign is moved to the start of the return day in the campaign's timezone (or the person's own timezone when the campaign respects lead timezones), so the first send lands in the campaign's sending window on that day. Every open task for them becomes due when the window opens that day. Queued LinkedIn actions are dropped and queued again on the return day.
- A hold only ever moves things later. A date earlier than what is already scheduled changes nothing, and a later out-of-office extends the hold — the one exception is a stated return date replacing a 7-day pause.
- The lead's activity line becomes "Out of office until Sep 21 — next step held" (or "Out of office (no return date given) — paused until Sep 21") when something was actually moved, and "Out of office — the last email goes again on Sep 21" when a re-send was scheduled.
- Out of office on the last email: when the out-of-office answered the email that ended a sequence (it ran out of steps — not one stopped by a reply, bounce, unsubscribe, block, a condition or a removal), that same email goes again on their return day, within the campaign's sending window. It is the email exactly as it went — same subject, same words, nothing rewritten — from the same mailbox, in the same thread, and it counts as a sent email (one credit). If that mailbox is at its daily limit it waits for it; if it was paused or taken off the campaign, another of the campaign's mailboxes sends it as a fresh email with its own signature; if that mailbox was deleted, the email isn't sent again. A finished campaign starts sending again for it and finishes again afterwards.
- The re-send happens at most once per person per campaign, so an auto-reply to the re-send (someone permanently out of office) never starts another. A manual email that was the last step opens its task again, due on the return day, instead of going by itself; a call or LinkedIn last step sends nothing again. Nothing goes again while the person is still in another running sequence — that one writes to them on their return day — and a real reply, a bounce or an unsubscribe before then cancels it.
- Out of office never starts a subsequence, whether it was tagged automatically or by hand.
- A person who is away and gets enrolled in a new campaign starts on their return day, not immediately.
- A real reply from the person ends the hold at once. Another out-of-office in the same thread keeps the "Out of office" label and can extend the hold.
- On the Leads page the Engagement filter "Out of office" lists everyone who has sent an automatic reply; the "Replied" engagement filter leaves them out unless they also sent a real reply.
Questions people ask
Someone's auto-reply said they're away but the next email still went out — why?
Most often the auto-reply didn't say they were away — an acknowledgement like "we've received your message" or a "no longer with the company" notice pauses no one — or it arrived after that email had already gone. An out-of-office pauses them until the date it gives, or for 7 days when it gives none.
Their last email arrived while they were away — will they ever see it?
Yes. When an out-of-office answers the last email of a sequence, that same email goes again on their return day (7 days on when they gave no date), in the same thread from the same mailbox. It happens once; if they reply before then, it isn't sent.
Can I set the return date myself?
Not directly. From the conversation you can pause them (More → Pause Lead) and resume when they're back, or add a follow-up task for their return date; you can also remove them from the campaign in its Leads tab.