Skip to content
Wrenwire
Docs

Getting ready to send

Before your first message sequence goes out, you need the sending side in place: a separate domain, a personal mailbox on that domain, three DNS records, a Snov.io account with the mailbox connected, and a few weeks of warm-up. This page walks you through it in order. The sections follow the steps of the Getting ready to send part of the setup checklist in the app, where you mark what is already done. The later steps of that part are not described here: your existing contact list, the company name of the data controller, and the first send.

Start here even if your campaign is not ready yet. The mailbox warm-up takes the longest, about three weeks, and its clock only starts once the mailbox exists and is connected. You can write your campaign content in the meantime.

The instructions below follow the Google Workspace path. On Microsoft 365 you do the same steps using Microsoft’s documentation, linked in the relevant sections.

Sending domain

Cold outreach goes out from a separate domain and a separate mailbox, never from your main company domain. If deliverability goes wrong, and early on that is easy, your main domain stays clean and your everyday company email is unaffected.

  1. Buy a domain for cold outreach. A .com, .eu or your country’s domain is fine, as long as it is not your main company domain.
  2. Keep it close to your brand so the address still looks like you, for example try-acme.com or get-acme.com.
  3. Enter it in the setup checklist under “Dedicated sending domain” and save. From then on the app can check its DNS records for you.

Sender mailbox

The sender mailbox has to be a personal one, for example jane.smith@try-acme.com, never a generic info@ or contact@. Generic mailboxes read like a machine rather than a person writing an email, and they deliver worse.

Add the sending domain to the Google Workspace you already have, as a secondary domain. Do not set up a new Workspace for it, and do not add it as a domain alias: an alias only forwards mail to your existing mailboxes, and cold outreach needs mailboxes of its own.

  1. Add the domain. Sign in to admin.google.com as a super administrator, then go to Account, Domains, Manage domains, Add a domain. Type it without https:// and without www, and choose Secondary domain.
  2. Prove you own it. Add the google-site-verification=… TXT record Google gives you in your DNS panel, with Host set to @ or left empty. Then click Verify in the Google admin console.
  3. Point the mail at Google. Remove the old MX records if nothing uses them, and add MX smtp.google.com with priority 1 on Host @. Then click Activate Gmail for the domain. A DNS change can take up to 72 hours to propagate.
  4. Create the mailbox. Directory, Users, Add new user, with a personal address on the new domain. Sign in to it once through gmail.com, accept the terms, then send and receive one test message.
  5. Enter that address in the setup checklist under “Sender mailbox on the sending domain” and save.

On Microsoft 365, add the domain and create the mailbox by following Microsoft’s instructions.

Domain authentication (SPF, DKIM, DMARC)

Three TXT records tell the receiving servers that mail from this domain really comes from you. You add them in the DNS panel at your domain registrar.

Record Host Value
SPF @ v=spf1 include:_spf.google.com ~all
DKIM google._domainkey the key generated in the Google admin console
DMARC _dmarc v=DMARC1; p=none; rua=mailto:dmarc@your-domain
  • DKIM: in the Google admin console open Apps, Google Workspace, Gmail, Authenticate email. Generate a key (2048 bit is recommended), add the TXT record Google gives you, then click Start authentication. The selector is google unless your provider gives you a different one.
  • DMARC: the address in rua has to be a mailbox that exists, because reports are sent to it. Start at p=none. Tighten the policy to quarantine or reject only once you can see that your regular mail passes SPF and DKIM.

Once the records are in DNS, use Check now on the “Domain authentication” step of the setup checklist. For that step, p=none is enough. If a record does not show up yet, check again later: a change can take up to 72 hours to become visible.

On Microsoft 365, DKIM uses the selectors selector1 and selector2, described in Microsoft’s instructions.

Snov.io account and plan

The sending itself is done by Snov.io: it holds the mailbox, the prospect lists and the message sequences Wrenwire hands over to it. It is a separate subscription with its own payment, outside your Wrenwire plan.

  1. Create an account at snov.io. Referral link: if you sign up through this link, we receive a commission from Snov.io. Your price does not change; you can also sign up directly at snov.io.
  2. A free account is enough to begin with. You can start the mailbox warm-up on it.
  3. The free account caps out at roughly 450 emails in total and does not renew, so it usually does not cover a full three weeks of warm-up. It also has no access to the Snov.io API. Take a paid plan before you start sending a campaign or searching for contacts in the Snov.io database through Wrenwire. The cheapest one is enough to start.
  4. If your message sequences use LinkedIn, add a LinkedIn seat to the plan. It is a paid extra.

In the setup checklist these are two separate steps. “Snov.io account” is the one you tick here; “Snov.io plan” comes later, after the mailbox warm-up, because that is when the plan is really needed.

Connecting Snov.io to Wrenwire

Wrenwire works inside Snov.io on your behalf. You hand over your logged-in session once, using a small Chrome extension. The extension is not in the Chrome Web Store, so you load it yourself.

  1. Download the extension package from the Snov.io settings screen in the app and unzip it.
  2. Open chrome://extensions in Chrome and turn on Developer mode (top right).
  3. Click Load unpacked and pick the unzipped folder.
  4. Log in at app.snov.io in the same browser.
  5. Click the extension icon and choose Send session. The “Snov.io connection” step in the setup checklist turns green as soon as the session arrives.

Chrome will warn you about an extension running in developer mode. That warning is about how the extension was installed, not about what it does.

Sender mailbox in Snov.io

Snov.io needs at least one connected mailbox before it can send anything. The app cannot check this for you, because whether the mailbox is connected is only visible inside Snov.io. Connect the mailbox you created under Sender mailbox.

  1. Turn on 2-step verification for that mailbox’s Google account: Google Account, Security, 2-Step Verification.
  2. Create an app password at myaccount.google.com/apppasswords and call it Snov.io. Snov.io uses this password, not the password to the account.
  3. Turn IMAP on: Gmail, Settings, Forwarding and POP/IMAP, enable IMAP.
  4. In Snov.io open Email Accounts, Add email account, Gmail (SMTP). Use the app password. For IMAP use imap.gmail.com, port 993, SSL. Then Check connection and Add account.
  5. Add the same mailbox once more through Add email account, signing in with Google.

After step 5 you will see two entries for the same mailbox: one from the Google sign-in and one for SMTP/IMAP. That is expected, not a duplicate to clean up.

Mailbox warm-up

A new domain and a new mailbox need about three weeks of gradually increasing activity before real sending starts. Rushing does harm here: a mailbox with no history that sends a lot from day one easily ends up in spam.

  1. Turn the warm-up on for the mailbox in Snov.io (or in whatever tool you use for it) and leave it running.
  2. In the setup checklist, start the countdown on the “Mailbox warm-up” step. Snov.io does the warming up itself. Wrenwire counts the days and tells you how much you can send per day.
  3. Keep building your campaign content in the meantime. Nothing blocks that, only the sending waits.

While the countdown runs, starting an email campaign is locked. If the domain has genuinely been sending email for months, you can say so on that step.

Daily sending limit

Snov.io sends as much as you let it. A safe daily sending limit protects the reputation of a warmed-up mailbox.

  1. Set about 50 emails per mailbox per day in Snov.io.
  2. If you use LinkedIn, keep to about 50 invitations a day there as well.
  3. While the mailbox warm-up runs, follow the daily number on the warm-up card in the setup checklist instead. It is lower on purpose.

These numbers are a starting point, not a delivery guarantee. Deliverability also depends on your content, your recipient list and the history of the domain.

Who you may contact, and on what basis

This page covers the technical side. Who you may contact in a given market, and on what legal basis, is covered on the Compliance page and the market pages it links to.