Solutions · Agencies

Outbound for agencies and consultancies

An agency's constraint is not finding prospects — it is running several sending domains at once without one client's bad month damaging another's, while producing reporting a client will believe. That is a deliverability and record-keeping problem before it is a prospecting one.

What this team is actually trying to do#

  • Keep each client's sending domain separate, and its reputation with it.
  • Show a client what actually happened, not a delivery percentage.
  • Stop a campaign automatically before a client's domain is damaged.
  • Send the retainer for signature and invoice it without leaving the record.

Isolation is the whole job#

The failure that ends agency relationships is contamination: a list imported for one client bounces, the mailboxes it burned were shared, and a different client's mail starts landing in spam. Reputation is earned per domain and per mailbox, so isolation is achieved by structure, not by care.

That means each client's mail leaving its own domain and its own mailboxes, with its own caps, ramp and health score — and a failure in one pool costing that client volume and nobody else.

Reporting a client will believe#

Delivery rates are the number most agency reports lead with, and they are close to meaningless — a message filed in spam is delivered. Clients who have been burned once know this, and a report built on it reads as evasion.

The defensible version is narrower and more persuasive: what was sent, what bounced, what was complained about, what replied, and — for mailboxes you can actually read — where test mail landed and when it was checked. Fewer claims, all of them checkable.

Automatic stops protect the relationship#

A client's domain is an asset you have borrowed. The worst outcome is not a slow month; it is handing back a domain that filters worse than when you started, which no amount of pipeline compensates for.

Automatic pauses on bounce and complaint thresholds are what make that outcome unlikely without requiring anyone to be watching on a Friday evening. They cost volume on the day they fire, which is the correct trade.

The commercial paperwork is part of the workflow#

Agencies produce more contracts and invoices per unit of revenue than almost anyone, and they usually produce them somewhere else — which is how a signed scope ends up disconnected from the pipeline that produced it.

Quote approval into an invoice, and e-signature with an audit trail, sitting on the same record as the deal, removes a whole category of month-end reconciliation.

What carries the workflow#

Sending identities per domain
Mail leaves the mailboxes you connect, each with its own weight, daily cap, ramp and health score — so one client's pool is scored and paused independently of another's.
Domain authentication checks
SPF, DKIM, DMARC, MX and blocklist status per sending domain, each answer timestamped, with cached results labelled as cached rather than presented as fresh.
Placement testing with history
Seed-list placement tests, kept as a series so a slow drift is visible. Folder placement is reported only for seed mailboxes you have connected — the case where it can actually be observed.
Automatic pauses
A mailbox pauses at a 0.3% complaint rate with at least two complaints, or a 5% bounce rate with at least five bounces, and only a person can resume it.
Retainers signed and invoiced
E-signature with a content hash and per-event audit records, quote approval into an invoice, and PDFs — all on the record the work sits on.

Every one of these is documented at /docs.

Questions#

Yes. Outbound leaves the mailboxes you connect, so each client's mail goes out over its own domain and identities, with its own caps, ramp and health score. Reputation is built and scored per mailbox and per domain.

Terms used on this page#

Go deeper#

Other kinds of team#

Run it on one record

Signals, prospect search, sequences, deliverability, pipeline, e-signature and invoicing.