← All posts

How to keep an Instagram outreach suppression list across campaigns

Record contact preferences in a manual suppression ledger, resolve uncertain matches, and separate eligible candidates from people to hold or exclude.

An Instagram outreach suppression list is your team's record of people who should be excluded from future outreach, and the reason and scope for that decision. Check it against each new candidate list before preparing messages. Keep unresolved identities or conflicting evidence on hold. A missing match means only that you found no restriction in the records you reviewed; it does not establish permission to contact someone.

This guide produces a manual contact-preference ledger and a reviewed candidate list. The ledger lives outside DM Studio. DM Studio does not import it as a suppression rule, detect stop requests, or synchronize it across teammates. Someone must review conversations, update the record, and remove excluded or held rows from the actual sending list.

Why isn't sending history enough?

Sending history tells you what a sending attempt recorded. A contact-preference ledger tells you whether another approach is appropriate for this brand or organization. A person can receive a message successfully and later ask for no further contact. Another person may be the wrong contact even if no message was sent.

RecordWhat it answersWhat it does not establish
DM Studio HistoryWhat attempt, message, time, and result are recorded in this Chrome browser?Whether the recipient replied or asked to stop
Saved campaign recipient stateWho is recorded as sent or remaining in that campaign?Whether a new campaign should contact that person
Manual suppression ledgerWhat restriction did the team verify, for which scope, and who owns the decision?An automatically enforced product filter

DM Studio's option to exclude previously successful recipients when preparing a new audience uses local sending history. It is a separate check. It cannot replace a record of refusals, stop requests, or wrong-target decisions. Review history and follow-up preparation when you need to reconcile actual sending results.

Download the manual review worksheet

Download the English suppression review CSV.

This CSV is not a sending list. Do not upload it to DM Studio. Its record_type is manual_review_not_send_list; it uses ledger_handle, not the import field username. It contains excluded and held candidates as well as an eligible example. Renaming that column to username, or copying the whole column into an import file, would turn people you meant to exclude into recipients.

The five sample IDs contain sample: and are deliberately not valid Instagram handles. They represent fictional people, not accounts to find or contact. Replace the examples in your own working copy. When opening the file in a spreadsheet, import all columns as text. The supplied file has no formulas, account credentials, or real contact records.

Use this worksheet as a record of one candidate review. Maintain your team's continuing suppression ledger separately using the same scope, handle, reason, evidence, and reviewer fields. Retain that ledger when starting a new campaign; an empty campaign is not an empty contact history.

What should each restriction record contain?

Keep enough detail for the next reviewer to reproduce the decision without copying entire conversations into the sheet.

FieldWhat to write
ScopeA brand or the whole organization, with a stable internal key such as sample_brand_a or sample_org
ledger_handleThe reviewed handle used for comparison, with the original input kept alongside it
ReasonStop request, wrong target, identity unresolved, or conflicting evidence; distinguish a declined offer from a request to stop future contact
EvidenceA short description and a reference your assigned reviewer can open, with the date checked
Review ownerThe person or team role responsible for confirming or changing the restriction
Decision and next actionExclude, hold, or eligible for this candidate review, with a concrete next step

Scope needs evidence. “Please stop contacting me from your company” can support an organization-wide entry when the conversation clearly refers to your organization. “This project isn't for me” does not by itself settle future contact preferences. Record what the person actually communicated. If you cannot resolve whether a restriction covers another brand, hold that candidate while the owner checks the original conversation. Do not switch brands or sender accounts to get around a restriction.

Use the ledger to record your team's contact preferences and decisions. This worksheet does not define legal retention periods or interpret legal rights or obligations. Decide who maintains the file and who can access its evidence. Set a review task when context needs checking; a review date must not automatically clear a stop request.

How do you compare handles without guessing identities?

For a plain handle, trim surrounding whitespace, remove a leading @, and use lowercase for comparison. Preserve periods and underscores: creator.a and creator_a are different strings. Keep the original value so a reviewer can see what changed.

For example, the fictional input @SAMPLE:CREATOR_A becomes sample:creator_a in this worksheet. The colon is a deliberate sample marker, not a normalization rule for real handles.

If the input is a profile URL, a display name, a renamed account, or an uncertain alias, inspect the actual profile and relevant conversation before assigning an identity. Do not strip a URL or merge similar-looking names and call that a verified match. If the evidence is missing, put the row on hold. The worksheet does not perform account lookup or track handle changes.

Worked example: five candidates become one eligible row

The fictional campaign is for sample_brand_a, part of sample_org. The reviewer compares brand-level entries and applicable organization-level entries, then checks current conversations. All dates below are fictional workflow examples on 2026-11-10, in KST.

CandidateEvidence checkedDecisionNext action
sample:creator_aOrganization-wide stop request, confirmed at 09:00ExcludeLeave out of every brand's proposed outreach under sample_org
sample:creator_bBrand A conversation confirms this is the wrong contact, checked at 09:05ExcludeRemove this person from Brand A's candidate list; do not guess a replacement account
sample:creator_cOld note says contact is welcome; later conversation may contain a stop request, checked at 09:10HoldReview owner resolves the conflicting evidence before any message
sample:creator_dDisplay name resembles a ledger entry, but handle identity is unconfirmed at 09:15HoldVerify the profile and conversation; do not assume no match
sample:creator_eBrand and organization records reviewed, no restriction found; current relevance checked at 09:20Eligible for this reviewPrepare one proposed recipient row, then complete the campaign preflight

Result: 5 reviewed, 2 excluded, 2 held, 1 eligible. The downloadable worksheet contains the same five decisions, their scope, reviewer, evidence notes, and next actions. It is a completed example, not a claim about real campaign results.

The output sending list would contain only the verified real handle corresponding to candidate E, plus the fields needed for that person's message. It would not contain the worksheet's sample ID, evidence notes, excluded rows, or held rows. “Eligible” is a candidate-review result, not approval to start sending: the sender, proposal, message, and current account conditions still need checking.

Apply the check to each new or resumed campaign

  1. Name the scope and owner. Record the intended brand, organization, sending account, and person responsible for the review. Other teammates must know which continuing ledger is current.
  2. Review the candidate inputs. Normalize plain handles, keep the original inputs, and hold uncertain identities. Check organization-wide restrictions as well as restrictions for the intended brand.
  3. Read the evidence. Compare the ledger with relevant Instagram conversations and current campaign notes. Do not treat a blank cell, an old approval, or a successful send as clearance.
  4. Write one decision per candidate. Exclude confirmed restrictions and wrong targets. Hold unknown or conflicting cases. Mark the remaining candidates eligible only after the relevance check.
  5. Build a separate sending file. Copy only eligible, verified recipients into the proper import format. Recount the rows and inspect the recipient preview. Keep the review worksheet outside the import flow.
  6. Recheck changes before sending. If a reply, sender change, handoff, or pause makes the review stale, compare the affected candidates again. Update restrictions promptly and remove affected people from remaining recipients before resuming. Updating an external sheet does not change a saved campaign.

Use the campaign preflight checklist for the final execution decision. For the separate mechanics of preparing an import, use Excel and CSV personalization.

Common failures and the action to take

  • The contact asked to stop after the file was prepared. Update the ledger, hold the affected campaign work, and remove the person from the prepared file and any remaining campaign recipients. Recheck the actual recipient preview before continuing.
  • Another browser has no record of the old message. Keep the restriction. Local history is not the shared ledger. Reconcile the records with the common owner before sending; use the handoff checklist.
  • A teammate says “we can try from the other brand.” Check the documented scope. Hold the candidate if that scope is unclear. Do not interpret a new sender as a way to bypass a stop request.
  • A review date arrives with no new evidence. Keep the restriction or hold decision. A calendar date is a task reminder, not evidence that the person's preference changed.

Frequently asked questions

Does DM Studio automatically apply this suppression CSV?

No. This is an external manual worksheet. Review it yourself, then construct a separate eligible sending list. Updating this file does not remove recipients from DM Studio or synchronize records between browsers.

Should every declined offer become an organization-wide stop entry?

No. Record the actual wording and context. Declining a project, being the wrong contact, and asking for no more contact are different decisions. Exclude the declined proposal as appropriate; hold future contact if its scope is uncertain rather than inventing permission or a wider restriction.

What if the person later asks for a new proposal?

Have the review owner verify the later conversation and what it covers. Keep the earlier entry and record the new evidence and the resulting decision for that scope. Do not silently erase the stop request or assume permission for every brand and project.

Can a spreadsheet enforce the exclusion for the team?

No. It helps people coordinate; it does not enforce product behavior. Assign a common owner, make the current file identifiable, and have the sender confirm the prepared recipient list against it. For a new proposal after a completed project, use the repeat-collaboration checklist.