Run it · Compliance

Choose your review mode. Sending checks always apply.

Intent fires, the entry rule matches, and the sequence runs. What was removed is a hold, not a check. The queue in front of the gate asked a person to re-approve a draft the product had already written from evidence it had already gathered. The gate itself is untouched, and it is enforced one layer below the code.

Talk to sales See pricing

OutboundSearch/14,208

Outbound row · pre-send evaluation

JurisdictionUS · CAN-SPAM

Entity typeBusiness contact

Lawful basisLegitimate interest, documented

SuppressionNo match at workspace or platform scope

Unsubscribe URLInjected by the transport

Postal addressInjected by the transport

Verdict: allow. Written to the row before the send.

messages_outbound_sent_was_gated. A row cannot reach sent without a verdict and an unsubscribe URL.

What is actually going on

Every claim below is followed by the mechanism under it, because a claim without a mechanism is a slide.

A database constraint, not a code path

An outbound row cannot reach sent without a gate verdict and an unsubscribe URL. A bug in the launcher fails as a constraint violation rather than as a delivered email.

The footer is appended by the transport

Unsubscribe link and postal address are added where the send happens, not by the caller. A caller able to omit them eventually will.

Jurisdiction × entity type × lawful basis

The verdict is computed per row, not per campaign, because the answer depends on who the person is and where they are.

Suppression survives everything

At workspace and at platform scope, exempt from every retention purge. A suppression list that a purge could empty is a list that eventually mails somebody who asked you not to.

Step by step

How the pre-send gate runs

1
Evaluate
Every outbound row gets a verdict before anything leaves.
2
Inject
The transport adds the unsubscribe URL and the postal address.
3
Enforce
The database refuses a sent transition without both.
4
Record
The verdict is stored on the row, so what happened is answerable later.

The numbers

Facts, not adjectives

Every figure here is a real value from the running product. A cadence from the scheduler, a price from the credit table, a limit from the ramp. A marketing page that invents a limit is a support ticket with a delay on it.

Run itCompliance

Enforcement: Database constraint, not application logic
Inputs: Jurisdiction, entity type, lawful basis
Injected: Unsubscribe URL, postal address, notice
Suppression scope: Workspace and platform
Purge exemption: Total

The pre-send gate, honestly

Can an agent argue its way past the gate?

No. Not arguing with the gate is in the hidden platform layer that sits above every editable prompt, and the gate is not a model call in the first place.

Can I turn off the unsubscribe footer?

No. It is platform-injected and not disableable, which is the deliberate cost of sourcing leads ourselves rather than only processing yours.

Run it

The team that does all of the above

Every feature

The agent rosterFive roles, one per job. Find, qualify, write, send, checkOpen The agent screenType a sentence; it becomes tool calls against an allowlistOpen InsightsThe funnel, what went out, what came back, and who found themOpen MCP & APIDrive your workspace from Claude, with your own scopesOpen

Keep reading

All features

The rosterThe agent rosterFive roles, one per job. Find, qualify, write, send, checkRead more DeliverabilityWarmup & deliverabilityAn enforced ramp, real warmup traffic, and an honest account of its limitsRead more SequencesSequencesEmail first, then LinkedIn the same day. One entry, one chainRead more

The pre-send gate is one part of it. The rest runs too.

Sourcing, enrichment, intent, copy, sending, replies and reporting are one product with one bill and one gate. Connect a channel and the whole motion starts.