EmailDesk marketing workflows provide a visible recipient opt-out and update scoped contact and campaign evidence when a valid unsubscribe request is received.
Reviewed: July 29, 2026
Marketing message requirements
EmailDesk campaign and marketing-test workflows retain a visible unsubscribe footer or link. Campaign delivery also adds List-Unsubscribe and one-click List-Unsubscribe-Post headers.
The unsubscribe URL uses a signed token scoped with the available organization, campaign, recipient, and email context. The recipient does not need to sign in.
What a valid request changes
A valid request marks the matching scoped contact as unsubscribed, upserts marketing unsubscribe evidence, and updates the matching campaign recipient when that context is available.
Campaign recipient eligibility is checked again before provider delivery. Contacts that are missing, unsubscribed, bounced, or suppressed are skipped with evidence under the current workflow.
Transactional email boundary
Necessary account, password, billing, receipt, security, support, or other operational messages can follow a transactional path rather than the marketing unsubscribe workflow.
A sender must not label promotional or audience mail as transactional to bypass recipient permission, unsubscribe, suppression, or acceptable-use requirements.
Customer responsibility
Customers remain responsible for permission or another lawful basis, accurate contact data, prompt opt-out handling outside EmailDesk where applicable, and clean audience practices.
EmailDesk can skip, review, or block marketing activity when required unsubscribe behavior is absent or when complaints, bounces, suppressions, policy decisions, or other evidence require action.