When a creator asks you to stop, pause their outreach at once and record the request in one shared suppression record. Apply it to every list, teammate and sending tool the request covers. Check that record again before each send, so an old export or a new campaign cannot restart contact.
Some requests go further than an unsubscribe. A creator may say an address is wrong, that it belongs to a former manager, or that they want their details deleted. Those cases also need you to find the address in every export and shared copy, remove or correct it, and keep a task log of what changed and what is still open.
Deleting a row from one spreadsheet leaves the other copies in place, and an influencer outreach unsubscribe should survive a change of campaign owner. The workflow below is an operational checklist. The legal examples come from UK and US guidance. Ask your privacy lead or a qualified adviser which rules, deadlines and retention exceptions apply to your organisation.
Sort the request before you act
Pause pending outreach to the creator while you work out what they asked for. Record when the request arrived and keep the original wording, or a link to it, in a restricted case record. Keep what the creator said apart from your team's reading of it, and do not copy the full message into every campaign sheet.
These are illustrative requests and recommended responses, not universal legal classifications.
| Request or situation | Recommended handling |
|---|---|
| "Unsubscribe me from your emails." | Suppress marketing email from the relevant sender across campaigns. Do not invent a campaign-only limit. |
| "Please stop contacting me." | Pause the team's outreach across channels. Record the broad wording and review any doubt internally. |
| "This campaign isn't for me." | End that proposal and its follow-ups. Do not record a permanent objection that the message never expressed. |
| "Delete my details and stop emailing." | Stop outreach now and open a separate erasure case. Review what minimal suppression record may remain. |
| An old manager's address is still linked | Stop using that address for this creator. Record which link is wrong and whether a replacement is verified. |
| The creator says an address is not theirs | Remove it from active outreach while you review it. Record which records hold the disputed link. |
Do not make a creator find an unsubscribe link after they have already asked you to stop. In the UK, the ICO says a direct-marketing objection needs no set wording, and it can reach any part of the organisation, spoken or written.
Do not downgrade an erasure request to an unsubscribe because it came as an informal reply. The ICO's erasure guidance says UK requests can be verbal or written and need not mention Article 17. If you are unsure who sent the request, that guidance calls for proportionate identity checks.
The ICO's erasure and right to object pages both say they are under review after the Data (Use and Access) Act. Have the case owner confirm the current requirements.
Stop the queued messages first
The person who receives the request should pause active sequences and remove scheduled outreach for that creator, including manual follow-up tasks. Record who did this and when. If your team cannot confirm that another tool has stopped, hold the affected sends until someone checks.
For US email covered by CAN-SPAM, the FTC requires honoring opt-outs within 10 business days. It also forbids charging a fee or asking for more than a reply email or a visit to a single web page. Use immediate suppression as your team's target. The legal deadline is no reason to leave a follow-up running.
Stopping one sequence is only part of the work. Modash's sequence announcement describes exit rules that a reply or a change in relationship status can trigger. Your team still needs to decide what stops future enrollment, other senders and re-imported contacts.
Record what the request covers
The ICO separates channel-specific opt-outs from broader direct-marketing objections. Your record should therefore name the channel, purpose and organisation covered. It should also identify the creator separately from any one email address.
Never treat another visible address or a DM button as a workaround. A channel outside a narrow opt-out still needs its own valid basis for contact. Limit business inquiries to those the creator welcomes and the applicable rules permit. Use the public-contact data review checklist before you treat discovered details as usable outreach data.
For agencies, record which represented brand or sender received the request. Escalate wording that may cover the whole agency. Do not quietly narrow it to one campaign, and do not assume it allows you to share personal data with every client.
Keep a shared suppression record
Use one central record that every outreach owner can check. These are suggested fields, not status names from a particular provider.
| Field | What to record |
|---|---|
| Identity | Internal creator ID and confirmed contact identifiers needed for matching |
| Scope | Sender or brand, channels and marketing purposes covered |
| Request | Received time, receiving channel and restricted evidence reference |
| State | Suppressed, or held while scope is reviewed |
| Enforcement | Tools, lists and queued messages checked, with a completion time for each |
| Owner | Person responsible for open actions |
| Changes | Reason, evidence and reviewer for any later scope change |
Keep the information needed to prevent repeat contact. Do not copy the creator's full profile, audience data or inbox history into the suppression record. The ICO recommends minimal suppression data so you can check new lists without continuing the marketing the person objected to.
Minimal suppression data also matters when a creator asks for deletion. The ICO's objection guidance explains why a minimal suppression record may still be appropriate after an erasure request. If you remove every trace of an opt-out, a later import can put the person back into outreach. Keep suppression data out of any marketing use.
Use confirmed identity links. A creator may have several profiles, and a manager may use one mailbox for several creators. Do not merge everyone who shares an agency address. The contact deduplication guide explains how to keep person, profile and representation records separate. If a shared inbox itself opts out, review that address-level restriction too.
Give senders access to the suppression decision. Restrict the underlying messages and personal details to the people who need them.
Enforce it at import and before sending
Check every incoming list against suppression before its contacts become eligible for outreach. A fresh import must never replace a suppressed state with an ordinary campaign status.
Check again when someone enrolls a creator in a sequence and again right before a message goes out. A list approved yesterday is stale once a request arrives today. Include teammate mailboxes, agency-run tools and manual DMs within the recorded scope.
If tools cannot share updates automatically, assign a named person to reconcile them before the affected campaign runs. Record incomplete updates as open work. A checkbox saying someone was notified does not prove their scheduled messages stopped.
Share suppression information only through an approved compliance process. The FTC restricts transferring opted-out email addresses, with an exception for a company hired to help comply with CAN-SPAM. It also warns that outsourcing email marketing does not remove the marketer's responsibility.
Trace every copy of the contact
A wrong address, a disputed address or an erasure request means you also have to find where the contact travelled. Start with the record that feeds your working lists. Record its internal ID, the source reference, the affected field and the teams known to have received it. Then follow each transfer outward.
Search these places within your authorised team access:
- Check the main CRM record, its linked profiles and any campaign-specific contact fields.
- Check research sheets, saved list copies and downloaded CSV files.
- Check outreach audiences, queued sequences and connected integrations.
- Check shared-drive folders, agency handoffs and attachments sent to colleagues.
- Check notes or briefs where someone pasted the address outside a contact field.
Search by the disputed address and by the creator's record ID or known handles. A search by name alone can miss an exported row. One manager address may also serve several creators, so check the requested scope before you remove unrelated records.
Give every copy you find a log entry. Record its owner and whether you can edit it, must ask another owner, or need a provider to act. A deleted CRM field does not prove that a downloaded file changed.
Mailchimp's deletion documentation is one provider example. It separates permanent deletion from archiving, which can be undone, and tells users handling its GDPR removal notice to cover every audience and connected integration. Check how each tool you use behaves. An archive command does not count as proof of erasure.
Give each copy an owner and completion evidence
Assign one case owner to coordinate the work and one responsible person for each location. Modash's article on influencer relationships recommends team communication guidelines and one contact person per creator. Apply the same idea here, so the creator does not have to repeat the request to each campaign manager.
Use this hypothetical task log as a model. The record ID, file names and results are illustrative and describe no real creator or deletion.
| Location | Owner | Action | Evidence | Status |
|---|---|---|---|---|
| CRM record C-204 | CRM administrator | Remove disputed contact field | Record ID, change time and a second-person check | Verified |
| Autumn-shortlist.csv | Campaign lead | Replace the shared export with a corrected copy | Old link disabled, replacement searched for the field | Verified |
| Agency working sheet | Agency contact | Remove matching rows and find onward copies | Request sent, agency confirmation still missing | Open |
| Outreach audience | Sending owner | Remove active contact, keep approved suppression | No queued message, suppression decision recorded | Verified |
| Backup copy | Systems owner | Apply the approved backup handling plan | Retention schedule and restore limits recorded | Pending expiry |
Put these case-level details above the log:
- The case records when the request arrived, who owns the case and when the response is due.
- The case records the request type and its confirmed scope.
- The case lists the places searched, the search date and the reviewer.
- The case names any retained data, its purpose, who can access it and when it will be reviewed or deleted.
- The case lists recipient notifications and copies that are still open.
- The case records the final response date and the evidence behind that response.
Use record IDs and restricted evidence links where you can. Do not make a fresh full-list export, or paste the deleted address into an open ticket, to prove you removed it. The case log itself needs an access and retention decision.
Handle copies you cannot remove yourself
Ask the owner of each shared copy to remove or correct the data and to name any onward transfers. Ask for confirmation with the file or system reference, the action taken and the completion date. A sent request stays an open task until you have evidence of the result.
Under the ICO's UK erasure guidance, an organisation that disclosed personal data must tell the recipients about the erasure unless that is impossible or takes disproportionate effort. Let the privacy lead judge any exception. An unanswered email is not evidence that a recipient deleted their copy.
Backups need their own entry. The same guidance covers putting backup data beyond use until an existing overwrite schedule removes it. Record the real schedule and how a restore will keep the contact out of active use. Do not promise removal from every backup at once if your system cannot do that.
Some records may need to stay for a legal obligation or legal claims. Have the privacy lead write down the reason and its limits. A restricted transaction record is no reason to leave the address in the next campaign export.
Test the paths that can restart outreach
Use team-owned test contacts in a safe test setup. Never send a test message to a creator who opted out. These hypothetical acceptance tests check whether your workflow blocks repeat contact.
| Test | Expected result |
|---|---|
| Re-import an old file containing a suppressed contact | Suppression remains, and the contact cannot enter outreach. |
| Have another teammate start a new campaign | The same scope restriction blocks enrollment or sending. |
| Queue a message, then record the opt-out | The queued message is cancelled or blocked before release. |
| Import a confirmed second address for a broadly suppressed creator | Identity matching keeps the broader restriction. |
| Attempt a DM after a broad stop-contact request | The DM task is blocked or held for review. |
| Disconnect a tool from suppression updates | Affected outreach waits until the state can be verified. |
Save the result, the owner and any gap for each test. Test again after you change an integration or import process.
After a removal or correction, generate the next permitted working export from the corrected source. Have a second person check it for the affected field and linked duplicate records. Check the queued audience separately. Neither check needs a message to the creator.
Keep the case open if an agency copy is unconfirmed or a retention decision is missing. A completion response should say what you removed, what remains under a documented restriction and what is still open. Do not claim you erased all copies unless the evidence supports it.
Reopen contact only with evidence
Do not expire an opt-out because a campaign ended, a teammate changed or the creator showed up in another list. Under the ICO's guidance, a person who does not opt out again has not reversed an earlier objection. A later specific withdrawal or agreement to marketing can change the position. Record the evidence and the approved scope before you change suppression.
Keep necessary admin for an existing relationship apart from new pitches. The FTC treats transactional and relationship messages narrowly, and an existing partnership alone does not make every email exempt. Have the responsible owner review payment or delivery messages and keep promotional content out of them.
For a routine correction, use the contact refresh queue to review a replacement address. A deletion request or marketing objection is no reason to look for another route to the same person.
Pick one team-owned test contact now. Suppress it, re-import it from an old list, and ask another teammate to try to enroll it. Keep the affected outreach paused until both paths respect the recorded restriction. Then open your task log and name the owner and the evidence needed to close the oldest open copy.
