Instagram DM campaign preflight checklist: approve or hold
Check the sender, every recipient row, variables, contact preferences, limits, and stop conditions before each campaign. Includes a completed example and manual CSV.
Before each Instagram DM campaign, check the sender, every intended recipient, message variables, contact exclusions, available product allowance, and what will make you stop. Approve only the reviewed rows for the named sender and file version. Hold the campaign if a shared requirement is unresolved; hold or exclude an individual row when the problem belongs to that recipient.
This is the final decision before a campaign, including a returning campaign. For installation and first-use steps, use the getting started guide. Here you will turn five fictional input rows into two ready rows, two held rows, and one excluded row, with an explicit approval record.
Download the manual campaign preflight worksheet. It contains the completed example and a blank check row. This is a manual review document, not a recipient import or a sending CSV. It does not read your account, block a send, or update DM Studio.
What are you approving?
Write a short approval scope before checking rows. In this fictional case:
- Campaign: autumn workshop invitation, prepared by Sam.
- Intended sender: fictional Brand A; the signed-in Instagram account must match it.
- Input: reviewed-list-v2; template: invitation-v1.
- Decision: only SAMPLE-01 and SAMPLE-03 may proceed after the checks below; no messages have been sent.
These labels are invented and are not Instagram handles. The example does not authorize real outreach. For your campaign, check the recipient's relevance, previous conversation, refusal and stated contact preference yourself. Being present in a public list does not settle whether a person should be contacted.
Check the shared requirements first
A correct recipient cannot repair a wrong sender or a missing template column. Resolve these campaign-wide checks before approving any row.
| Shared check | Evidence to inspect | Hold condition |
|---|---|---|
| Sender | The connected Instagram account in the sending screen, compared with the intended brand | Different account, uncertain identity, or sender changed since review |
| Input and template version | Original reviewed file, imported headers and exact variable names | Missing column, stale file, or saved data differs from the reviewed original |
| Contact exclusions | Your manual refusal/preference records, prior conversations and available history | Exclusion check not completed, or unresolved previous contact |
| Available allowance and controls | Current plan allowance, connected account's daily count and settings | Required capacity not available, settings not reviewed, or an active restriction |
| Stop and handoff | Named operator, reason to stop and where pending rows will be recorded | Nobody owns the decision, or the team intends to retry through an unresolved restriction |
In DM Studio, the phone preview shows the first row with a username; it is not an all-row check. Loading a saved CSV campaign can lose custom column values. When those variables matter, keep the original file, reimport it, and inspect the table and template again before a later run. Use the CSV preparation guide for the mapping step.
Walk through the same five fictional rows
The source file has offer, but the template expects proposal. That missing header affects the whole file, not only SAMPLE-03. Sam first maps offer to proposal in a copy, keeps the original, and checks every row again. The table records row-specific issues after that shared correction.
| Sample ID | Data and context | Issue found | Resolution and final state |
|---|---|---|---|
| SAMPLE-01 | Avery; ceramics tutorial; paid workshop collaboration; Brand A | No further issue after header correction | Ready for Brand A |
| SAMPLE-02 | Blank first_name; textiles tutorial; paid workshop collaboration; Brand A | Blank cell would leave an incomplete greeting | Hold until the name is verified or a neutral greeting is separately reviewed |
| SAMPLE-03 | Jules; print tutorial; paid workshop collaboration; Brand A | Proposal was under the source header offer | Ready after the shared mapping and full-row review |
| SAMPLE-04 | Ren; illustration tutorial; paid workshop collaboration; intended Brand B | This row belongs to a different sender | Hold outside this campaign; review separately with its intended sender |
| SAMPLE-05 | Sol; clay tutorial; paid workshop collaboration; Brand A | Prior conversation records a request for no further invitations | Exclude from this invitation and retain the preference in the manual exclusion record |
All people, details and observations are fictional. SAMPLE IDs are review labels, not account names. Do not upload the example to a sender.
Sam does not switch to Brand B in the middle of the approved Brand A campaign to process SAMPLE-04. A sender change invalidates the relevant sender review. Sam also does not treat SAMPLE-05 as eligible just because it appears in a new campaign.
Check the actual text for every ready row
For the corrected first_name, topic and proposal columns, the template is:
Hi {{first_name}}, I enjoyed your {{topic}}. May I send a brief for a {{proposal}}?
The two ready rows must match these complete drafts:
| Ready row | Reviewed message |
|---|---|
| SAMPLE-01 | Hi Avery, I enjoyed your ceramics tutorial. May I send a brief for a paid workshop collaboration? |
| SAMPLE-03 | Hi Jules, I enjoyed your print tutorial. May I send a brief for a paid workshop collaboration? |
A blank cell and an absent header are different failures. A blank first_name can produce “Hi ,”. An absent proposal column can leave {{proposal}} visible. Neither an account lookup nor a correct first preview proves the other rows are complete. Inspect each intended message against the source details; a fluent sentence about the wrong person's work still fails review.
Which limits belong in the approval?
DM Studio's product ceiling is 100 successful sends per Instagram account per day. Free adds a separate allowance of 5 successful sends per day across Instagram accounts on the same license. PRO removes that free server allowance but keeps the per-account product ceiling. A lower user setting can leave less available capacity.
The minimum interval is 20 seconds. At the default interval, waits are randomized from 20 seconds up to, but not including, 40 seconds; a longer user setting produces longer waits. Batch breaks occur after ten attempts, default to 60 minutes, and cannot be set below 30 minutes. Product controls are not Instagram's published safe limits and do not guarantee delivery.
In this example Sam records that the current screen allows the two ready rows under the reviewed settings. That is an invented observation, not a measured product result. If the screen blocks sending, the allowance is unknown, or Instagram has returned a restriction, mark hold. Do not infer available capacity from the size of the CSV. See daily limits and their units.
Write the final approval and stop conditions
Sam's completed record reads:
Approved for preparation and a separate user-started sending decision: Brand A, reviewed-list-v2, invitation-v1, SAMPLE-01 and SAMPLE-03 only. SAMPLE-02 and SAMPLE-04 remain held; SAMPLE-05 is excluded. Sam owns the review. No message has been sent in this example. Recheck if the sender, input, template, preferences or allowance changes.
The operational stop conditions are equally specific: stop if the sender differs, a token or incorrect detail appears, a new refusal is found, or a restriction/error makes the next action uncertain. Preserve the remaining rows and record what happened before deciding whether to resume. Do not turn “pending” into “failed” or “sent” without evidence.
DM Studio stops its queue on recognized account-level restrictions and preserves pending recipients. That product behavior does not replace the manual contact-preference review. Its optional exclude previously contacted accounts control uses successful history in this browser; it is not a refusal register or a complete record of conversations from every tool. Check the option and its scope instead of assuming it is enabled.
A completed preflight is a bounded human decision. It does not automatically start the queue or authorize every later campaign. Keep the held and excluded rows outside the approved sending input, and keep a dated copy of the decision.
How should I fill the download?
Each CSV row records the check or sample ID, expected evidence, observed issue, resolution, final state, owner and next action. Shared gates, all five sample rows, both rendered messages and the final decision are included. Replace the fictional records with your own; add rows for every intended recipient. Every cell is text and there are no formulas.
Keep the approval worksheet separate from the actual recipient file. If you cannot complete a required check without access you do not have, write unknown and hold. Buying a subscription, connecting an account or sending a test message is not required to complete a hold decision.
Common questions
Does passing preflight mean delivery is guaranteed?
No. It means the named file and workflow passed your stated preparation checks. Instagram can still refuse an attempt, and recipient responses are unknown.
Can I approve just the ready rows?
Yes, after every shared gate is resolved. Remove held and excluded rows from the sending input and record the exact approved subset.
Should I reuse last week's approval?
Recheck it. A different sender, changed file, missing custom data, new contact preference or changed allowance can invalidate the earlier decision.
DM Studio team publishes this guide and sells the product described. The walkthrough is fictional, the worksheet is manually maintained, and no external account or delivery test was performed for this example.