What is new-lead direct mail?

A practical guide to turning a new lead event into a traceable mailing: source records, address readiness, exclusions, proofing, send windows, tracking fields, and measurement boundaries.

What is new-lead direct mail?

New-lead direct mail is a mailed postcard or letter triggered by a new lead event or qualification rule. It gives operators a physical follow-up path while preserving the data needed to explain why the record was mailed.

A new lead may come from a form, import, call, event, referral, CRM stage, or another source-system signal. The workflow should not depend on a vague label such as fresh lead. It should preserve the source event, lead identifier, mailing address, proof version, send rule, batch record, and later review notes.

How is new-lead direct mail different from triggered postcards?

New-lead direct mail is one type of triggered direct mail. The trigger is specifically a new lead or qualification event, while triggered postcards can start from many events, including carts, purchases, inactivity, appointments, or status changes.

For the broader event-triggered workflow, see the triggered postcards guide. For the release logic that decides whether a record should actually mail, see the direct mail send-rule guide.

What source event should start the workflow?

The workflow should start from a named source event or qualification rule. Examples include a new form submission, qualified inbound call, imported lead, newly assigned owner, changed CRM stage, or first-party audience event.

The event record should answer: where did the lead come from, when did it qualify, which person or account owns it, and what mailing action is being considered? Without that record, the campaign becomes hard to audit and harder to explain when duplicates, exclusions, or source-system conflicts appear later.

Operator rule: do not release a new-lead mailing from a static label alone. Keep the source event, lead key, qualifying date, audience rule, and review owner together.

What should teams check before a new-lead mailing is released?

Teams should check the source event, lead identifier, address readiness, suppression rules, duplicate-send window, variable fields, proof version, campaign metadata, send window, and measurement plan before release.

Check	Question the workflow answers	Safe action
Source event	Why is this lead eligible now?	Hold records with an unclear or missing qualification event.
Recipient key	Which lead, contact, account, or household will receive the mail?	Hold records without a stable key for future review.
Address state	Is the mailing address complete enough for postal review?	Hold incomplete, ambiguous, or exception addresses.
Suppression result	Should this recipient or address be excluded?	Reject or hold records that match an active exclusion reason.
Duplicate window	Was a similar piece sent recently?	Hold records that need duplicate-send review.
Proof version	Is the creative approved for this lead source and data state?	Hold until variable fields, fallback copy, and layout are reviewed.
Campaign metadata	How will this mailing be measured later?	Save campaign ID, batch ID, tracking fields, and response sources.

What address checks matter for new leads?

New-lead mailings should check address completeness, standardization, secondary-unit risk, source-system conflicts, and whether the record needs manual review before release. A new lead is not automatically a mailable lead.

USPS Publication 28 and DMM 602 are useful starting points for address standards and addressing rules. Operators should also keep the source-system address, standardized address, exception reason, and reviewer action visible. For a deeper address-readiness workflow, see the mailable address guide.

How should the postcard proof handle variable lead data?

A new-lead postcard proof should show the final layout, address block, source-specific copy, variable fields, fallback copy, and any fields that may be blank. The proof should match the audience data used for the batch.

USPS Mailpiece Design resources and DMM 201 help teams review physical mailpiece layout. Those sources support layout readiness checks; they do not make an internal proof a postal approval. For production review steps, see the print proof guide and the postcard template guide.

How should teams prevent duplicate or awkward sends?

Teams should compare lead keys, contact keys, household keys, addresses, recent batches, campaign types, and source events before release. A new-lead trigger should not bypass suppression or duplicate-send controls.

The common failure is treating each source event as independent when several systems describe the same person or address. A form submission, list import, and owner assignment may all look new. A duplicate-send prevention rule gives the workflow a way to pause and review before mailing twice.

How should teams measure new-lead direct mail?

Teams should measure new-lead direct mail with campaign IDs, batch IDs, mailed counts, held counts, response sources, mailstream signals, and a declared measurement window. A later response should not be treated as automatic proof that the postcard caused it.

New leads often receive email, calls, ads, texts, and sales follow-up at the same time. Keep measurement modest and traceable: what was mailed, when it entered the mailstream, what response paths were watched, which records were held, and which assumptions remain unresolved. For measurement boundaries, see the measurement window guide and the direct mail attribution guide.

What should a Sendvo-style workflow keep visible?

A Sendvo-style workflow should keep the source event, lead key, address state, suppression result, duplicate-send decision, proof version, campaign ID, batch ID, tracking fields, and review state visible together before release.

Sendvo is in beta, so product wording should stay capability-framed. The operational pattern is stable: when software connects a lead event to physical mail, the workflow needs a traceable record from source event through proofing, batching, mailstream tracking, and later review.

FAQ

What is new-lead direct mail?

New-lead direct mail is a postcard or letter sent after a new lead enters a source system or qualifies for mailed follow-up. A safe workflow records the source event, recipient key, address state, suppression result, duplicate-send window, proof version, campaign ID, batch ID, tracking fields, and measurement window.

Is new-lead direct mail the same as triggered direct mail?

New-lead direct mail is one type of triggered direct mail. The trigger is a new lead event or qualification rule, while triggered direct mail can also start from other events such as cart activity, customer milestones, inactivity rules, or source-system state changes.

What should teams check before sending a new-lead postcard?

Teams should check the source event, lead identifier, mailing address, suppression rules, duplicate-send window, proof version, variable fields, send window, campaign metadata, and measurement plan before release. Records with missing address or unclear eligibility should be held for review.

What is new-lead direct mail?

TL;DR