Instantly tutorial: a clean setup sequence

1. Decide how you will provision domains and mailboxes

Before creating a campaign, decide whether you are connecting existing Google/Microsoft/SMTP accounts, buying done-for-you accounts, or using another Instantly-supported infrastructure option. Keep ownership, renewals, provider, and intended campaign use documented for each domain and mailbox.

If cold outreach is a meaningful part of the business, many teams use separate sending domains rather than placing experimental cold-email volume on the primary corporate domain. Whatever model you choose, make the sending identity clear and keep domain forwarding and ownership records organized.

2. Validate DNS and account connectivity

Confirm each mailbox can send and receive normal mail, then validate MX, SPF, DKIM, and DMARC. Instantly's current account dashboard includes domain-setup testing, but it is still worth checking a real message's authentication results after configuration.

Do not move to campaign creation while accounts are disconnected, authentication is failing, or the sender name/reply path is wrong. Those are infrastructure issues that copy cannot fix.

3. Warm up and ramp accounts deliberately

Instantly's current documentation recommends warming new accounts before campaign use and exposes warmup health on the Email Accounts dashboard. For standard new accounts, its guidance currently recommends at least two weeks of warmup before campaigns; AirMail has different preparation guidance. Follow the current platform instructions for the account type you purchased.

Campaign Slow Ramp is a separate account-level control. When enabled, current documentation says it starts campaign sending low and increases gradually until the configured account maximum. This is useful when transitioning from preparation to live sending.

4. Prepare the lead file before import

Clean the list outside the campaign first. Normalize company names, deduplicate contacts, apply suppression, verify role/account fit, and decide how to treat risky addresses. Instantly can verify during upload using Credits, but that should be the final data-quality gate rather than the first time anyone checks the list.

For CSV imports, current documentation requires the email field and supports predefined fields plus custom variables. Remove columns the sequence does not need so the mapping screen stays understandable.

5. Import leads and verify field mapping

In the campaign's Leads section, add the CSV (or another supported source), then inspect Instantly's suggested mappings. The email column must map to Email. Name, company, title, personalization, and custom fields should map to the variables you will actually use.

Enable duplicate checks according to your campaign policy. If using Instantly verification, confirm you have enough Credits and review the resulting Valid/Invalid/Risky statuses before activation. Upload a small batch first when the field schema is new.

6. Build the sequence around message logic

Use the Sequences section to create the initial email and follow-ups. Each step should add a new reason to respond rather than repeat the first message. Instantly supports step timing, variables, preview/test sending, and variants. Use placeholder/fallback values anywhere missing data could break a sentence.

Do not create dozens of variants on the first campaign simply because the software supports them. Test a meaningful difference—segment, offer angle, subject strategy, or ask—while holding the rest relatively stable.

7. Configure campaign options and sending controls

Assign the intended sending accounts, set the campaign daily limit, and review stop-on-reply. Current campaign options also include tracking controls, delivery optimization, provider-routing options, company-level stop behavior, unsubscribe headers, and other advanced settings depending on the plan.

Choose tracking deliberately. If deliverability is a higher priority than open/click analytics, text-only or reduced-tracking settings may be appropriate. Do not enable every option by default.

8. Configure schedule and stop behavior

Set active sending days/hours and any campaign start/end dates. Follow-up delays are calculated per lead and are still constrained by the active schedule. Make sure the campaign has enough daily capacity for both new leads and scheduled follow-ups.

Test reply behavior with an internal address. A real response should change the lead state the way you expect. For account-based outreach, review company-level stop options so colleagues do not continue receiving automated follow-ups after a teammate has already engaged.

9. Run a pre-launch QA pass

10. Monitor the first live batch before scaling

After launch, check that the campaign is actually sending from the intended accounts, that bounces are controlled, that replies enter the correct inbox/CRM workflow, and that no field or formatting issue appears in live mail. Review account-level usage so one sender is not unexpectedly carrying most of the volume.

If placement, provider errors, or bounces deteriorate, reduce pressure while you diagnose. If delivery is healthy but replies are poor, move upstream to the ICP, offer, and sequence rather than changing infrastructure without evidence.