Should I pause or unenrol a contact who is out of office?

Pause. Unenrolling ends the enrolment: the remaining steps are discarded, and re-enrolling later starts them from step one, so they receive the opening email again weeks after they first got it. Pausing keeps the steps and their order intact and stops the sends until you lift it. Unenrol only when the reply tells you something permanent — they have left the company, or they do not want contact — which is a different decision entirely.

What happens to steps that were already scheduled when I pause?

They stop sending. Pausing holds the enrolment where it is rather than deleting the queue, so when you resume, the contact continues from the step they were on rather than starting again. That is the practical difference from unenrolling, and the reason pausing is the right default for someone who is temporarily away.

What if the reply doesn't give a return date?

Then you have nothing to schedule the resume against, and guessing produces a task nobody trusts. Pause the enrolment, set the resume task for one to two weeks out, and treat that date as a check-in rather than a certainty. ReplyCircuit handles this the same way — when no date is present it says so on the review card instead of inventing one.

What if the return date lands on a weekend?

Resume on the next working day rather than the literal date. An email that arrives Saturday sits in the same backlog you were trying to avoid, which defeats the point of pausing at all. Roll it to Monday morning — and if their return date is itself a Monday, that is the best possible day for it.

Does the out-of-office reply count as a reply in my sequence reporting?

Often yes, and that is a separate problem worth knowing about. Auto-replies that HubSpot registers as responses inflate your reply rate on the Analyze tab, so a sequence can look like it is performing while nobody human has answered. We cover how to spot and correct that in the guide on auto-replies being counted as responses.

All guides

12 min read

How to pause a HubSpot sequence during an out-of-office

Written by the ReplyCircuit team · Last verified September 2026

A prospect goes away for two weeks and the enrolment carries on without them. In most cases HubSpot detects the out-of-office, keeps them enrolled, and steps three, four and five fire into an empty mailbox — and where detection fails, such as a Gmail auto-reply landing in an Outlook inbox, they are unenrolled entirely instead. Neither outcome is the one you wanted, and the decision about which to make is yours, by hand, every time.

The short answer

You have three options when a prospect is away — pause, unenrol, or let it run — and they are not equivalent. Pausing keeps the remaining steps and the enrolment history; unenrolling throws both away.
No integration can pause a HubSpot sequence for you. The public sequences API can see that a contact is enrolled, but there is no endpoint to pause an enrolment and no way to read whether one is paused. Any tool claiming automatic pausing is either unenrolling instead, or reminding you to do it.
HubSpot does not resume anything. Once paused, the enrolment sits there until a human restarts it — and nothing in HubSpot reads the return date out of the reply.
The resume day is the whole point. Pausing protects your steps; resuming on the morning they are back is what actually wins the reply.
A sequence pause does not block newsletters. Use an active HubSpot segment where ReplyCircuit OOO until is after Today under Don't send to for every marketing email.

The manual workaround

Spot the out-of-office in your inbox — it often never reaches the CRM.
Open the contact, find the active enrolment, and decide: pause, unenrol, or leave it.
Pause it in HubSpot, on the contact record, one contact at a time.
Set yourself a reminder to resume it on the return date — three weeks from now.

With ReplyCircuit

ReplyCircuit reads the reply and extracts the return date.
It detects the active enrolment and tells you which sequence it is, by name.
It hands you a one-tap link straight to the contact so the pause takes seconds.
It books the resume for the day they return, so the part everyone forgets is the part that is automatic.

Sequences and newsletters need separate protection

Pausing the contact here protects only their sales sequence. HubSpot marketing emails and newsletters use separate send and exclusion lists, so they can still reach the same person and trigger another out-of-office reply.

For marketing sends, create an active HubSpot segment such as Out Of Office Contacts with the filter ReplyCircuit OOO until is after Today. Add that segment under Don't send to on each marketing email. Use the sequence pause and the marketing exclusion together when your team sends both kinds of email.

Pausing is the easy half. Remembering to resume it three weeks later, on the right day, for the right contact, is the half that quietly fails.

See how ReplyCircuit handles the resume

Pause, unenrol, or let it run

First, the gate: sequences are a paid feature. They need Sales Hub or Service Hub Professional or Enterprise, an assigned Sales or Service seat, and sequences permissions on your user. If you are on Starter or Free, none of what follows is available to you — the equivalent there is a task queue and a dated reminder.

When an out-of-office comes back, you have three choices, and most teams make them inconsistently because nobody has written down what each one costs.

Let it run. The remaining steps send on schedule into a mailbox nobody is opening. On the day they return, those emails are somewhere in a backlog being triaged, not read. You have spent your best three touches and got nothing for them — and if the sequence completes while they are away, the contact drops out the far end and never gets a genuine follow-up at all.

Unenrol them. This stops the sends, which is better than nothing, but it throws away the remaining steps and ends the enrolment. Re-enrolling later starts them at step one, so they get the opening email again, weeks after they already received it. HubSpot's own guidance on unenrolling treats it as ending the sequence for that contact, not as a temporary hold.

Pause it. This is almost always the right answer. The enrolment stays intact, the remaining steps stay queued in the order you designed them, and nothing sends until you lift the pause. The only cost is that you have to remember to lift it — which is exactly where this falls apart in practice.

The pause is a click. The resume is the risk.

A paused enrolment with no reminder against it is a sequence that quietly stops existing. ReplyCircuit dates the resume from the reply itself, so the restart happens on the right morning without anyone holding it in their head.

Start your 14-day trial

No credit card · Cancel any time

What HubSpot does on its own, and where it stops

HubSpot does try. Sequences read the email server response to spot automated replies, and its knowledge base states that in most cases out-of-office replies will not cause unenrollment. That detection is automatic — there is no out-of-office setting to switch on, so if you have gone looking for one, you have not missed it.

Detection is also client-dependent, and HubSpot publishes the gaps. Gmail to Gmail, Outlook to Gmail and Outlook to Outlook are recognised; a Gmail out-of-office landing in an Outlook inbox is not, and that contact gets unenrolled as though a human replied. The same event, two opposite outcomes, decided by which mail clients happen to be involved.

But detection is where it stops. HubSpot will not pause the enrolment, will not read the return date out of the message body, and will not schedule the resume. There is no pause-until-return-date feature in sequences — the behaviour is binary: enrolled and sending, or unenrolled and finished. Everything in between is a person doing it by hand.

And the timing you are protecting is worth protecting. The gap between reaching someone while they are away and reaching them on the morning they are back is not marginal:

832 emails

the average backlog waiting after two weeks away — every sequence step you sent during the break is somewhere in the middle of it

Source: LondonOffices.com — survey of returning office workers

51%

of professionals who check email on holiday do it only to cut the backlog down — triaged and archived, not read or answered

Source: Robert Walters — 2025 annual leave research

Morning one

the return morning is the one window before the backlog rebuilds — the hours where response rates are highest

Source: Boomerang — analysis of millions of emails

No published study isolates pausing and resuming a sequence as a single variable — this is the evidence chain from three independent sources, and we would rather show you the chain than quote a number nobody measured.

Pausing it by hand (how teams do it today)

This is the native routine, start to finish. It takes about two minutes per contact and it works — the difficulty is never the clicks, it is doing it every morning and remembering the second half three weeks later.

1. Find the auto-reply. Start in your inbox, not HubSpot — auto-replies frequently never surface as a contact activity. A mail filter on "out of office", "automatic reply", "OOO" and "annual leave" into one folder makes this a once-a-day job instead of a constant interruption.

2. Read the body for the return date. The subject line tells you nothing useful. You are looking for the exact day they are back — that single date drives everything that follows.

3. Open the contact in HubSpot. If they are currently enrolled, an alert appears at the top of the contact record naming the sequence, with Pause and Resume in it — you do not need to go hunting through the Sequences tool.

4. Click Pause in that alert. Use pause rather than unenrol so the remaining steps and their order survive. Unenrol only if the reply tells you they have left the company or do not want to be contacted at all — that is a different guide.

5. Create the resume task in the same visit. On the contact, click Create task, set the due date to the return date, assign it to the sequence owner, and title it so it is unambiguous three weeks from now: "Resume paused sequence — back today". A calendar reminder in your own diary is not good enough; if you are off that week, nobody else can see it.

6. Log a note on the timeline saying why the sequence has a gap in it. When someone reviews the record in November, "paused 8 Sep, on leave, resumed 29 Sep" is the difference between a considered pause and a sequence that looks abandoned.

There are three levels of pause, and only one of them is the right tool here. Pausing from the contact record holds that one person, which is what an out-of-office calls for. Pausing a sequence from the Sequences list, or using Pause all, is for when you are the one going away. Watch the catch on those two: HubSpot only pauses the contacts you personally enrolled — anyone enrolled by a colleague keeps sending, which is why a shared prospect needs a message to whoever owns the enrolment.

Step five is the one that fails. Steps one to four happen because the reply is in front of you; step five has to survive three weeks of everything else.

Why no integration can do the pause for you

This is worth being straight about, because it is the thing most tools are vague on. HubSpot's public sequences API lets an application read a contact's enrolments — it can see that Danielle is in "Civils — Depot Rollout Q3". It does not expose an endpoint to pause an enrolment, and it does not report whether an enrolment is currently paused or running.

So there are exactly three things a tool can honestly do. It can unenrol the contact and call that pausing, which loses your remaining steps. It can claim to pause and quietly do nothing, which is worse. Or it can detect the enrolment, take you straight to the right screen, and own the half HubSpot genuinely leaves open — the return date and the resume.

We build the third one, and we say so on the card: ReplyCircuit tells you which sequence is running, gives you a one-tap link to the contact, and you confirm the pause in about five seconds. We do not report the pause as done until you tell us it is, because we cannot read it back and we are not going to guess in your CRM.

If you take one thing from this page into a vendor conversation, make it this question: when you say you pause the sequence, do you call the pause, or do you unenrol the contact? There is no third technical answer, and the two have very different consequences for your remaining steps.

The resume day is where the money is

Pausing protects the steps you already wrote. Resuming on the right morning is what turns them into a reply. And the resume is the half with no forcing function behind it — the auto-reply prompted the pause, but nothing at all prompts the restart.

One detail worth knowing before you plan around the resume: HubSpot does not fire the next step the moment you unpause. It waits out the remainder of the delay it was in when you paused. If a three-day delay had run two days, there is still a day to go after you resume. So if you want to be in front of them on the morning they are back, send that first email yourself and let the sequence pick up behind it — which is exactly what the resume-day template above is for.

The failure mode is quiet and common: a contact paused in July, still paused in October, sitting in a sequence that shows as active and produces nothing. Nobody notices, because a paused enrolment does not appear anywhere as a problem. It just stops.

Which is why the resume belongs on a dated HubSpot task assigned to the sequence owner, not in a person's memory or a personal calendar. Every pause should create one, in the same two minutes as the pause itself.

That is the piece we automate. ReplyCircuit reads the return date out of the reply, books the resume against the owner for that exact morning, and shows you what is due to come back this week — so a paused sequence is a scheduled state, not a forgotten one.

The reply that should trigger a pause

From: d.okonkwo@harlow-civils.co.uk

Subject: Automatic reply: Following up on the depot rollout

I am on annual leave from 8 September and back in the office on Monday 29 September.

I will not be picking up email while I am away. For anything that cannot wait, Priya Raman (p.raman@harlow-civils.co.uk) is covering my projects.

Danielle Okonkwo — Commercial Manager, Harlow Civils

Away until
Monday 29 September — three full weeks of sequence steps with nobody reading them
Resume date
29 September — the morning the pause should be lifted, not a day later
Covering colleague
Priya Raman — at her desk today, and a reason not to wait three weeks
What HubSpot does
Detects the auto-reply, keeps Danielle enrolled, sends steps three, four and five anyway

What ReplyCircuit does with that exact reply

The same message arrives at your processing address. Here is the review card the rep sees, before anything is written to HubSpot:

Out of office · return date found · active enrolment detected

Contact: Danielle Okonkwo — Harlow Civils
Return date extracted: 29 September 2026
Sequence detected: "Civils — Depot Rollout Q3", currently enrolled
Pause step: One tap opens the contact in HubSpot — you pause, then confirm
Resume booked: Task due 29 Sep: "Resume Danielle's sequence — she is back today"
Timeline note: Logged with the original reply attached, so the gap in the sequence is explained

Copy-paste: the two messages a paused sequence needs

The first goes out on the morning you resume. The second is for the case that catches everyone out — the prospect is shared, and someone else owns the sequence.

Resume-day email (send instead of restarting the sequence)

Subject: Picking this back up — {{first_name}}

Hi {{first_name}},

Welcome back. I paused my emails while you were away rather than filling your inbox, so this is the first one you'll have from me since {{away_date}}.

Where we left it: {{one_line_reason}}. If it's still worth ten minutes, I have Wednesday morning or Thursday afternoon.

If the timing is wrong, say so and I'll leave it with you.

{{your_name}}

Internal note — asking the sequence owner to pause

Subject: Pause needed: {{contact_name}} is out until {{return_date}}

Hi {{colleague_first_name}},

{{contact_name}} at {{company}} is on leave until {{return_date}} — auto-reply came back this morning.

They're still enrolled in {{sequence_name}}, which is yours. Could you pause them on the contact record? Otherwise the next three steps land in an empty mailbox and we burn the sequence before they read a word of it.

Happy to pick the resume back up on {{return_date}} if you'd rather I owned it from there.

{{your_name}}

Common questions

No — and this is the most useful thing on this page. HubSpot's public sequences API can read a contact's enrolments, so an app can tell you which sequence someone is in. There is no public endpoint to pause an enrolment, and no way to read back whether one is paused. Any product advertising automatic pausing is doing one of two things: unenrolling the contact instead, which discards your remaining steps and restarts them at step one if you re-enrol, or simply prompting you to pause it yourself. Ask which, because the answer changes what happens to your sequence.

Sources

Keep reading

The complete guide to HubSpot reply routing (2026)

9 min read

Email reply automation for HubSpot out-of-office replies (2026)

7 min read

HubSpot marked an auto-reply as a response — what to do

10 min read

How to update HubSpot when a contact leaves a company