Do not contact
Do not contact rules suppress future outbound messages across channels.
Do not contact is the workspace suppression ledger for outbound work. Use it when a person, a company, an email domain, a phone number, a LinkedIn identity, or an X handle must not receive a future outbound message.
The ledger belongs to the senders pack, while a Sequence determines the cadence and the Inbox holds an existing conversation. Read Senders and mailboxes before configuring sender capacity, and read Sequences and enrollment before starting outreach.
What a stop means
A suppression stops future sends and outbound channels for the stored identifier. The sender policy covers an email address, an entire email domain, a phone number, a company, a LinkedIn identity, or an X handle, so the scope depends on the identifier you add.
This is not a mailbox pause and it is not a warmup setting. Listing suppressions never changes mailbox pause or warmup, which makes the list safe to inspect before changing any outreach plan.
A reply, bounce, unsubscribe, suppression, decline, wrong person, and a finished conversation each end outreach to that person across channels. Do not use another sender, another sequence, or another channel to work around one of those stops.
A stop also does not send a reply. When a send result or stop result is unclear, read the current conversation and the current sequence state before retrying. A conversation status alone is not evidence that a message was delivered.
Choose the right scope
Use an individual email address, phone number, LinkedIn identity, or X handle when one contact must be excluded. Use a domain when no address at that domain should receive outbound email, and use a company when every prospect at that company must remain excluded.
The workspace-wide list capability returns entries by email, domain, company, phone, or LinkedIn identity. The focused list capabilities separate email addresses, domains, companies, phones, LinkedIn identities, and X handles when you need to audit one kind of entry.
A company-level entry is broader than an individual contact entry. If only one person asked not to hear from you, a company block would exclude other prospects at that company too. If the whole organization has opted out, a company block matches that policy better than many individual rows.
The system normalizes do-not-contact rows. Writes converge on a unique normalized row, and a repeated delete remains safe when the row is already absent. That behavior helps an agent recover from a retry without creating duplicate blocks.
| Identifier | Use it when | Outbound consequence |
|---|---|---|
| Email address | One address must not receive email outreach. | Future outbound delivery is suppressed for that identifier. |
| Domain | Every address at one domain must be excluded. | Outbound email is stopped for addresses at that domain. |
| Company | The whole company must remain excluded. | Prospects at that company stay excluded. |
| Phone, LinkedIn, or X | A channel-specific identity must not receive outreach. | The matching outbound safety gate excludes that identity. |
Add and import rows
Architect can add one identifier or prepare a review of the current ledger. It uses the same capability catalog that is available through the other product surfaces, so it first discovers the exact schema before it writes a row.
For a prepared list, import parsed CSV rows with senders.suppressions.import. One request adds up to 500 rows. For a worksheet, use senders.suppressions.import_from_worksheet to add normalized values from selected Dreamstate worksheet columns.
A CRM import copies selected list-member identifiers into the local ledger and does not write back to the CRM. A saved CRM sync can add new members automatically, and its controls can list sources, list saved syncs, create or update a sync, pause or resume it, request immediate processing, or stop the sync. Stopping a sync does not remove the entries it already blocked.
Use a worksheet import when the source of truth is a Dreamstate workbook. Use a CRM import or sync only after checking the connected list and filter. The sender pack owns the ledger, while the integrations pack owns a third-party connection behind a provider.
List the current do not contact entries for this workspace. Add jane@example.com as an email suppression, then show the result without changing any sender settings.Review before a send
Before a live outbound run, inspect sender health, sending hours, cooldowns, daily caps, suppressions, and remaining headroom. Drafting, previewing, and validating can happen without an email or LinkedIn account connected, but a missing account blocks sending on that channel.
Send capacity is paced over days rather than minutes. A capped cell or delayed send is pacing, not necessarily a failure. Check the intended channel and the stored suppression before changing a sequence, because changing channels cannot bypass a stop.
For a sequence plan, the useful evidence is the current suppression list, the recipient's existing thread, sender health, and the selected sequence state. A sequence's outcome reporting distinguishes sent, replied, bounced, unsubscribed, and failed totals, so use those states to investigate what happened rather than inferring delivery from a draft.
Do not contact writes are synchronous, have no credit charge, and make an internal reversible change. Listing entries is synchronous, read-only, and has no side effect. These properties do not make the policy unimportant: the write changes the people an outbound plan may reach.
When it goes wrong
If an enrollment reports suppressed_or_do_not_contact, the recipient is blocked by the sender safety check. Read the matching suppression list, confirm the identity and scope, and keep the sequence stopped for that recipient while the workspace resolves the policy.
If the blocker is no_connected_sender, missing_email, or missing_linkedin_url, fix the sender or recipient data instead of changing the suppression record. A missing connection blocks running or sending the affected step, not the ability to build the sequence.
If an import is larger than 500 parsed CSV rows, split it into bounded requests. If a CRM sync is unexpectedly adding entries, list the saved sync and the available CRM source, then inspect the selected list or filter. Removing a saved sync leaves existing blocks in place, so review those rows separately when the policy changes.
If a person replies, declines, bounces, or unsubscribes after an earlier outreach attempt, do not restart the sequence through another channel. Read the full current thread. For an unsubscribe or decline, do not pitch and confirm that the relevant suppression is present.