Cold email outreach: how to reach the inbox and get replies.

What cold email is, and why it is not spam

A cold email is a message to someone you have never been in touch with, sent to start a conversation about a problem they probably have. Cold email outreach runs it as a method: a list of people picked for a reason, a short first email, a few follow‑ups and a quick answer to whoever writes back.

What separates it from spam is who it goes to and why. Each email goes to a person you chose for a reason you can name, it is about their work, it comes from a real person, and it lets them say no in one line. Two hundred people who fit usually start more conversations than five thousand who might, and your domain will still be in good shape when the campaign ends.

It is also regulated, and the rules depend on where your recipients are. In the US the CAN-SPAM Act "makes no exception for business-to-business email" (FTC, CAN-SPAM Act compliance guide, August 2023). In the EU and the UK, GDPR and national rules apply: you need a lawful basis to use a person's data, and some countries ask for consent before a marketing email, even to a work address. Check the rules for each country you write to, and ask a lawyer when in doubt. Under CAN-SPAM, every email needs:

• A true sender name and a subject line that matches the email
• A clear statement that the email is an ad
• Your postal address
• A way to opt out, honored within 10 business days

In GetSales you describe your buyers in one sentence, typed or said, and AI Search turns it into filters you can read.

The right people, and every address checked

Write down who you sell to before you search: the role, the company size, the industry and the problem you solve. Then add a reason each company might care now, such as a new sales hire, a new office or a round of funding. A list built that way is shorter, and every name on it has a first line waiting. Take out your customers, your open deals and anyone who opted out before.

Then check every address before the first send. Mail to an address that does not exist bounces, and each bounce counts against the mailbox that sent it. Most cold email guides say to keep bounces under 2 percent. A verifier sorts the list into addresses that are deliverable, addresses on a catch-all domain (one that accepts every message, so nobody can tell if the person exists) and addresses that failed. Send to the first group, think twice about the second and drop the third.

Write to work addresses. A sales pitch in someone's personal inbox is easier to resent and harder to justify.

In a GetSales table, pick a verifier and each address is checked before it lands, and an address that bounced, unsubscribed or complained is not sent to again.

Set up the domain and the mailboxes first

Deliverability comes before copy: an email in the spam folder has no subject line worth testing. Many teams send cold email from a second domain that looks like their main one, such as yourcompany.co beside yourcompany.com, so a bad week hurts that domain and not the one the company runs on.

Authenticate every sending domain with SPF, DKIM and DMARC. SPF lists the servers allowed to send for the domain, DKIM signs each message, and DMARC tells the receiving server what to do when a check fails. Since February 2024 Gmail asks every sender for SPF or DKIM and a spam rate under 0.3% in Postmaster Tools, and asks bulk senders for all three (Google, Email sender guidelines, read October 2026).

Then go slowly. A new mailbox that sends a few hundred emails on its first day looks like what it is. Each provider sets its own limits, and a cold mailbox should sit far below them. The setup, in order:

1. Buy a second domain close to your main one and point it at your site
2. Add the SPF, DKIM and DMARC records, and check that they pass
3. Create two or three mailboxes on it under real people's names
4. Warm them up for a few weeks, starting with a handful of emails a day
5. Spread each campaign over several mailboxes instead of pushing one

GetSales sends from your sender profiles' own mailboxes on Google Workspace, Microsoft 365 or IMAP and SMTP, and sending spends no credits.

One short email, one reader, one reason

Write the first email for one person. Open with something true about them or their company, the reason you picked them. Say in one sentence what you do about the problem that reason points to, and ask one question they can answer in a line. That is the whole email: three or four sentences, readable on a phone without scrolling.

Personalize past the first name. A greeting with their name over a template still reads as a template. A line about their hiring, their new office or a post they wrote shows you looked, and it decides whether the rest gets read. The best reasons are recent ones, such as a job change or a second visit to your pricing page. In GetSales, Signals shows who changed jobs and, on a site switched to People, who came back to your pricing page.

Keep the subject short and plain, like a note from a colleague: two to four words, no capitals, no hype. Leave out images, attachments and any second link. Ask for a reply, not a meeting: "Worth a look?" is easier to answer than a request for 30 minutes on Tuesday. Three to start from:

In GetSales the email takes a first line written from each person's own row, and a variable with no value and no fallback fails that send by default instead of going out with a gap.

Follow up in the thread, and stop on a reply

Most replies come to a follow‑up, not to the first email. A busy reader sees the first one, means to answer and forgets. Write the follow‑ups before you send anything, two to four of them a few days apart, each short and each with something the last one did not have: a detail, a one-line case, a simpler ask. Most guides put the whole sequence at three to seven emails.

Send each follow‑up as a reply in the same thread, so the reader sees your first email under it and you never repeat yourself. And stop the moment someone answers, whatever the answer: a follow‑up after "not now" is how a cold email turns into a complaint.

Send on working days, in the reader's working hours. Past that, the studies on the best hour disagree, so test on your own list. In GetSales you pick the days and hours a workflow sends, and with Follow the person's timezone on, 9 means 9 where they are, when their zone is known.

In a GetSales workflow a follow‑up is a Send email step after a wait. It replies under the previous email by default, and by default a reply pauses the follow‑ups.

Add LinkedIn between the emails

An email from a stranger is easy to ignore. The same name in a connection request a few days later is harder to. Most cold email guides stop at the inbox, but your reader also has a LinkedIn account, and a second channel gives a quiet campaign another way in without a fifth email in the thread.

Keep the shape simple. Visit the profile, send a connection request with a short note or none, and wait a few days for the accept. Those who accept get a LinkedIn message that picks up where the email left off. Those who do not get the next email. Send both from the same person, so the request carries the name they saw in their inbox.

LinkedIn sets its own limits on requests and messages, and they differ from account to account, so pace the requests and withdraw the ones nobody answers. A plan for ten days:

1. Day 1: the first email
2. Day 3: a profile visit and a connection request, a short note or none
3. Day 6: a LinkedIn message to those who accepted, the next email to the rest
4. Day 10: the last email

One GetSales workflow holds both channels: a wait for the accept splits the people, those who accept get a LinkedIn message, the rest get an email, from the same sender profile and paced within each account's limits.

Answer while they are warm, and count replies

A reply is the point of the whole campaign, and it cools fast. Someone who wrote "send me more" at ten is still thinking about it at half past and has moved on by tomorrow. Answer the same hour if you can, the same day at worst. Put every reply where the team will see it, not in five mailboxes nobody opens after lunch.

Sort the replies as they come. An interested one gets an answer and a time. A "not now" gets a note in the calendar for when they said. A wrong person gets a thank-you and a question about who is right. An unsubscribe comes off every list at once.

Judge the campaign by replies, and better by positive replies and meetings. Opens say little: Apple Mail Privacy Protection loads an email's remote content in the background, so an open count includes emails nobody read (Apple, read October 2026). Guides in 2026 put typical cold email reply rates between about 1 and 6 percent. Below that, look at the list and the first line before you touch the subject. In GetSales each sending step shows what it sent, who replied and the rate.

In GetSales each person has one thread in Unibox, LinkedIn and email together, where the AI SDR drafts each answer and each scenario sets whether it sends on its own or waits for your OK.

The whole campaign from one sentence

Done by hand, the method takes a handful of tools: a database for the list, a finder and a verifier for the addresses, a spreadsheet for the first lines, a sequencer for the emails, another for LinkedIn and an inbox for the replies. It works. It also means an export and an import between each step, and every handoff is a place where a bounced address or an opt-out goes missing.

In GetSales the people come from AI Search into a table, a workflow reaches them on LinkedIn and email, and the replies land in Unibox, where the AI SDR drafts the answer. By hand or not, go down this list before the first send:

• Who you sell to fits in two sentences
• Every address is checked, and customers and opt-outs are out
• The domain passes SPF, DKIM and DMARC, and the mailboxes are warm
• Each first email has a reason that is about the reader
• The follow‑ups are written, and a reply stops them
• Every email carries your postal address and a way to opt out
• Someone owns the replies, the same day

Say who you sell to, out loud or typed, and Creator plans the search, the table, the work emails, the first lines, the workflow and the AI SDR, then asks before anything starts.