A practical reference for writing Sailebot‑ready outreach that lands in the inbox, catches attention, and drives replies. Keep the guidance below tight and natural; adapt examples with your own tone.

Merge Fields To Use:

Category	Merge Field
Contact Info	{target_firstname}
Contact Info	{target_lastname}
Contact Info	{target_company}
Contact Info	{target_fullname}
Your Info	{client_firstname}
Your Info	{client_company}
Your Info	{client_fullname}
Your Info	{client_signature}
Sailebot Content	{opt_out}
Email Context	{previous_from}
Email Context	{previous_to}
Email Context	{previous_cc}
Time & Date	{international_time_a}
Time & Date	{international_time_b}
Custom Fields	{gdpr_link}

1) Subject Lines that Get Opened

TL;DR
Keep subjects 3-5 words.

💡 Pro tip: Read the subject out loud. If it sounds like an ad, rewrite it as a task the recipient owns; something that belongs on their to-do list. It should feel so relevant to their day-to-day that skipping it would mean missing a responsibility.

Bad → Better → Best

Bad: Unlock explosive growth with our limited offer
Better: Quick question about growth and revenue at {target_company}
Best: {target_company}'s Q3 Growth

Do	Don’t
Name one specific thing you help with.	Stack adjectives or hype.
Avoid Common Spam Triggers.	Use urgent, limited time, act now.
Keep subjects between 3-6 words.	Put the entire value in the subject.

Try this now (60 seconds)

Pick one draft subject and read it out loud. Would it belong on their to-do list? If not, rewrite until it does.
Keep it under six words and personalise with one merge field.
Avoid ALL CAPS and heavy punctuation.

Examples to copy

{target_company}'s Q3 Growth
{target_company}'s Growth Plan
KPI's at {target_company}

2) Avoid common spam triggers

TL;DR
Open with a greeting of your choice (e.g., “Hi {first_name}”) and get to immediate relevance by citing a recent update, trend, or shared challenge tied to their role or KPIs while skipping clichés. In one or two crisp sentences, hint at the benefit, keep it conversational, and show quick credibility or alignment if possible.

💡 Pro tip: Read it out loud. If it sounds like a promotion or a countdown, rewrite it as a routine work task or status check.

Do	Don’t
Address by name and keep it conversational (“Hi {first_name}”).	Use clichés like “I hope this finds you well.”
Establish quick context in the first sentence (recent update, trend, shared challenge).	Bury the lead or open with a generic intro.
Spark relevance first and tie to their role or KPIs.	Lead with vague curiosity bait that is not job-relevant.
Show credibility or alignment early (stat, mutual context, recognizable client).	Make it about you with no proof or alignment.
Write something personal, relevant, and hard to skim past.	Use filler that is easy to skip.

Try this now (60 seconds)

Scan your subject for any trigger words below.
Swap hype terms with neutral alternatives:
- “save big” → “cost review”
- “last chance” → “status update”
- “risk-free” → “trial details”
Remove extra punctuation and any ALL CAPS.

Groupings below are illustrative. Do not use these.

Money / financial:
free, save big, cash bonus, earn money, extra income, financial freedom, lowest price, best deal, double your, no cost

Urgency/pressure:
act now, urgent, limited time, do not miss out, instant, only today, exclusive offer, last chance, guaranteed

Risky promises:
risk-free, no obligation, 100% satisfied, no strings attached, winner, congratulations, amazing, once in a lifetime, miracle

Overhyped:
click here, buy direct, apply now, cheap, credit, fast cash, luxury, promise you, trial

Formatting traps to avoid:
ALL CAPS, !!! or ???, emojis, symbols like %, $, or “% off,” fake threads like “Re:” or “Fwd:” when not genuine

3) Strong Openers

TL;DR

Open with a direct, conversational greeting and immediately tie to a recent update, trend, or shared challenge relevant to their role/KPIs; keep it to one or two crisp sentences that hint at the benefit without over-explaining.

Do	Don’t
Make it personal, relevant, and hard to skim past.	Open with a generic filler.
Address by name and keep it conversational (“Hi {first_name}”).	Use clichés like “I hope this finds you well.”
Establish quick context in the first sentence (recent update, trend, or shared challenge).	Delay context or start with a broad self-intro.
Hint at the value to come without over-explaining.	Over-explain or pitch in detail in the opener.
Keep it short; one or two crisp sentences.	Write more than 1–2 sentences.
Lead with relevance tied to their role or KPIs.	Lead with curiosity or unrelated details.

Weak opener

 “I hope this email finds you well. I wanted to introduce myself and share how we can help your business.”

Stronger opener

 “Hi {first_name}, I noticed {target_company} recently expanded into {new market}, which often adds pressure on operations. At {client_company}, we help leaders navigate that transition without sacrificing efficiency.”

4) Structure the Body for Clarity and Impact

TL;DR

Keep the body to four short sentences focused on earning interest, not delivering a full pitch. Pair a clear value proposition to a real pain in plain, scannable text tied to the recipient’s role, industry, and priorities, and include only offerings that are directly relevant.

Do	Don’t
Keep it short, four sentences max; aim for interest, not a full pitch.	Write long paragraphs or try to deliver the full pitch.
Pair a clear value prop with a real pain.	List features or offerings without linking to a problem.
Show how you solve a real problem.	Make generic claims with no concrete tie-in.
Include only offerings that are relevant to this audience.	List multiple offerings that aren’t directly relevant.
Tie back to the recipient’s role, industry, and likely priorities.	Rely on generic phrasing that could apply to anyone.

Use the framework below as defaults; adjust lengths to fit your voice and market.

Email 1: Light and curiosity‑driven

Subject (≤ 6–8 words): {target_company} outbound trends
Length: 100–150 words
Tone: Conversational; open the loop; include Value Prop #1
Content guide:
- Generic observation or trend: “Talking to a lot of teams like {target_company} lately…”
- Hypothesis about a current challenge
- Quick intro to {client_company}
- Ask: “Open to a quick chat next week?”
- Bargain: “Happy to send a 30‑second explainer or quick stat sheet.”
- Opt‑out: “If this is not relevant, no stress at all.”

Email 2: Context and social proof

Subject (≤ 6–8 words): follow‑up on {target_company}
Length: 150–200 words
Tone: Credible and validating; reframe Value Prop #1 with data
Content guide:
- Reference Email 1
- Share a market or client stat that adds urgency
- Expand pain → how your solution helps
- Ask: “Would a quick walkthrough be helpful?”
- Referral bargain: “If this is not your focus, happy to be pointed to the right person.”
- Opt‑out: “Totally fine if this is not a top priority.”

Email 3: Use case and reinforcement

Subject: {original subject}
Length: 200+ words
Tone: Confident and results‑driven; introduce Value Prop #2
Content guide:
- Reference Email 1’s theme
- One clear use case with result and timeline
- Add a new benefit or capability
- Ask: “Quick 10‑minute slot this week?”
- Opt‑out: “If it is not a fit, feel free to ignore.”

Email 4: Fresh angle and close

Subject: final check‑in, {target_company}
Length: 150–200 words
Tone: Friendly and low pressure; include Value Prop #3
Content guide:
- New challenge you solve (fresh point of view)
- Support with a stat or recent industry shift
- Brief recap of how you help
- Choose‑your‑own‑path asks:
  - Schedule a quick call
  - Introduce a colleague
  - Request a short case study
- Opt‑out: “Totally understand if now is not the right time; just let me know.”
- Referral request: Include a clear handoff ask

5) Optimize for Deliverability

TL;DR

Use a plain text style and keep most emails to 50 to 125 words; avoid heavy formatting (bold, images, links/URLs, phone numbers, addresses, attachments) and limit exclamation points, ALL CAPS, and marketing phrases to reduce filtering. Subdomain/Sailes Created Domain setup and warm-up are handled automatically by Sailes Deliverability feature, so focus on monitoring engagement (leads, objections, unsubscribes) and ensuring the audience list matches the content.

Do	Don’t
Use a plain-text style.	Use heavy formatting (bold, images, multiple links/URLs, phone numbers, addresses, attachments).
Keep most emails within 50–125 words.	Write long, dense messages.
Limit exclamation points and ALL CAPS; avoid marketing-heavy phrases.	Shout with CAPS, stack punctuation, or use promo language.
Rely on automatic Sailebot deliverability feature (subdomain/Sailes Created Domain, DNS, & warm-up)	Manually tinker with DNS/warm-up or add third-party warm-up tools when it’s already handled.
Monitor engagement (leads, objections, and unsubscribes) and adjust content.	Ignore negative signals and keep sending the same copy.
Update content every 45 days to ensure it stays fresh in the inbox.	Keep sending the same stale copy.

6) Write an Effective Call to Action

TL;DR

Have one clear ask per email and keep friction low: use plain text, no links in the body, include opt-out language, and offer an alternate path for people who avoid meetings. Choose the CTA by temperature (reply yes for a placeholder or a 30-second overview), default meeting (15-minute chat or brief walkthrough), event option (webinar or virtual lunch and learn), in-person only if local, or a referral to the right owner.

Do	Don’t
Have one clear next step and one question per email.	Stack multiple asks or CTAs.
Keep friction low and offer an alternative path (e.g., lunch & learn or LinkedIn connection in later emails).	Force a meeting as the only option.
Use Micro-yes CTAs when cold: “If helpful, let me know, and I will send a placeholder.” / “Happy to send a 30-second overview if that is easier.”	Ask for high-commitment actions in the first touch.
Use the Meeting (default) ask when appropriate: “Would you be open to a quick 15-minute chat next week?” / “What does your calendar look like for a brief walkthrough?”	Leave the next step vague or implied.
Offer Webinar / Virtual Lunch & Learn as an option: “If easier, I can reserve you a seat for our short session on {topic}.”	Push an event without presenting it as an optional path.
Use In-person only when locality is clear: “If you are in {city}, happy to meet for a 20-minute coffee…” / “We can host a short lunch & learn…”	Not using this when applicable.
Ask for a Referral/handoff when appropriate: “If someone else owns this at {target_company}, potentially another Engineering leader, could you loop them in?”	Keep emailing the wrong contact without asking for the owner.

Pick the CTA by temperature

Micro‑yes (lowest friction):
“If helpful, reply yes and I will send a calendar hold.” “Happy to send a 30‑second overview if that is easier.”

Meeting (default):
“Would you be open to a quick 15 minute chat next week?” “What does your calendar look like for a brief walkthrough?”

Webinar / Virtual Lunch & Learn option:
“If easier, I can reserve you a seat for our short session on {topic}. Reply yes and I will send the hold and details.”
In‑person when local
“If you are in {city}, happy to meet for a 20 minute coffee near your office.” “We can host a short lunch and learn for your team on {topic}. Let me know and I will coordinate dates and bring lunch.” “If it is easier, we can do a quick on‑site walk to scope {area}.
Referral/handoff:
“If someone else owns this at {target_company}, perhaps another leader in Engineering, could you please loop them in?"

8) Staying Compliant

TL;DR

Cold outbound works when it’s compliant and trustworthy: include a clear opt-out and keep the tone aligned to your voice. Avoid links, phone numbers, attachments, or full URLs in the body; steer clear of sensitive or regulated claims and overpromising; and limit capitalization, symbols, and spammy words.

Do	Don’t
Include a clear opt-out (e.g., “If this is not relevant, let me know and I will step back.”).	Omit an opt-out or bury it.
Use a GDPR-compliant unsubscribe text/link when sending emails in the EU/UK (place it in the footer or signature; keep body copy plain text).	Drop links in the body copy or use non-compliant unsubscribe language.
Keep body plain text with minimal formatting.	Add heavy formatting, images, attachments, phone numbers, or full URLs in the body.
Make cautious, accurate statements.	Make sensitive/regulated claims or over-promise outcomes.

✏️ Note: To ensure GDPR compliance, add the exact text below to your sequence after Email 1. Email 1 must include a unique GDPR link. If you don’t have this link, contact your Support Manager or use the Support Chat in the bottom-right corner of Starboard.

"In accordance with article 13 of GDPR, you received this email based on legitimate business interest. If you are not interested in being engaged further, please respond to this email."

8) Build Then Assemble Workflow (Sailes example)

Build each block first, then assemble into one plain-text note. Keep it to four sentences and one clear CTA. No links in the body.

Block steps

Subject (3–6 words, ≤ 45 chars)
Examples: “{target_company} outbound trends”, “question on {topic}”.

Opener (1 sentence)
“Hi {target_firstname}, talking with teams like {target_company} lately, we are seeing {pain_trend}.”

Pain → Value (1–2 sentences)
“Many leaders cite {pain}. At Sailes, we help {role} {desired_outcome} without {common_objection}.”

Proof (optional, 1 clause)
“Teams like {peer_company} saw {result} in {timeframe}.” Tip: If this makes it 5 sentences, fold the clause into Pain → Value.

Single CTA (choose one)

“Would you be open to a quick chat next week?”
“If easier, I can reserve you a seat for our short virtual lunch and learn on {topic}."
“If you are in {city}, happy to meet for a 20 minute coffee near your office.”

Opt-out / Unsubscribe (1 short line)
“If this is not relevant, let me know and I will step back.”GDPR note: Include a GDPR text where required in place of the unsubscribe text above.

Template

Subject: {University Name} downtime

Hi Jamie, speaking with other operations leaders in higher education, I’m hearing that maintenance windows still create long downtime, and surprise outages disrupt student services.

Many teams cite fragmented monitoring and slow after-hours escalation; at {Company_Name}, we help campus ops shorten incidents and restore services faster without adding tools or headcount, and a peer like ({University Name} cut downtime by about 28% in a month.

Would you be open to a quick 15-minute chat next week?

{First Name}

--
{Full Name}
{Title} Strategic Partnerships - Higher Education

{Company Name}

If this is not relevant, let me know, and I will step back.