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
Contact official Selstack support when the saved result, status or resolved identity still conflicts with the intended record after one refresh. Include the business, page, time, safe reference and visible message. Do not include passwords, OTPs, recovery codes, full card details, BVN, NIN or unmasked bank documents.