Sender Infrastructure Provisioning (Onboarding)

Sender Infrastructure Provisioning (Onboarding)

1. 01

   Confirm the client's legal basis for outbound before buying a single domain

   Jurisdiction determines whether opt-out language, sender identification, or prior-consent rules apply. Get the answer in writing from the client's counsel or compliance lead, not from the sales rep who signed the retainer.

2. 02

   Register secondary domains that are distinct from the client's primary brand domain

   Agencies running cold volume on the main corporate domain put the client's transactional and support email at risk. Keep the primary domain clean and treat outreach domains as consumable inventory.

3. 03

   Configure SPF, DKIM, and DMARC on every sending domain before the first message leaves

   Saleshandy auto-configures these records in under 10 minutes, which is the benchmark to hold any vendor to. If setup takes an afternoon of DNS tickets, the tool is the wrong fit for a multi-client agency.

4. 04

   Decide between shared vendor infrastructure and private isolated sending

   Aerosend isolates every 10 domains on dedicated servers with aged IPs, while most platforms pool reputation across tenants. The choice changes both monthly cost and how much deliverability risk the agency absorbs on the client's behalf.

5. 05

   Cap mailboxes per domain and per sending IP, then document the cap in the client's delivery plan

   Write the number into the retainer scope so a later volume request becomes a change order rather than an argument. Caps are the cheapest deliverability control an agency owns.

6. 06

   Run warmup for the full ramp window before any campaign goes live

   Woodpecker and PlusVibe both bundle warmup into the base plan, so the constraint is patience rather than budget. Starting a sequence on day three of a 21-day ramp is the most common self-inflicted deliverability failure.

7. 07

   Set up bounce, spam-complaint, and domain-burn alerting routed to a named owner

   Aerosend monitors five metrics for burn signals. Whatever the platform, the alert needs a human on the other end within the same business day, not a dashboard nobody opens.

8. 08

   Record the full provisioning state in the client handoff file

   Domains, DNS records, mailbox counts, warmup start dates, and alert thresholds belong in one document. When the account moves between delivery pods, that file is the difference between continuity and a rebuild.