# Instantly vs Smartlead: suppression across client campaigns Compare Instantly and Smartlead blocklist scope and conversation history. Canonical page: https://quillwell.com/guides/compare/instantly-vs-smartlead/ Updated 2026-10-30 Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/ ## The short answer - [Instantly’s blocklist](https://help.instantly.ai/en/articles/6192983-global-blocklist) covers a workspace; check the import route to determine whether ongoing campaigns are included. - [Smartlead’s blocklist](https://helpcenter.smartlead.ai/en/articles/139-what-is-global-block-list-your-comprehensive-cold-outreach-guide) requires entries in the matching client scope; unassigned entries protect unassigned campaigns. - If your agency separates Smartlead clients, verify suppression for each intended scope before activating campaigns. - Preserve lead and conversation exports before switching, then verify what the destination can restore. ## Map the scope before importing Map each campaign to a workspace or client before relying on a blocklist. Suppose an agency has two clients and one unassigned campaign. [Instantly’s blocklist guide](https://help.instantly.ai/en/articles/6192983-global-blocklist) describes workspace-wide blocking. Its Blocklist tab is checked during import and across ongoing campaigns. [Smartlead’s blocklist guide](https://helpcenter.smartlead.ai/en/articles/139-what-is-global-block-list-your-comprehensive-cold-outreach-guide) assigns entries to a client; unassigned entries protect unassigned campaigns. In the example, the agency needs matching entries for each client and an unassigned entry for the unassigned campaign. [Smartlead’s troubleshooting article](https://helpcenter.smartlead.ai/en/articles/410-why-are-blocked-leads-still-receiving-emails) says each entry and campaign must share client scope. Domains match exactly and should omit protocol and www. Write down the workspace and client associated with each campaign. Reconcile those boundaries against the suppression records before activation. Check the actual configuration with inactive fixtures. A successful import alone does not prove coverage across every client. ## Check the destination of each import Choose the destination of each import deliberately. The same Sheet can give different coverage depending on where it is connected. [Instantly’s blocklist guide](https://help.instantly.ai/en/articles/6192983-global-blocklist) describes two Google Sheets paths. A Sheet imported into the Blocklist tab receives ongoing-campaign checks; the separate Google Sheets Blocklist connection checks imports only. [Smartlead’s blocklist guide](https://helpcenter.smartlead.ai/en/articles/139-what-is-global-block-list-your-comprehensive-cold-outreach-guide) documents CSV import and export. Its client association determines which campaigns the entry covers. [Smartlead’s API reference](https://helpcenter.smartlead.ai/en/articles/125-full-api-documentation) describes import settings that can bypass global-block and unsubscribe checks. Import success does not prove send eligibility; inspect the settings and ask about subsequent checks. [Smartlead’s All Leads guide](https://helpcenter.smartlead.ai/en/articles/425-all-leads-unlimited-lead-storage) describes switches that can ignore duplicate checks or suppression during a campaign push. Its initial rollout targets Unlimited users with 60K+ leads. Record every route your team uses, including integrations. Keep each configuration with the client’s suppression inventory. For the two-client example, trace each incoming list to the campaign it will serve. Record who owns the list and when it was last reconciled. If an integration uses a different route from a manual import, include it in the test. An unexamined route can leave the agency unable to explain its coverage. ## Separate duplicates from suppression Test duplicate checks separately from suppression. Avoiding a repeated record does not prove whether a do-not-contact rule applies. [Instantly duplicate documentation](https://help.instantly.ai/en/articles/7891047-check-for-duplicate-leads) says workspace-level checks across campaigns and lists are on by default and can be disabled. File-level duplicate removal always runs. That workspace rule does not prove protection across separate workspaces. Test each boundary your agency uses. [Smartlead troubleshooting](https://helpcenter.smartlead.ai/en/articles/410-why-are-blocked-leads-still-receiving-emails) warns that already-queued messages may precede blocking. Its wording leaves the exact check timing unclear, so do not assume a block recalls a queued message. For an already enrolled fixture, inspect the displayed status and queue without sending. If eligibility is not visible, record the result as unresolved. ## Keep the history before changing tools Preserve the history before changing tools or cycling contacts. A contact row alone may lack the context the next operator needs. [Smartlead export options](https://helpcenter.smartlead.ai/en/articles/57-data-export-options-in-smartlead) include separate campaign lead and inbox exports. The inbox export exposes sequence and reply details alongside sent and replied timestamps and the unsubscribe flag. [Smartlead’s API reference](https://helpcenter.smartlead.ai/en/articles/125-full-api-documentation) describes a separate per-lead campaign message-history endpoint. That description does not prove that another product can import the history. [Instantly’s download guide](https://help.instantly.ai/en/articles/6285719-how-to-download-leads-csv) covers leads from campaigns, CRM and All Leads. It does not prove portability of full reply history or analytics. [Instantly plan documentation](https://help.instantly.ai/en/articles/7920548-outbound-plans-comparison) counts active and paused campaign contacts against uploaded contact limits. Pausing alone does not free that capacity. [Smartlead troubleshooting](https://helpcenter.smartlead.ai/en/articles/410-why-are-blocked-leads-still-receiving-emails) warns of a possible email-thread loss when removing a block entry. Preserve history first and confirm the consequence with Smartlead. Keep the original export and a mapping of the client to each suppressed address. Verify that the destination can restore the history and suppression reason before retiring the old record. Agree on the minimum conversation history your team must retain. Ask the destination vendor to show how each field appears after import, then compare it with the original export. ## Run an inactive acceptance test Test each boundary with owned fixtures before activating campaigns. This is a test for you to run; we have not run it. Keep all test campaigns inactive. Agree on the expected result before each step. Record the product and plan, then note the configuration date and client aliases. Include the import route and before-and-after counts.