Know when your outreach is ready to send.

Name the audience, business purpose, offer, source of account relevance and intended channel. Record the sender identity, reply owner and the action a recipient is being invited to take. The connected outbound campaign guide connects that message to account research, sales follow-up and measurement.

A new vacancy, expansion announcement or other buying signal can explain why an account deserves review. It does not establish permission to contact a person or prove that the account is ready to buy. Keep the signal as dated evidence within the campaign decision.

Identify who authorises activation and what they must see first. A working integration is one part of that record. Do not make “mailbox connected” the event that automatically starts sending to a list.

Document the source of contact details, the relevant markets, recipient types and relationship context. Name who determines the applicable rules and what evidence the campaign keeps. An email address found publicly or returned by an enrichment service is a data point, not a permission record.

Regional and recipient distinctions matter. The UK ICO’s B2B marketing guidance distinguishes corporate subscribers from sole traders and some partnerships, and states that personal-data obligations can still apply. The page is under review following legislative changes; check current guidance for the actual markets and campaign before activation.

Keep the decision and its date with the campaign. If a recipient’s type or applicable rule is unclear, hold that recipient for the responsible review rather than treating uncertainty as approval. Rules established for one market should not be copied to another simply because both audiences are B2B.

List the domains, mailboxes and services that will send on the organisation’s behalf. Confirm who owns them, who can change their configuration and where replies arrive. The visible sender, message content and reply destination should accurately identify the organisation responsible for the outreach.

Check authentication against the actual sending services. Record the status and evidence for SPF, DKIM and DMARC as applicable, alongside DNS, transport and message-format requirements. A copied DNS value or a provider’s setup screen is not enough evidence if the actual test message fails the relevant check.

Google’s current sender guidelines apply to personal Gmail accounts and distinguish all-sender requirements from additional bulk-sender requirements. They include authentication and delivery controls, with one-click unsubscribe requirements for relevant bulk marketing and subscribed messages. Check the live requirements for the actual sending pattern; these technical rules do not grant permission to contact someone or guarantee inbox placement.

Keep exclusions and opt-outs effective across the tools used by the agreed campaign. Test that a suppressed contact cannot re-enter through a fresh import, enrichment result, duplicate account record or a retried step. Retain the information needed to honour the decision under the organisation’s retention arrangements.

The CRM enrichment evaluation should check whether new data can overwrite or bypass an existing exclusion. A new address for the same person or company may require review; it is not automatically a fresh invitation to contact them.

Test replies, out-of-office messages, delivery failures and a request to stop. Identify which need an immediate pause, which become a task and who covers the owner’s absence. Use authorised controlled destinations for readiness testing, with no real prospect records or automatic customer messages in a demonstration.

Once the evidence is complete, the named authorised person can approve the agreed first stage. Define that stage by a reviewed group, relevant timing and the team’s capacity to monitor and respond. No universal daily volume or warm-up schedule can replace the requirements of the actual provider, audience and campaign.

Recheck exclusions at the point of sending. Keep a record of the campaign, message version, intended recipient and resulting send status so a retry can be reconciled. An uncertain provider response should trigger checking, not an automatic second message.

Keep the pause control accessible to the responsible operator. Changes to the sender, source, recipient rules, message purpose or system connections may require another readiness review. Keep the approval with the readiness record so a later operator can see exactly what was authorised.

Record delivery failures, deferrals, complaint information where available, opt-outs and replies alongside the provider’s current limits and monitoring definitions. Decide in advance who investigates a change and which conditions pause the campaign. A low complaint count should not be treated as proof of relevance or permission.

Review replies in their sales context: interested, wrong person, not relevant, later timing or stop request. Preserve the recipient’s meaning rather than reducing every response to a positive-engagement count. A delivered message is not evidence of a qualified opportunity.

Use the monthly commercial review to separate reliability, team use and commercial progress. Keep raw counts and the observation period visible before deciding whether to adjust the message, audience or handover.

Keep one operating record for the agreed campaign: dated policy references, technical evidence, recipient decisions, suppression rules, approvals and recovery instructions. Name the people responsible for access, configuration, replies and changes. Store credentials in the approved access system, outside the campaign brief.

The tools and agents guide helps connect the existing tools around this work. A Build campaign includes agreed planning, setup, operation and improvement. Define readiness checks and reply responsibilities with the team that will run it. Run is optional continuation after Build; ongoing review during the initial campaign belongs in Build’s agreed scope.