9 min read
How to update HubSpot when a contact leaves a company
Written by the ReplyCircuit team · Last verified September 2026
HubSpot's own figure is that marketing databases decay by about 22.5% a year, and job changes are the largest part of that. When someone leaves, one auto-reply tells you everything you need — the person is gone, and often who has taken over. Miss it and you keep sending to a mailbox that is about to be deleted, while the replacement contact never reaches the CRM.
The short answer
- HubSpot will not detect a departure for you. The "no longer with the company" reply is a normal inbound email — nothing on the record changes until a person or an app changes it.
- Do three things per departure: set Lead Status to "No Longer With Company", unenrol them from active sequences, and create the named replacement against the same company.
- "This mailbox will be closed shortly" is a countdown, not a footnote. Once it is deleted your sends hard bounce, and the bounce itself is the reputation damage.
- No app can set marketing-contact status. Set the field you can set, then let a one-time HubSpot workflow flip those contacts to Non-Marketing.
The manual workaround
- Read the 'no longer with the company' auto-reply.
- Find the contact in HubSpot and set Lead Status to 'No Longer With Company'.
- Unenrol them from every active sequence so sales steps stop firing.
- Copy the replacement contact's name, email and job title out of the reply.
- Create the new contact, associate the company, and set the lifecycle stage.
- Once, not per contact: build the workflow that moves those contacts to Non-Marketing.
With ReplyCircuit
- ReplyCircuit reads the reply and sets Lead Status to "No Longer With Company" on the departed contact.
- Your one-time HubSpot workflow picks that value up and moves them to Non-Marketing.
- It extracts the replacement contact from the message and creates the record.
- It associates the new contact with the same company and notifies the record owner.
What HubSpot actually does when someone leaves
Nothing, until the mail server tells it something. A "no longer with the company" message is usually a normal auto-reply from a mailbox that is still alive, so HubSpot logs it as an inbound email and leaves the record exactly as it was. The contact stays in your sequences, stays marketable, and stays in your active lists.
Later, when IT deletes the mailbox, sends start hard bouncing. At that point HubSpot does step in: a hard-bounced address is dropped from marketing email automatically. That sounds like the problem solves itself, and it is where most teams stop thinking about it.
It does not solve itself, for three reasons. The bounce itself is the damage — reputation is hurt by the send that bounced, not by the ones you stop afterwards. Bounce suppression covers marketing email, not one-to-one sales email or sequence steps, which keep firing at a dead mailbox. And a bounced record still sits in your portal as a marketing contact you are paying for, with no note explaining why the deal went quiet.
The gap between the reply arriving and the mailbox being deleted is usually weeks. That window is the entire opportunity: it is when the replacement contact is named, and when you can act before anything bounces at all.
Rather not run this routine every morning? ReplyCircuit does every step from the reply itself.
Start a free trialThe 10-minute manual version (how teams do it today)
Everything here is native HubSpot plus your inbox. It is a real routine, not a placeholder — teams run exactly this:
1. In Gmail or Outlook, build a filter into a dedicated folder for the phrases that signal a departure: "no longer with", "has left the company", "is no longer employed", "left the business". Review the folder once a day.
2. Open the message and pull out three things before you touch HubSpot: confirmation that the person has gone, the name of anyone covering the role, and their email address.
3. Find the contact in HubSpot and set Lead Status to "No Longer With Company". Use one consistent value — this is the field everything else keys off, so a free-text note will not do.
4. On the record, open Sales > Sequences and unenrol them from anything active. Bounce suppression will not stop sequence steps, so this is the part that actually protects the account from an awkward send.
5. Create the replacement contact, associate them with the same company, and set an owner. Thirty seconds now, versus rebuilding the relationship from scratch in six months.
6. Once, not per contact: build the HubSpot workflow that watches for Lead Status "No Longer With Company" and sets those contacts to Non-Marketing. That is the only way the marketing-contact count ever comes down.
The routine works. It costs ten minutes a day, it stops the week you are on holiday, and it misses every departure phrased in a way your filter did not anticipate.
Every departure handled the moment the reply lands
ReplyCircuit reads the reply, flags the departed contact, creates the replacement against the same company, and tells the owner. Free trial, no card required.
Start your 14-day trialNo credit card · Cancel any time
The replacement contact is free pipeline
The most valuable line in a departure reply is the one naming a replacement. That person holds the role you were already targeting, they have been handed the responsibility this week, and you have a genuine reason to be in touch — their own company's auto-responder sent you to them.
Compare that with sourcing the same person cold in two months: no referral, no context, and by then your competition has probably called them.
Most teams lose it because the reply is skimmed and archived. The name was in front of you and never became a record.
Weeks
typically pass between the departure auto-reply and IT deleting the mailbox — that gap is your entire window
Source: HubSpot Knowledge Base — email bouncesReferred
not cold — their own company's auto-responder handed you the replacement's name and address
Source: The reply itselfNo study isolates "contacted on the departure reply" versus "contacted two months later" as a variable — this is the evidence chain, not a single benchmark.
Deciding what happens to the old record
Do not delete it. The departed contact carries the email history, the deal associations, and the reason the conversation stopped — delete it and the next rep to look at the account has no idea what happened.
Keep the record, mark it, and take it out of circulation: Lead Status set, sequences cleared, Non-Marketing via the workflow. That combination stops every automated send without destroying the history.
One thing to watch: if you already run a workflow that resets Lead Status when a contact replies, exclude "No Longer With Company" from it, or your departure flag gets overwritten by the very reply that created it.
A real departure reply, broken down
From: s.whitfield@northbank-group.com
Subject: Automatic reply: Q4 pricing for Northbank
Thank you for your email.
Sarah Whitfield is no longer with Northbank Group. This mailbox is not monitored and will be closed shortly.
For anything relating to procurement, please contact Daniel Osei (Head of Procurement) at d.osei@northbank-group.com or on +44 20 7946 0102.
The departure
Sarah Whitfield has left Northbank Group — flag the record, don't delete it
The deadline
"will be closed shortly" — the address will hard bounce soon, so stop sends now
The replacement
Daniel Osei, Head of Procurement — the exact role you were targeting
The contact details
d.osei@northbank-group.com, +44 20 7946 0102 — enough to create the record in full
What ReplyCircuit proposes for that same reply
This is the review card you would see. You approve it, or you switch this reply type to automatic once the accuracy has earned your trust.
Contact departed · replacement named
- Departed contact
- Sarah Whitfield — Lead Status → "No Longer With Company"
- Sequences
- Unenrolled from "Q4 pricing outreach" (step 3 of 6)
- New contact
- Daniel Osei · d.osei@northbank-group.com · Head of Procurement
- Association
- Northbank Group (same company record)
- Owner notified
- Task created for the deal owner: "Intro to Daniel Osei — Sarah has left"
- Marketing status
- Handled by your HubSpot workflow watching Lead Status
Two emails you can send today
The first is for when the reply names a replacement. The second is for when it doesn't and you need a route back into the account.
Intro to the named replacement
Subject: Passed to you by Northbank's system — Q4 pricing
Hi Daniel, I emailed Sarah Whitfield about procurement at Northbank and got an automatic note saying she has left, and that you have picked up the area. Short version of where we got to: we were looking at how your team handles [specific thing], and Sarah had asked for pricing ahead of Q4. Rather than restart that from scratch — is this still yours, and is it still worth a conversation? Happy to send the one-page summary she had, or to leave it if the priority has moved. Best, [Your name]
No replacement named
Subject: Who has taken over from Sarah?
Hi [name], I had been speaking with Sarah Whitfield about procurement, and her mailbox is now returning an automatic reply saying she has left Northbank. Could you point me to whoever has picked that up? Happy to send them the background directly so nobody has to repeat themselves. Thanks, [Your name]
Common questions
Sources
Keep reading
Turn every departure reply into a clean record and a new contact
ReplyCircuit classifies every reply and keeps HubSpot accurate automatically.
Start your 14-day trial14-day free trial · No credit card · Cancel any time