Stop sending product updates to unqualified leads

The product changelog went to 14,000 marketing contacts. Half of them asked for a newsletter. Sales marked a chunk Unqualified last quarter.

Those people still got What's new in version 4. They unsubscribe, or they reply as if sales reopened a closed no.

Stop the send list. Product updates belong to people who should hear about the product.

Build an active segment on lifecycle stage and lead status, then exclude the rest. Regular emails use Don't send to. Automated product mail follows the workflow's enrollment, not that menu.

Product mail is not for every marketing contact

A newsletter subscriber opted in for articles. A product update is a changelog, a feature launch, or a version note.

Those are different subscription jobs. Mixing them on one static All contacts list is the leak.

HubSpot's segment help treats lifecycle stage as a property that changes, and it names active segments as the tool for that. A static launch list from last year still holds people sales already marked Unqualified. The next What's new send will not notice.

Welcome pacing is a different dump, covered in how to fix welcome sequences that dump six emails in three days. This post is the wrong people, not six emails in three days.

Lead status Unqualified is not a blog subscriber

HubSpot's lifecycle stage help puts Lead status under Sales Qualified Lead. Default lead status values include New, Open, In Progress, Open Deal, Unqualified, Attempted to Contact, Connected, and Bad Timing. Unqualified here means sales already worked an SQL and said no, or not now.

A blog signup is usually Subscriber. A form conversion without sales work is usually Lead. Those records often have a blank Lead status.

Filtering only Lead status is Unqualified will miss them. They will still get the changelog.

Product updates that should reach customers and active users need a positive include, not a single exclude. Build who is in. Then exclude Unqualified, Bad Timing, Subscriber, and Lead if those stages should never see version notes.

Regular emails need Don't send to

HubSpot's Don't send to help applies to regular marketing emails. Select the exclude segment in Don't send to, then review it on Review and send. Contacts in that segment are dropped even if they also sit in Send to.

One exception is documented. If a contact is added as an individual in Send to, they still get the email even when they are on a Don't send to segment. A VP pasted into the recipient field will receive the changelog you thought you blocked.

HubSpot errors if Send to and Don't send to segments together use more than 250 filters. Build one include segment and one exclude segment instead of stacking many nested lists. Membership-in-segment filters keep the pair simple.

Don't send to does not rewrite an automated email. Recipients for automation come from the workflow. Fixing the regular send and leaving the workflow on All marketing contacts leaves the leak on a schedule.

Automated product emails follow enrollment

If the changelog is saved for automation, open the workflow that sends it. Enrollment on marketing contact create, or on a list with no lifecycle filter, will keep mailing Subscribers. Add enrollment that matches the live product audience, and unenroll when lifecycle or lead status leaves that audience.

A suppression segment on the workflow can drop people who become Unqualified after they enrolled. They will not finish the remaining feature emails. That is the same HubSpot unenroll idea as a welcome canvas, pointed at status instead of pacing.

RSS or blog subscriber sends pick recipients from blog subscribers. Do not use that path for a product changelog unless the blog is only for customers. The audience is the subscription, not the feature.

Keep the include list active

Create an active segment whose filters are the people who should get product mail. Lifecycle stage is any of Customer or Evangelist is a clean starting include. Add Lead status is none of Unqualified and Bad Timing if SQLs must see releases.

Exclude from that segment with Lifecycle stage is any of Subscriber or Lead, if those stages should stay on the newsletter only. HubSpot's exclude-from-segment help uses Lifecycle stage is none of Customer as the example for keeping customers out of a prospect list. Flip that pattern for product mail.

HubSpot's default lifecycle updates only move a record forward. A Customer will not slide back to Lead on their own. Unqualified is a lead status sales set, so the exclude segment has to read that property, not wait for lifecycle to rewind.

Re-send a test to the new Send to and Don't send to pair. Check a known Unqualified record and a known Subscriber in the preview of who will not be sent. If they still appear, the individual override or the automated workflow is the remaining leak.

• Send to is all marketing contacts, with no lifecycle or lead status filter.
• The launch list is static, so Unqualified records never drop off.
• A contact was added individually, so Don't send to does not block them.
• The changelog is automated, so Don't send to on a regular email never runs.
• Filters use only Lead status Unqualified and miss blank-status Subscribers.
• Blog subscriber RSS is the channel used for version notes.

Unlike a full lifecycle marketing and automation engagement, this post covers only product-update lists by stage and lead status. For a look at whether the next changelog is a customer list or a leftover file, start with Get Free Assessment.