Guide

Five rules, in order, before anyone is written to.

The most damaging thing a sending tool can do is email the same person twice from two campaigns. CraftNudge runs every import through the same rules, in an order that was chosen rather than accumulated.

What happens to each row of an upload?

Five checks, in this order. Is it an address at all. Is it already a lead in this campaign. Is it, or its whole domain, on the workspace blocklist. Is it already a lead in another campaign in this workspace. Was it sent an email inside the re-contact window. The first check that fires decides the row’s bucket, and the upload reports every bucket: added, invalid, duplicates, blocked, in another campaign, contacted recently.

Why that order?

Not an address comes first because nothing else can be said about it. Then the campaign’s own duplicates, so re-uploading yesterday’s file reads as duplicates rather than as a rule firing. Then the blocklist: what you added by hand or by CSV, address or whole domain, plus every unsubscribe and every address a receiving server said does not exist, which land there on their own. Then the two workspace rules, the narrower one before the wider one. An address caught by two rules is counted under the one that matters most.

What does “one campaign at a time” do?

On by default. An address that is already a lead in another campaign in the workspace is skipped and counted. It exists because the re-contact window below can only catch an address you have already written to: two uploads made before the first send would both go out, and one person would get two cold emails from you. A skipped row is visible. A second cold email is not recoverable.

What is the re-contact window?

Nobody in the workspace is contacted again inside this many days, whatever campaign it is. The default is 180 days, counted from the last email you sent to that address. Set it to 0 to turn the rule off. It is a workspace setting, so it applies to every campaign at once.

Do lists follow the same rules?

A list is a set of people, not a campaign, so putting someone on a list only checks two things: is it an address, and is it new to the list. The five rules run when the list starts a campaign, exactly as they run for a CSV, so the same list can start one campaign now and another next quarter without anyone being written to twice.

Why can I not delete a lead I have emailed?

Deleting a lead takes its send records with it. That would hand today’s cap back to the inbox and let a re-upload start the sequence from step one. So a lead that has been emailed can be paused, and resumed later, but not deleted. The check is inside the delete itself, so a send landing while you look cannot be erased.

What does the free mail server check do?

One click looks up the mail server of every pending lead’s domain. A domain with no mail server cannot receive mail from anyone, so those leads are marked invalid before the first send. It is a DNS query, not a verification service, and it costs nothing. It catches the worst of a stale list, not every bad address.

Does the API do the same?

Yes. Leads added by the API go through the same five rules and get the same counts back, so a pipeline that feeds CraftNudge can read what was skipped and why.

Both workspace rules sit on one card in settings, with the counts they produce shown on every upload. Contacts are unlimited on every plan, so the list can be generous and the rules can be strict.