Send · Senders

Cold volume spends a dedicated domain, never your company mailbox

A sending domain is a real connection row: pending until its DNS verifies at the vendor, with the records, the bare domain and the reply-to mailbox stored on it. A sender is one from-address on that domain. Rotation, daily pacing, workspace isolation and the age ramp all apply per address, because that is the unit a reputation attaches to.

Talk to sales See pricing

GTM

MWMy workspaceworkspace

SendersSearch/14,208

go.example.comVerifiedSPF · DKIM · DMARC

priya@go.example.com41/50

62 days old · today’s ceiling comes from the age band

hello@go.example.comRamping27/50

31 days old · today’s ceiling comes from the age band

team@go.example.comRamping25/25

9 days old · today’s ceiling comes from the age band

sales@reach.example.comRamping6/10

2 days old · today’s ceiling comes from the age band

What is actually going on

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

Verification is a live call, not a saved string

Saving checks the credential against the vendor's own API before the row reads as connected. A card that says connected means something that worked once against the real endpoint.

A client workspace is a container

The launcher considers only the queue row's own workspace's connections plus the org-level shared pool. Outreach can never leave through another client's identity.

The launcher parks rather than improvises

If no verified sender exists for a row, it parks with a plain reason. It does not quietly fall back to something else and it does not fail silently.

Health is asked, not assumed

A six-hourly job asks the vendor whether each domain still verifies and resets the daily and weekly counters, so a card degrading is something the product noticed rather than something you discover from a bounce.

Step by step

How sending domains & senders runs

1
Attach
Enter the subdomain. The vendor returns the records.
2
Publish
Add the records at your DNS provider.
3
Verify
One click, one live check. Pending until it passes.
4
Rotate
Add senders. The launcher picks one per send, inside the ramp.

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.

SendSenders

Domain: A subdomain, never the root
Receiving: Enabled at attach, so replies land
Row per: From-address, not per domain
Health check: Every 6 hours
Ramp anchor: account_warmed_at, else connected_at

Sending domains & senders, honestly

Why a subdomain rather than my main domain?

So that a bad week of cold volume cannot damage the reputation your invoices and password resets depend on.

How many senders should I run?

Enough that your daily target divided across them sits inside each one's ramped ceiling. The senders screen shows the effective limit per address rather than making you compute it.

Send

Out through your own accounts, at a safe pace

Every feature

Email & LinkedInTwo channels, two vendors, one each, and honest about the limitsOpen Warmup & deliverabilityAn enforced ramp, real warmup traffic, and an honest account of its limitsOpen SequencesEmail first, then LinkedIn the same day. One entry, one chainOpen

Keep reading

All features

DeliverabilityWarmup & deliverabilityAn enforced ramp, real warmup traffic, and an honest account of its limitsRead more ChannelsEmail & LinkedInTwo channels, two vendors, one each, and honest about the limitsRead more ComplianceThe pre-send gateThe last thing before a send, and the database agreesRead more

Sending domains & senders 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.