List owners can offer a backup opt-out when the ESP’s one-click link fails in a corporate firewall. The form records the address and the list they mean, then honour it in your ESP the same day.
Notify whoever owns the ESP, with a same-day SLA in your team.
Name the actual lists, plus an ‘all’ option.
Also add it to email footers as a backup URL.
Do the actual unsubscribe. Then mark the submission processed.
An unsubscribe form is a web page where someone asks to leave a mailing list. US CAN-SPAM and UK PECR / ICO guidance both expect a working opt-out. Your ESP’s List-Unsubscribe header should do the real work; this HTML page is the fallback when that link 404s or the person forwards a newsletter without headers.
It uses the signup pack because you still need email plus an ‘interest’ select you will relabel to which list. It is not a signup. Make that obvious in the heading so you do not accidentally recapture people.
The only job is to identify the address and the list. Do not upsell on this page.
Do not require phone or company. Extra fields look like a dark pattern and attract complaints to the ICO or state AGs.
One-click unsubscribe is the law-adjacent best practice. A form is the spare tyre.
Mailchimp, Customer.io, and SES all support it. Keep it working; this page is backup.
Linked in the footer of the site and in a P.S. when IT blocks the ESP domain.
SMS-style, messy for email. Still log those in the same dashboard if you accept them.
How you get blocklisted. Do not.
A single /unsubscribe page on your marketing host is enough. Process the dashboard into the ESP daily.
This form does not suppress at the ESP automatically. Someone must action it. Automate with Zapier if volume is high.
No. Keep one-click. This is for failures and forwarded mail.
US law expects prompt honouring (commonly treated as 10 business days max—aim for same day).
Soft opt-in still needs an easy opt-out. Honour this form as if it were the ESP link.
Optional message only. A required survey is a bad look and may be seen as a barrier.
Capture repro steps, severity, and environment from users on your site.
Let customers pitch product ideas with context, not a one-line tweet.
A lighter intake than a feature request for culture, process, or UX niggles.