Selstack
How it worksDiscoverPricingFeatures
Sign inStart free

Selstack Help Centre

Help homeSearchBlog
Help Centre

/

Marketing and Leads

/

Handle Unsubscribe Requests Correctly

Marketing and Leads

6 min read

Handle Unsubscribe Requests Correctly

Use permission and customer context to honour the request promptly and keep transactional communication distinct, test the journey and define when follow-up should stop.

Last updated 19 October 2026

A person planning work in a notebook beside a laptop.

Selstack is a platform for creators and businesses to build a public selling page, share individual offers, accept supported payments and bookings, and manage the resulting orders and customer details. A “Stack” is a selling page. This guide explains the relevant workflow and the seller’s responsibilities; payment methods, account requirements and some features depend on the business configuration and plan.

This task connects permission-based customer communication to a measurable business journey. This guide focuses on how to honour the request promptly and keep transactional communication distinct.

Define the audience and permission

Before creating a form, mailing list or email, state who should receive it and why. The task is to honour the request promptly and keep transactional communication distinct. A purchase receipt, support conversation or scraped address is not automatic permission for unrelated promotional email.

Use the right Selstack record

Build from the form, contact, campaign or order that provides the relevant context. Keep the source and intended action visible so leads with different needs are not pushed into the same follow-up.

Create a focused message or form

Ask only questions that affect qualification or delivery. Use a recognisable sender, clear subject or heading, useful explanation and one main next step. Keep sensitive data out of custom fields and tracking events.

Preview and test safely

Check the mobile layout, personalisation fallback, links, consent wording and unsubscribe path. Use a test recipient or safe submission rather than sending a draft to the full audience.

Review outcomes and stop conditions

Measure delivery, replies, qualified leads, orders and unsubscribes according to the campaign purpose. Stop follow-up when the person completes the action, opts out or no longer belongs in the mailing list.

Example: Handle Unsubscribe Requests Correctly

Use the campaign’s signed unsubscribe route and keep transactional purchase communication separate from promotion.

If Handle Unsubscribe Requests Correctly is not working

If an unsubscribed address appears in a marketing audience, stop the send and investigate suppression before contacting them again.

Confirm the result

  • The audience, permission and message purpose agree.
  • Personalisation, links, consent and unsubscribe behaviour were tested.
  • The follow-up has a clear owner and stop condition.
  • Results are measured against leads, orders or replies rather than views alone.

When to ask Selstack for help

Use email for a defined customer purpose

Selstack’s email tools connect campaigns and relevant customer lists within the business workspace. Before composing a message, decide who should receive it, why it is relevant and what the recipient should be able to do next. A campaign is not improved by being sent to the largest possible audience. A useful message might introduce a resource someone requested, explain an offer relevant to an interested group or provide a permitted follow-up. Keep necessary service information and optional promotional messages clear in both wording and audience selection.

Prepare the right audience

Review the mailing list or supported audience selection before writing a subject line. Confirm how people joined, what they were told and whether they remain eligible to receive the message. Do not add every order email address to a promotional list simply because it exists in Contacts. If the audience is unexpectedly large or contains an unfamiliar source, investigate before sending. A smaller, relevant group is easier to serve well and gives more meaningful feedback than an indiscriminate list of people with different expectations.

Write a message with one clear next step

Use a subject line that accurately describes the message rather than inventing urgency or suggesting a private transaction that has not occurred. In the body, explain the useful information or offer promptly and link to the relevant public page. A recipient who already chose a product should not need to search the entire selling page again. Review the price, currency, delivery wording and availability at the destination. The email and selling page should make the same promise, including any important conditions.

Make the sender recognisable

Review the business’s email settings and the sender or reply details available in the workspace. Use a name the recipient can connect to the business they interacted with. Check where a real reply will go and who is responsible for answering it. A polished design is not enough if customers reply to an unattended inbox or cannot identify the sender. Avoid presenting a campaign as an official personal message from someone who has not actually reviewed or sent it.

Preview and test before scheduling

Read the message on a narrow screen and inspect the supported preview or test route. Check the heading, paragraph length, links and call-to-action wording. Open every important destination rather than judging the link text alone. Review personalisation and make sure the message remains understandable when an optional name is missing. If a test exposes a problem, correct the campaign before sending. A test email is a check of the selected content and delivery route, not a reason to assume every recipient will open or act on the final campaign.

Choose timing deliberately

When scheduling a campaign, confirm the date, time and relevant time-zone context shown by the interface. Consider whether the offer will still be available when recipients read it. Do not schedule a message around a deadline that exists only in an old draft. Review campaign state after scheduling and distinguish a saved draft from a queued or sent message. Where an automation is configured, inspect its trigger, audience and content together so a new contact does not receive a message intended for a different stage of the relationship.

Read reports according to their labels

Sending, delivery, opening, clicking, enquiring and buying are different events. Use the report’s definitions and compare the same time period and audience when reviewing results. An open does not prove that the person read the whole message, and a click does not prove a paid order. If a campaign produces traffic but few useful actions, inspect the destination and the fit between the message and offer. Avoid changing several major parts at once when you want to understand what improved the result.

Respect unsubscribes and customer preferences

Keep the unsubscribe route available and honour the supported suppression state. Do not move a person to another list to continue the same unwanted promotion. If the business also maintains external email tools, review how customer preferences are respected in those copies. Necessary order or support communication should remain focused on its service purpose. A clear distinction protects the customer’s expectations and helps the team avoid treating every address as permission for every kind of message.

Build a maintainable follow-up routine

Keep a record of the campaign’s purpose, audience, destination and useful outcome. Review repeated customer questions and update the underlying offer or message where appropriate. A welcome sequence should deliver the promised resource and help the recipient use it before introducing a relevant next choice. Selstack supplies the campaign and customer context, while the business remains accountable for the relevance of its audience, accuracy of its claims and quality of the replies it sends when a customer responds.

Review Selstack pricing for current plans and online payment fees. For related tasks, visit the Help Centre. If the recorded result remains unclear, contact support with the relevant safe reference.

Was this article helpful?

Related help articles

A person planning work in a notebook beside a laptop.

Marketing and Leads

Follow Up With a New Lead

Use permission and customer context to reference the original request, answer one need and define stop conditions, test the journey and define when follow-up should stop.

6 min

Can’t find the answer?

Contact Selstack support and we’ll help you work through it.

Contact support