Cold email first line examples for SDRs: open on the prospect’s own problem

The best cold email first line examples open on a problem the prospect’s own customers met, such as “I signed up to your store on Monday, and your welcome email arrived 7 hours later.” A compliment on a podcast can now be drafted for every rep at once, while a line about the prospect’s own emails is true of one company. Obsession keeps what each company on your list shows only to its customers, dated with a screenshot, by API, MCP (the standard way AI agents call tools) or a table.

Cold email first line examples that earn replies open on a problem the prospect’s own customers met this week, seen by signing up as one of them. “I signed up to your store on Monday, and your welcome email arrived 7 hours later” is true of one company. The prospect can check it in a minute, and it names the problem an email platform fixes.

Most advice on first lines teaches the compliment: a podcast episode, a funding round, a LinkedIn post. AI research agents now draft those for every row of a list. Clay’s page for Claygent, its research agent, offers the sample prompt “Write a personalized email copy based on recent news and job postings from this company’s website.” When every sales development representative (SDR) can produce the same compliment in one step, the prospect reads it as a template.

A fact about the prospect’s own company still works. Gong Labs analysed more than 30,000 prospecting emails from more than 250 companies, and found that “engaging executive buyers (directors and above) using a company-specific topic triples prospecting email reply rates”. It also warns that “irrelevant personalization still falls flat”. The first email carries most of the result. Instantly’s Cold Email Benchmark Report 2026 covers its users’ sending from January to mid-December 2025. It puts the average reply rate at 3.43%, and the top 10% of senders at 10.7% or more.

What makes a personalized cold email first line work

The first line is the sentence after the greeting, and most inboxes show it as preview text beside the subject line. A personalized cold email first line works when it passes 4 tests.

• It is a dated fact about the prospect’s business.
• The fact is a problem your product fixes.
• The prospect can check it in a minute.
• It could be sent to no other company.

The strongest facts come from what the prospect sends the people who sign up. That means its welcome email, the reminder after a basket, the text after an opt-in, the chat’s answer and the emails in a free trial. Those reach only someone on the other side of the sign-up, so no other rep has them unless they did the same work. This works for any vendor whose product touches what the prospect’s customers see. That covers email and SMS platforms, deliverability, loyalty and reviews, checkout and payments, and help desks and AI support. It also covers messaging and verification APIs, identity and onboarding, and the tools software companies use to run trials.

The first line template

Every line in the examples follows one shape, so a team can copy it into its own playbook. Keep it to one sentence of under 25 words.

The second sentence offers the screenshot, and the third says in one line what your product changes. The fact does the persuading, so the line needs no adjectives.

24 cold email first line examples for 8 types of vendor

Each line is written as a rep who signed up once, on a date the prospect can check, and stopped before paying. Each comes with the fact behind it and why it works. Pick the group your company sells into, then swap in the fact you found.

Email and SMS platforms selling to brands

• “I signed up to your store on Monday, and your welcome email arrived 7 hours later.” Behind it: the welcome email’s arrival time, measured from the sign-up confirmation. Why it works: welcome timing is a setting in the prospect’s email platform, and they can check it in their own flow report.
• “I left an £85 basket on your store on Monday evening, and no reminder had arrived by Wednesday night.” Behind it: no abandoned cart email inside 48 hours, with the spam folder checked. Why it works: the prospect believes that flow is running, and the basket puts a number on it.
• “I ticked the box for texts when I signed up last week, and no text has arrived since.” Behind it: a text opt-in with no message inside 7 days. Why it works: an SMS vendor sells the revenue from that list, and an opt-in with no text is a list nobody is using.
• “I signed up on Monday and got the same welcome email twice, 4 minutes apart.” Behind it: 2 identical emails with their arrival times. Why it works: a doubled welcome points to 2 flows firing on one sign-up, a setup problem the platform’s onboarding team fixes.

Deliverability and email authentication

• “Your welcome email went to spam in a new Outlook inbox I signed up with on Monday.” Behind it: the folder where the email landed, in one new inbox. Why it works: a sending report counts an email as delivered, and the spam folder is where the subscriber found it.
• “Your welcome email on Monday failed its DKIM check in a new Gmail inbox.” DKIM is a signature checked on arrival to prove which company sent an email. Behind it: the authentication result in the email’s own headers. Why it works: authentication is a deliverability vendor’s first fix, and the prospect can read the same header in a minute.

Loyalty, reviews and referral apps

• “I joined your rewards club when I signed up last week, and the email with my welcome points hasn’t arrived.” Behind it: the loyalty welcome message missing inside the window. Why it works: the points email is the first thing a loyalty programme sends, and the gap sits in a setting the prospect can open today.
• “The referral link in your welcome email on Monday opened a page saying the offer had ended.” Behind it: the link, the page it opened and the date. Why it works: a referral programme runs on that link, so a broken one costs every share a customer makes.
• “Your welcome email on Monday asked me to review a product before I’d bought anything.” Behind it: a review request sent to a subscriber with no order. Why it works: a reviews app that fires on sign-up instead of delivery is a trigger setting a reviews vendor can show them.

Checkout, payments and promotions

• “The 15% code from your welcome email was refused at checkout on Tuesday.” Behind it: the code, the basket and the error message, in one screenshot. Why it works: a refused code loses the order at the last step, and a checkout or promotions vendor can show the rule that rejected it.
• “On a phone last week, your checkout offered card payment only, with no Apple Pay or PayPal.” Behind it: the payment options shown at checkout on a phone. Why it works: wallet options are what a payments vendor sells, and the screenshot shows exactly what a mobile shopper saw.
• “Delivery was free on your product page on Monday, and a £4.95 charge appeared only at the last step of checkout.” Behind it: the product page and the final checkout step, side by side. Why it works: a charge that appears late is a checkout problem with a price on it.
• “Your homepage pop-up offered 15% on Monday, and the welcome email that followed offered 10%.” Behind it: 2 different offers for one sign-up. Why it works: a pop-up or onsite vendor can show which tool sent which code.

Help desks and AI support

• “I asked your chat on Monday whether returns are free, and it said yes; your returns page says £3.95.” Behind it: the chat transcript beside the policy page, both dated. Why it works: a wrong answer from a support bot becomes a refund or a complaint, and help desk and AI support vendors sell accurate answers.
• “I emailed your support at 10:00 on Monday, and the first reply came 31 hours later; your help page promises 24.” Behind it: the response time against the prospect’s own published promise. Why it works: their promise is the benchmark, so the line needs no claim from you.
• “During my trial last week, your in-app chat said single sign-on (SSO) was included; your pricing page lists it on Enterprise only.” Behind it: the chat answer beside the pricing page. Why it works: a bot that promises a feature the plan lacks creates a sales problem as well as a support one, at a software company that sells on trust.

Messaging and verification APIs selling to apps

• “Your sign-up code took 6 minutes to reach my phone on Monday, and the first one never came.” Behind it: each one-time code with the time it was requested and the time it arrived. Why it works: code delivery is what an SMS or verification API sells, and a slow code stalls the sign-up at a step the prospect’s growth team measures.
• “I chose WhatsApp updates when I signed up last week, and every message since has come by email instead.” Behind it: the channel chosen at sign-up and the channel each message used. Why it works: a messaging vendor sells delivery on the channel the customer chose.

Identity, sign-up and onboarding

• “Your verification email took 40 minutes to arrive on Monday, so my sign-up sat unfinished.” Behind it: the sign-up time and the arrival time of the verification email. Why it works: identity and onboarding vendors sell completed sign-ups, and 40 minutes is long enough for a new customer to leave.
• “Your sign-up failed at the address step on a phone last week, with no error message.” Behind it: a screenshot of the step and the device. Why it works: the prospect’s analytics show a drop at that step without the reason, and the screenshot is the reason.

Trials, onboarding and retention at software companies

• “I started your free trial on 2 November, and after the welcome email nothing came until ‘Your trial ends tomorrow’ on day 13.” Behind it: every trial email by trial day. Why it works: onboarding and lifecycle vendors sell the days between, and the prospect’s own trial shows the silence.
• “Your free plan stopped me at 3 projects on day 2, and no upgrade prompt explained the paid plans.” Behind it: the trial limit and the missing upgrade prompt, each with a screenshot. Why it works: pricing and paywall vendors sell the moment a free user hits a limit.
• “When I cancelled my trial last week, the cancel page offered 50% off for 3 months, and the email that followed offered 30%.” Behind it: the save offer in the cancel flow beside the one in the email. Why it works: retention and billing vendors sell one save offer, set once, and 2 offers mean 2 tools disagree.
• “I invited a teammate during my trial on Monday, and the invitation email never reached them.” Behind it: the invite time and an empty second inbox after 24 hours. Why it works: product-led growth tools sell team invites, because each invite is a new user.

Where the facts behind cold email opening lines come from

Most sales teams use similar data, from contact databases and intent tools to Exa’s search of the public web. Each source is good at its part of the job.

Public research by hand

The company’s website, its annual report, the latest news, its job posts and its leaders’ posts give a rep context on the company and the person. They cost nothing but time, and every other rep selling into the account reads the same pages.

Contact databases and intent data

Contact databases give names, titles and verified addresses, and intent tools report which accounts are researching a topic across the web. Together they say who to email and when. Intent data says an account might buy; its own customer emails show why.

AI research agents

An AI research agent runs the public research for every row of a list and drafts a line from it. Claygent describes itself as able to take on “company research, lead qualification, signal detection”, with web access “to do more real-time research” and a reasoning trace behind each decision. Its pages don’t describe signing up as a customer at the companies it researches.

Exa and search of the public web

As of 11 November 2026, Exa calls itself “The world’s data for AI agents” and says it searches “the largest index of public web and private information”. Its page for go-to-market teams offers “One company data API for finding accounts, enriching your CRM with cited sources, and tracking signals that win deals”. It draws on 70 million companies, more than 1 billion people profiles and live web sources. That puts the public web in front of a rep in seconds. Exa’s pages don’t describe signing up at the companies it covers or keeping what those companies send their customers. Obsession vs Exa sets the two side by side.

What public sources can’t show

Every source in that list reads what a company publishes, or what others publish about it. What a company sends the people who sign up sits on the other side of a login wall, any step a site puts between a visitor and what it shows customers. Its welcome email, its basket reminder, the text after an opt-in, the chat’s answer and the emails in its trial reach only a customer. Our guide to the web behind the login covers what sits behind each sign-up, login and form.

The same facts double as timing. A welcome email that stops is a buying signal for an email platform, and a trial that goes quiet after day 1 is one for an onboarding tool. So is the week an account’s emails start coming from a new email platform. An SDR manager can sort a whole territory by them.

How to get the facts by hand

One rep can collect these facts for a short list of top accounts this week. Each step has what a pass looks like.

1. Pick the accounts and the problem

List the accounts. For each one, write down the problem your product fixes that a customer could see, such as a slow welcome email, a missing reminder or a wrong chat answer. A pass is one sentence per account.

2. Sign up as a customer

Use a fresh inbox and phone number for each account, in your own name or your company’s, and never enter details that aren’t true. The guide is it legal to mystery shop competitors sets out what decides whether a method is allowed; none of this is legal advice. A pass is the confirmation email in the inbox, with its time written down.

3. Do what a customer does, then stop before paying

Opt in to texts, leave a basket, start a trial or ask the chat one question, whichever matches the problem. Record the country and the device, because a store can treat a UK phone and a US desktop differently.

4. Wait for the window to close

Set the window before you start: 1 hour for a welcome email, 48 hours for a basket reminder, 7 to 14 days for texts. A message counts as missing only once the window has closed and the spam folder has been checked.

5. Save the evidence

Screenshot every screen and keep every email with its full header, which shows the time it arrived and the domain that sent it. A pass is a folder per account with a dated file for each fact.

6. Write the line

Fill the template: when, what you did, what happened, and the prospect’s own benchmark where one exists. Read it aloud. If it would make sense sent to another company, it isn’t finished.

How to check a first line before it goes

• True, in the right voice. Write “I” only if you signed up yourself. When your team or a service it uses collected the fact, write “we”, and keep the screenshot ready to send.
• What any customer could see. Nothing about a person, nothing from inside their systems, nothing that needed a password a customer wouldn’t have.
• One sign-up, said once. The line describes one visit on one date. It never suggests the company has been followed for months, and it offers the screenshot instead of attaching a file of findings.
• A problem your product fixes. A true fact your product doesn’t touch is trivia, and the prospect reads it that way.
• Still true on send day. Teams fix broken emails and codes. Check the welcome email or the code again if the line is more than a week old.
• Within the law. In the US, the FTC’s CAN-SPAM guide says “the law makes no exception for business-to-business email”. It bans deceptive subject lines and requires a valid postal address and opt-outs honoured within 10 business days. In the UK, regulation 23 of the Privacy and Electronic Communications Regulations bars marketing email that hides who it is from or gives no valid address for opting out. This is general information, not legal advice.

How to personalize cold emails at scale

Signing up by hand takes about 15 minutes an account: 10 to sign up, act and screenshot, and 5 to log what arrives across the window (example times). The days of waiting run alongside. The sum grows with every account a team adds.

The same sum gives 125 hours a week for 10 SDRs, and 12.5 hours for one. Past a short list of top accounts, it needs an inbox and phone number per account, kept open for weeks, with every original saved.

Obsession collects what companies show only to customers, step by step: their screens, emails and texts, member prices, trial limits, quotes and cancel offers, each dated with a screenshot. Teams and AI agents look up any company through the API or MCP, and a company not yet covered is added on request. For outbound, Obsession’s prospect intelligence signs up, opts in to texts and asks the chat at every company on your list. It writes each fact, its date and its screenshot back to the same rows in Clay, a sheet or the CRM, for as long as you set. It also shows the platform that sent each email, and the week an account’s emails start coming from a different one, as on the page for sales teams. Exa gives reps the public web in seconds; Obsession gives them what each account sends the people who sign up, and a team can use both. Run it on the accounts your SDRs open this month, so you can see what it does to reply rates, meetings booked and opportunities.

Where SDRs get first line facts, compared

Each option reads a different part of an account. We make Obsession, so every other option is described from its provider’s own pages as of 11 November 2026. Facts checked 11 November 2026.

For a first line about what the prospect’s own customers received, use Obsession, which keeps it dated for every account on your list, for as long as you set. Public research and Exa give the context on the company. AI research agents draft lines from public facts across a whole list, and signing up by hand works for a short list of top accounts.

Limits and next steps

• Lines about orders need an order. Delivery emails, returns and review requests after a purchase reach only someone who bought. Obsession covers every step short of paying, so those lines come from an order your own team placed.
• One sign-up is one customer’s view. A new UK subscriber on a phone sees what that store shows new UK subscribers on phones. Say so in the line when it matters.
• A fact that isn’t a problem is not a first line. Many sign-ups will turn up nothing worth saying. That is useful too: it moves the account down the list.

When the prospect replies, the sales business case template opens the next call with the same screenshot. Teams that want each fact as a field in their own tools can follow Clay custom signals. Start with the 10 accounts your SDRs most want to meet this month, and write each first line from their own inbox. Sales intelligence from behind the login shows the same view for every role on a revenue team, with an example for each.

Frequently asked questions