Handling unsubscribe requests across several lists

Record what the person asked to stop, then apply that scope to every marketing list and system it covers. Changing the status in the list that sent the email may leave the same address eligible elsewhere. A confirmation screen is useful only when the covered sending routes reflect it.

Interpret the request

Read the wording in the email, the page reached after a click and any reply or support message. “Stop the workshop newsletter” may be narrower than “Stop emailing me marketing.” Preserve the person's wording; do not reduce a broad request to a single-list opt-out because one list owns the link.

Where the scope is unclear, review the surrounding message and resolve it promptly. Apply exclusions before another campaign is queued.

For commercial email and SMS, the Spam Act 2003 (Cth) requires a functioning unsubscribe facility that works for at least 30 days after sending. Unsubscribe requests must be actioned within five business days. ACMA (Australian Communications and Media Authority) publishes its Avoid sending spam guidance.

Direct marketing opt-outs also sit within the Privacy Act 1988 and the Australian Privacy Principles, including APP 7.

Map the sending routes

List each audience, automation, event tool and provider that can send the business's marketing. For each route, record who owns recipient status and how an opt-out reaches it. Include manual uploads and integrations that might later update the address.

A request record should capture the address, request time and channel, the person's wording, the marketing streams covered, propagation status and an owner for unresolved routes. Limit access to the personal information needed for this task. A central record works only if each sender uses it or receives a reliable update before selecting recipients.

Set an owner and completion deadline for each hand-off, with all covered routes updated within the five-business-day limit. Record when each route confirms exclusion, then check any queued campaign before it is released.

Account for platform boundaries

Platform status models vary. When one business uses several audiences, check the actual configuration; do not assume an opt-out in one audience updates another.

Mailchimp requires an unsubscribe link on all email campaigns sent through its platform. The link does not by itself show that the request has reached every audience, automation or provider; verify each route in the inventory.

Different unsubscribe mechanisms can carry different scopes. Treat a separate reply asking to stop all the business's marketing according to that broader request. Bring body-link, inbox and reply-based requests into the same scope-and-propagation process.

Verify the exclusion

Use authorised controlled records representing an address in one list, an address in two lists and an address updated by an integration after opting out. For each, inspect the saved statuses, next audience selections and queued automations. If a covered route still selects the address, hold its marketing while the hand-off is corrected.

A purchase, import or service-contact update is not itself a fresh marketing choice. If a person later makes a clear new subscription choice, assess and record it separately. Retain the earlier request so a future upload cannot erase the reason for exclusion.