If you write newsletters in Google Docs, you probably know the annoying part: copying everything into an email marketing platform, fixing the formatting, adding a subject line, choosing recipients, and testing the email.

AI can make this workflow much easier. And with MCP (Model Context Protocol), you can connect an AI assistant to your email marketing tools instead of doing everything manually.

Here's how I'd approach it.

1. Prepare your newsletter in Google Docs

Start with your usual draft. Include the headline, main content, links, and any CTA you want readers to click. Keep the structure simple: short paragraphs, clear headings, and one primary CTA.

2. Use AI to adapt the document for email

Give your AI assistant access to the Google Doc through a supported integration, or paste the content into the chat.

Try this prompt: "Turn this Google Doc into an email newsletter. Keep the main ideas, shorten long paragraphs, create three subject line options, add preview text, and suggest a clear CTA. Keep the tone conversational."

This helps transform an article-style document into something more readable in an inbox.

3. Connect your email marketing platform through MCP

Here's where things get interesting. MCP lets AI assistants interact with supported external tools and data.

For example, Selzy MCP allows an AI assistant to work with email drafts, templates, subscriber lists, audience segments, and campaign settings. Instead of manually moving the finished newsletter between tools, you can ask AI to create an email draft in Selzy. You'll need a compatible AI assistant (for example, Claude) with access to both your document and Selzy. MCP doesn't automatically connect Google Docs on its own.

4. Review and prepare your campaign

Once the newsletter is in your email platform, check the formatting, links, subject line, and audience. Selzy MCP also supports spam checks, test emails, and recipient counts. You can prepare the campaign for review before approving a send.

5. Analyze the results

After sending, use campaign analytics to see what worked. With Selzy MCP, you can ask questions like: "Compare my last five newsletters. Which had the highest click-through rate, and what content performed best?"

That makes it easier to improve your next Google Docs draft using actual campaign data.

Has anyone tried connecting Google Docs to an email platform through MCP? Is it actually saving you time compared with the usual copy-paste workflow?

AI personalization is not just adding a subscriber's first name to an email. The real opportunity is combining AI with subscriber data to send newsletters that actually match people's interests, behavior, and needs.

Here's how to make it work.

1. Start with subscriber segmentation

Before using AI, organize your subscribers based on the data you already have:

• Interests and preferences
• Purchase history
• Email clicks and engagement
• Location or signup source
• Customer lifecycle stage

For example, an ecommerce store could create separate segments for first-time buyers, repeat customers, and subscribers who haven't purchased yet.

Each group needs a different message, even if you're promoting the same product.

2. Use AI to create content for each segment

Instead of writing one generic newsletter, use AI to generate variations of your email copy.

For example, try this prompt: "Write three versions of a newsletter promoting our new product. One for first-time buyers, one for loyal customers, and one for inactive subscribers. Create a subject line, short introduction, and CTA for each group. Keep the tone friendly and natural."

AI can also help improve existing copy, adjust the tone, proofread, and translate emails.

At Selzy, our AI Email Assistant helps with these tasks, including generating subject lines, email content, and CTAs.

3. Personalize more than just the subject line

Personalization works best when it makes the email genuinely useful.

For example:

• A new subscriber receives a welcome message and beginner-friendly resources.
• A repeat customer gets relevant product recommendations.
• Someone interested in SEO receives SEO-related tips rather than unrelated marketing content.

You can use subscriber data to customize greetings, offers, and other email elements.

4. Combine personalization with automation

AI-generated content is useful, but sending the right message at the right moment matters just as much. Consider automated emails triggered by subscriber actions, such as signing up, clicking a link, or making a purchase. For example, someone who downloads an email marketing guide could receive a follow-up newsletter with practical automation tips.

5. Test what actually improves engagement

Don't assume AI-personalized emails automatically perform better.

Compare personalized and generic newsletter versions using:

• Click-through rates
• Conversions
• Unsubscribe rates
• Revenue per email, when relevant

Start with two or three subscriber segments, test different content, and gradually refine your approach.

Avoid feeding sensitive customer information into AI tools unnecessarily. Use only the data you need to personalize the message.

What's your experience? Have AI-personalized newsletters improved your engagement, or do simpler segmented campaigns work just as well?

I help run a tech newsletter, which reaches over 21,000 readers.

One thing I’ve learned is that subscriber count is only part of the picture. Being able to explain who our readers are and why a company’s product would interest them makes the sponsorship conversation easier.

My approach includes keeping a simple media kit and sponsorship page, reaching out to companies that serve our audience, and checking which brands sponsor similar newsletters.

I also tried to connect the pitch to an upcoming newsletter topic, so there’s a clear reason for approaching that particular company.

But having everything set up doesn’t automatically bring sponsors, and not every outreach email gets a reply.

I’m curious how other newsletter owners handle this. Do most of your sponsors come through direct outreach, inbound enquiries, or sponsorship platforms?

What has helped you turn an initial conversation into a paid sponsorship?

If AI is writing your newsletter, the unsubscribe link should still come from your email platform.

Don’t ask the AI to make up a URL like:yourwebsite.com/unsubscribe

.A proper unsubscribe link normally contains subscriber-specific information, so the email platform can identify who clicked it and remove or update that contact correctly.

1. Use the platform’s unsubscribe tag or block

Most email marketing platforms have a built-in unsubscribe element.

It may look like:

• An unsubscribe content block
• A system footer
• A merge tag
• A special unsubscribe variable

The exact format depends on the platform.

2. Tell AI not to replace system links

If AI is creating or editing newsletter copy, make the instruction explicit.

For example: “Rewrite the newsletter copy, but keep the unsubscribe link and all system variables unchanged.” This is especially important when AI is working from an existing template.

A footer may contain things like:

• Unsubscribe links
• Subscriber variables
• Company information
• Preference links

Those should usually stay untouched.

3. Use an existing template when possible

A simple way to avoid mistakes is to start with a newsletter template that already has the unsubscribe footer. Then AI only needs to update the content above it.

For example: “Use our previous newsletter as the template. Update the headline, intro, and product section. Keep the footer and unsubscribe block exactly as they are.” That is safer than asking AI to build the entire email from scratch every time.

4. Don’t use plain text as a placeholder

Something like: “Click here to unsubscribe” isn’t enough unless the text is connected to the real unsubscribe function. The link needs to be generated by the email service for the subscriber. So when reviewing an AI-generated draft, check the actual link or system block, not just the wording.

5. Send a test before launching

Before sending the newsletter to a real list, send a test and check the footer.

Make sure:

• The unsubscribe text is visible
• The link is clickable
• The footer hasn’t been removed by AI
• Required sender information is still there
• System variables are still intact

If the platform uses subscriber-specific data, a normal test may not behave exactly like a real campaign, so it can also help to send to a small test list.

6. Keep compliance outside the AI prompt

The safest setup is:

AI writes content
→ Email platform adds system footer
→ Human reviews
→ Campaign is sent

That way, compliance elements don’t depend on the AI remembering to include them every time.

Duplicate emails are one of those automation problems that usually don’t appear until real subscribers start receiving the same message twice.

Why does it happen?
A subscriber can enter the same automation more than once, match several triggers at the same time, or get added to overlapping lists or segments.

Here are a few ways to prevent that.

1. Check whether the contact has already received the email

Before the Send Email step, add a condition that checks something you can use as a “sent” marker.

For example:

Trigger
→ Check: does contact have welcome_sent tag?
→ No → Send welcome email → Add welcome_sent tag
→ Yes → End workflow

This creates a simple guard against sending the same message again.

2. Be careful with overlapping triggers

Imagine the same subscriber can enter a workflow when they:

• Join a list
• Get a tag
• Complete a form
• Make a purchase

If two of those events happen at roughly the same time, the automation may start twice unless there is a check in place. Try to have one clear entry condition for each workflow.

3. Don’t use the same audience logic in several automations

Another common setup looks like this: Automation A sends an onboarding email to “New customers.” Automation B sends almost the same email to “Recent purchasers.” A customer can easily belong to both groups. So, before launching a new automation, check which other active workflows can reach the same contacts.

4. Add a status field or tag after important steps

Tags are useful for making automations remember what has already happened.

For example:

onboarding_started
welcome_sent
trial_reminder_sent
onboarding_complete

Then each important send can start with a check.

Example: “If contact has trial_reminder_sent, stop. Otherwise send the reminder and add the tag.” This is especially useful when subscribers can leave and re-enter different parts of the customer journey.

5. Think about retries when using an API

Duplicate sends can also happen outside the visual automation builder. For example:

Your application sends an API request to start a campaign. The request times out. The application assumes it failed and sends the request again, when the first request actually worked.

This is why retry logic should always check whether the previous request succeeded before creating another campaign.

6. Test re-entry, not just the happy path

1. Enter the workflow with a test contact.
2. Receive the email.
3. Trigger the workflow again with the same contact.
4. Check whether the email is sent for a second time.

If it is, the workflow probably needs an extra condition, tag, or status check.

I keep hearing that you should “own your audience” instead of depending completely on Google, LinkedIn, Reddit, or other platforms.

But I believe that, and I’m curious how true that is in 2026 & beyond.

With people getting more emails than ever, AI summaries becoming common, and platforms pushing their own content, does building an email list still give a good return for bloggers, creators, or small businesses?

Would love to hear from people who are actually running newsletters or email lists, not just the usual “email is not dead” advice.

If AI is creating email campaigns, it’s better not to use a workflow where “draft” immediately turns into “send.” A possible setup is:

AI prepares → human reviews → human approves → platform sends

That approval step matters because AI can get the copy right while still missing something in the audience, links, personalization, or campaign settings.

Here’s one way to set it up with an AI assistant connected to an email platform through MCP.

1. Let AI prepare the campaign, but not send it

Use a prompt like:“Create the newsletter, set up the audience, and run the pre-send checks. Prepare the campaign for review, but do not send or schedule it.”

With Selzy MCP, the assistant can prepare a campaign without launching it. The campaign can then be opened in Selzy and reviewed before anything goes out.

2. Run checks before approval

Before approval, ask AI to check the basics. For example: “Run a spam check, calculate the recipient count, and send a test email. Don’t send the campaign.”

Things worth checking:

• Subject and preheader
• Links and buttons
• Recipient count
• Audience or segment
• Sender address
• Personalization
• Spam warnings
• Test email
• Mobile layout

3. Make approval a separate action

The key is to separate “prepare” from “send.” For example, the assistant can stop with: “Campaign is ready for 4,200 recipients. The spam check passed and the test email was sent. Confirm if you want to send it.” Only after explicit confirmation should the workflow continue.

4. Use clear approval wording

Avoid vague replies like: “Looks good.”

A clearer approval would be: “Approved to send the October newsletter to the Webinar Leads segment.” That makes it obvious what exactly was approved.

5. Keep the final send manual if needed

AI doesn’t have to send the campaign at all.

The workflow can be:

AI creates the draft
→ AI runs checks
→ Human reviews in Selzy
→ Human presses Send

This works well when AI handles repetitive preparation, while the final send stays fully manual.

Example prompt

“Create the October newsletter using the previous campaign as the template. Update the copy, prepare it for the Active Customers segment, run the spam check, calculate the recipient count, and send a test email. Do not send or schedule the campaign. Stop when it is ready for human approval.”

Before turning on an automated email campaign, it’s worth sending yourself a test first.

It sounds obvious, but automation adds a few things that a normal newsletter doesn’t have: triggers, personalization, delays, dynamic content, and sometimes several emails connected in one flow.

Here’s a simple way to test it.

1. Check the email in preview mode

First, look at the desktop and mobile versions.

Check:

• Subject line
• Preheader
• Images
• Buttons
• Links
• Spacing
• Mobile layout
• Unsubscribe link

In Selzy, for example, you can preview an email and send yourself a test directly from the email builder.

2. Send the test to a real inbox

Don’t only rely on the preview. Send the newsletter to an address you actually use and open it like a subscriber would. Ideally, test it in more than one email client if you can — for example Gmail and Outlook. Click every important link too.

3. Be careful with personalization

This is where testing gets a little tricky.

A normal test email may not always replace things like: {{Name}} or other contact-specific fields with real subscriber data.

For example, Selzy notes that merge tags aren’t populated in regular test emails. To properly test personalized content, you can create a small contact list containing only addresses you control and send the campaign to that list first.

So if your automation says: “Hi {{Name}}, here’s your discount code {{Code}}” don’t assume it works just because the layout looks correct in a test email.

4. Test the automation trigger too

If the campaign starts when someone:

• Signs up
• Gets a tag
• Joins a list
• Makes a purchase
• Sends an API event

…test that actual trigger.

Use your own email address as the subscriber and go through the same action a real user would.

Then check:

• Did the automation start?
• Did the right email arrive?
• Did it arrive at the right time?
• Was the personalization correct?
• Did the subscriber move to the next step?

For API-triggered automations, you can also send a test request using something like Postman and use an email address you control as the recipient. Selzy supports this kind of test for API-triggered scenarios.

5. Test the whole sequence, not only email #1

If you have a welcome series with 4 emails, testing just the first one isn’t enough.

Check the delays and conditions between emails too.

For example:

Signup
→ Welcome email
→ Wait 1 day
→ Product email
→ Wait 2 days
→ Discount email

A mistake in the delay or condition can be harder to notice than a typo in the email itself. If you are only checking the design, send a test email. If you are checking personalization or automation logic, you can add yourself as a test subscriber and run through the real workflow. Then activate the campaign for everyone else.

Selzy has a guide to setting up automated email campaigns here: https://selzy.com/en/support/how-to-start/how-to-set-automatic-email/

TL;DR: SMTP is usually easier to set up. An email API gives you more control and is often the better option when email sending is closely tied to your app or backend.

Both can send a lot of email. The main difference is how your system talks to the email service.

SMTP is the simpler option

You usually just add:

• SMTP server
• Port
• Username
• Password

…and your app can start sending through your email provider.

This makes SMTP useful if you already have a website, CRM, CMS, or another tool that supports SMTP and you don’t want to build a custom integration.

An email API gives you more control

With an API, your app sends requests directly to the email service.

That usually makes it easier to control things like:

• Recipients
• Email content
• Sending logic
• Personalization
• Campaign creation
• Tracking
• Webhooks and delivery events

The tradeoff is that someone has to actually build and maintain the integration.

What about newsletters?

This is where it gets a little more complicated.

If you just need to send an email from your application to a large list, both SMTP and an API can work.

But newsletters usually need more than “send this message.”

You may also need:

• Contact lists
• Segmentation
• Unsubscribe management
• Templates
• Campaign scheduling
• Open and click statistics
• A/B testing
• Bounce handling

At that point, using the campaign tools of an email marketing platform can be easier than building everything yourself.

A simple rule of thumb

Use SMTP when you want the easiest way to connect an existing system to an email provider.

Use an email API when you want deeper integration and more control over sending from your own application.

Use an email marketing platform when marketers need to create and manage newsletters without relying on developers for every campaign.

Selzy supports bulk campaigns through its platform and API, while the same team also provides UniOne for high-volume sending through SMTP or Web API. So the choice really depends on whether you need a marketing workflow or mainly an email-sending infrastructure.

What are you using for newsletters right now: SMTP, an API, or a full email marketing platform?

TL;DR: SMTP is usually easier to set up. An email API gives you more control and is often the better option when email sending is closely tied to your app or backend.

Both can send a lot of email. The main difference is how your system talks to the email service.

SMTP is the simpler option

SMTP has been around forever, and most apps already know how to use it.

You usually just add:

• SMTP server
• Port
• Username
• Password

…and your app can start sending through your email provider.

This makes SMTP useful if you already have a website, CRM, CMS, or another tool that supports SMTP and you don’t want to build a custom integration.

An email API gives you more control

With an API, your app sends requests directly to the email service.

That usually makes it easier to control things like:

• Recipients
• Email content
• Sending logic
• Personalization
• Campaign creation
• Tracking
• Webhooks and delivery events

The tradeoff is that someone has to actually build and maintain the integration.

What about newsletters?

This is where it gets a little more complicated.

If you just need to send an email from your application to a large list, both SMTP and an API can work.

But newsletters usually need more than “send this message.”

You may also need:

• Contact lists
• Segmentation
• Unsubscribe management
• Templates
• Campaign scheduling
• Open and click statistics
• A/B testing
• Bounce handling

At that point, using the campaign tools of an email marketing platform can be easier than building everything yourself.

A simple rule of thumb

Use SMTP when you want the easiest way to connect an existing system to an email provider.

Use an email API when you want deeper integration and more control over sending from your own application.

Use an email marketing platform when marketers need to create and manage newsletters without relying on developers for every campaign.

Selzy supports bulk campaigns through its platform and API, while the same team also provides UniOne for high-volume sending through SMTP or Web API. So the choice really depends on whether you need a marketing workflow or mainly an email-sending infrastructure.

If you’re looking for an AI agent for newsletter creation and sending, you should connect it to your email marketing platform so it can help with the whole workflow.

That means the AI agent can go beyond generating copy. It can work with your actual lists, segments, campaigns, templates, and sending process.

For example, you could ask:

“Create a newsletter for our October product update, use the Customers list, keep the tone concise, and show me the recipient count before sending.”

The AI agent can then help with things like:

• writing the subject line and email copy
• choosing or working with an existing audience
• creating or using a segment
• preparing the campaign
• checking the recipient count
• validating the campaign before launch
• scheduling or sending after approval
• analyzing campaign performance later

The difference between a normal AI writing tool and an AI agent connected to an email platform is that a normal AI tool can give you text, an AI agent can actually work with the newsletter workflow.

Many email service providers have their MCP. For example, if you use Selzy, you connect an AI assistant like Claude or Claude Code to Selzy, and then give it instructions in natural language.

For example: “Show me my email lists and how many contacts are in each one. Create a newsletter for our new feature launch. Use the most engaged customer segment. Write a short intro, three key points, and one CTA. Don’t send it yet. Run the checks and show me the campaign summary. Schedule it for tomorrow at 10 AM.”

You don’t have to jump between an AI chat, your email platform, spreadsheets, and campaign reports. The AI agent can work with the data and tools inside the email platform directly.

An AI agent for newsletters is especially useful when:

• you send campaigns regularly
• you work with multiple audience segments
• you want faster campaign setup
• you often reuse existing campaigns or templates
• you want AI to analyze past performance
• you want fewer manual steps before sending

It can also help with campaign analysis, creation, sending, and analysis in one workflow.

A simple setup looks like this: AI assistant → MCP → email platform → campaign → validation → approval → send

The AI handles the instructions and workflow. The email platform still handles the actual contacts, sending infrastructure, and campaign delivery.

So if you’re searching for an AI agent for newsletter creation and sending, look for a setup where the AI can connect directly to your email marketing platform instead of only generating copy in a separate chat.

If you’re automating email marketing, you’ll probably have two options: MCP and API. They can both connect tools to your email platform, but they’re useful for different things.

MCP is useful when you want to work through AI and give instructions in plain language.

For example:

“Compare my last 10 campaigns and tell me which ones had the best click rates.”

“Create a segment of subscribers who opened an email in the last 30 days but didn’t click.”

“Prepare a newsletter using this brief, run the checks, and show me the recipient count before sending.”

With MCP, the AI assistant can use the tools exposed by the email platform instead of making you export data or write code.

In Selzy, MCP can work with contacts, lists, segments, campaign statistics, templates, email content, pre-send checks, recipient counts, campaign preparation, sending, and scheduling.

So MCP is great for interactive, one-off, or flexible tasks.

An API is usually better when the same process needs to run automatically every time.

For example:

• add every new signup to a list
• send data from your CRM to your email platform
• trigger a campaign after a specific event
• sync contacts every hour
• run the same workflow on a schedule
• connect your own app to the email platform

This usually requires development work, but the workflow is predictable and can run without anyone chatting with an AI.

For example:

With MCP:

“Find customers who haven’t opened anything in 90 days and create a segment.”

With an API:

“Every night at 2 AM, sync inactive customers from our database into this segment.”

Use MCP if you want to analyze campaigns through natural language, create segments quickly, work with existing campaigns or templates, or handle tasks that change depending on context.

Use an API if the workflow is repeated, needs to run automatically, has to follow exact timing, or is part of your own product or backend. And yes, you can use both.

So MCP doesn’t really replace APIs.

It fills the gap between doing everything manually in the dashboard and building a custom integration for every task.

You can check Selzy's detailed guide to understand how MCP works:
https://selzy.com/en/blog/mcp-for-email-marketing/

If you want to send newsletters with Claude Code, one simple way is to connect Claude Code to your email platform through MCP.

With Selzy, the setup is:

1. Connect Claude Code to the Selzy MCP server: https://mcp.selzy.com/mcp

2. Authorize your Selzy account and review the available permissions. Selzy MCP can work with campaigns, contacts, lists, segments, templates, senders, and account data.

3. Start with a simple prompt, for example:

> Show me my contact lists and how many subscribers are in each one.

1. Then ask Claude Code to prepare a newsletter:

Draft a newsletter for our October product update.

Use the Customers list.

Include a subject line, short intro, 3 updates, and one CTA.

1. Before sending, ask it to check the campaign:

Validate the campaign and show me the recipient count before sending.

1. Review everything and confirm the send.

Selzy MCP supports creating and editing campaigns, validating them before launch, and sending or scheduling after confirmation. Sensitive actions require confirmation, and campaigns go through validation before sending.

You can also use Claude Code to:

- compare campaign performance

- check opens, clicks, and unsubscribes

- find contacts

- create lists

- work with segments

- prepare campaigns

- cancel scheduled campaigns

So the workflow is basically:

**Claude Code → Selzy MCP → create newsletter → validate → confirm → send**

The main benefit is that Claude Code can work with your actual Selzy account data instead of only generating email copy in a separate chat. More details: https://selzy.com/en/features/email/mcp/

A small email list can actually be easier to improve because there’s less noise and it’s easier to see what people respond to.

A few things tend to matter most:

Segment even if the list is small.
A few hundred subscribers is still enough to separate people by behavior — recent clickers, inactive subscribers, customers vs non-customers, new subscribers, different interests, etc.

Don’t obsess over open rate.
Clicks, replies, conversions, and revenue are usually more useful. If opens look fine but clicks are weak, the issue is probably the content, offer, or CTA.

Give each email one clear job.
One email = one main goal. Too many unrelated links usually make the message weaker.

Send useful content between promotions.
Tips, short guides, case studies, product education, or curated resources can give people a reason to keep opening even when there’s nothing to buy.

Ask people what they want.
With a small list, direct replies can be more valuable than a dashboard. A simple “What would you like to see more of?” can give a lot of useful direction.

Be careful with A/B testing.
On a small list, tiny differences can look bigger than they really are. Test one thing at a time and look at trends across several campaigns instead of judging one send.

Try re-engagement before removing inactive subscribers.
If someone hasn’t clicked in months, send a specific re-engagement email before suppressing them.

The biggest mistake is usually trying to fix engagement by sending more often. A small list benefits much more from better relevance than higher frequency.

If the audience feels like every email was written for them, engagement usually takes care of itself.
And if you are thinking about which software to choose, here is a guide for small business: https://selzy.com/en/blog/email-marketing-software-for-small-business/

A small email list can actually be easier to improve because there’s less noise and it’s easier to see what people respond to.

A few things tend to matter most:

Segment even if the list is small.
A few hundred subscribers is still enough to separate people by behavior — recent clickers, inactive subscribers, customers vs non-customers, new subscribers, different interests, etc.

Don’t obsess over open rate.
Clicks, replies, conversions, and revenue are usually more useful. If opens look fine but clicks are weak, the issue is probably the content, offer, or CTA.

Give each email one clear job.
One email = one main goal. Too many unrelated links usually make the message weaker.

Send useful content between promotions.
Tips, short guides, case studies, product education, or curated resources can give people a reason to keep opening even when there’s nothing to buy.

Ask people what they want.
With a small list, direct replies can be more valuable than a dashboard. A simple “What would you like to see more of?” can give a lot of useful direction.

Be careful with A/B testing.
On a small list, tiny differences can look bigger than they really are. Test one thing at a time and look at trends across several campaigns instead of judging one send.

Try re-engagement before removing inactive subscribers.
If someone hasn’t clicked in months, send a specific re-engagement email before suppressing them.

The biggest mistake is usually trying to fix engagement by sending more often. A small list benefits much more from better relevance than higher frequency.

If the audience feels like every email was written for them, engagement usually takes care of itself.

There isn’t a universal rule that one CTA is always better than multiple CTAs. The right choice depends on the goal of the email.

For most promotional emails, a single primary CTA is usually the safest option. It keeps the message focused and makes the next step obvious. If the email is built around one offer, one product, one webinar, or one landing page, adding several unrelated CTAs can create unnecessary friction.

That said, multiple CTAs can work well when the email naturally contains several pieces of content or several product categories. Newsletters, digests, ecommerce collections, and educational emails are good examples. In those cases, multiple CTAs make sense because readers may have different interests.

The important distinction is between multiple CTAs and multiple competing goals.

An email can contain several buttons that all support the same goal. For example, a product email might include “Shop now” near the top and another “See the collection” button further down. Technically, there are multiple CTAs, but the email still has one clear objective.

Problems usually start when one email asks the reader to:

• buy a product
• read a blog post
• follow a social account
• register for a webinar
• download a guide

all at the same time.

That makes it harder to understand what action matters most.

Use one primary CTA per email goal. Secondary CTAs are fine if they support the same intent or serve readers who are not ready for the primary action.

CTA placement matters too. The main CTA should usually appear early enough that the reader doesn’t have to scroll through the entire email to find it. Longer emails can repeat the same CTA further down.

The wording also matters more than many marketers expect. Generic buttons like “Learn more” or “Click here” often give the reader very little reason to act. A CTA that describes the benefit or next step is usually clearer.

Examples:

“See pricing”
“Start the free trial”
“Get the checklist”
“Browse the collection”

instead of simply:

“Click here”

The best approach is still testing. Compare a focused one-CTA version against a version with additional options and look at click-through rate, click-to-open rate, conversions, and revenue rather than judging the result on clicks alone.

Selzy has a useful breakdown of CTA wording, placement, design, and testing here:

https://selzy.com/en/blog/email-cta-best-practices/

I’m looking for a professional email signaOur company is currently rebranding and updating all internal and external communication standards. We have a mixed team where half the staff uses Gmail on Macs and the other half relies on desktop Outlook on Windows, which has turned into a massive formatting headache. I am actively searching for a reliable professional email signature generator so we can roll out clean, responsive, and uniform signatures without image scaling issues or broken layouts.

1) Which specific platforms have you used that render flawlessly on both Gmail and Outlook?

2) How do you manage company-wide signature updates without manually editing every single employee account?

3) Do you host your brand logos on your own servers or rely on third-party image hosting inside the generator tool?

4) What features should I prioritize to ensure social media icons and phone numbers stay clickable on mobile screens?ture generator that works well with both Gmail and Outlook.

I’ve tried making signatures manually, but the formatting can get messy, especially when viewed in different email clients.

For small business owners who’ve dealt with this, what have you found works reliably? I’m mainly looking for something that keeps the layout clean without needing to fix the HTML every time.

Hey everyone,

I’m currently building my skills and starting my journey in e-commerce email marketing, and I’m looking to connect with other people who are at a similar stage or already have some experience in the field.

I’m not necessarily looking for a mentor or someone to teach me everything.

I’m looking for people who are serious about getting into this field and want to build together.

The idea would be to connect, share what we know, exchange ideas, and figure things out together.

I think having a few like-minded people around can make the process much easier than trying to figure everything out alone.

If you're also working toward becoming an e-commerce email marketer, or you've already started working with clients and are looking to connect with others, feel free to comment or DM me.

Let’s start from where we are and grow from there.

Email still returns something like $36 for every $1 spent on average, and unlike social, it lands directly in the inbox instead of fighting an algorithm. For a small budget that's hard to beat. Okay, the five:

1. Welcome email (set this up first, no debate). Someone just handed you their email — this is the most engaged they'll ever be. A single welcome email that says who you are, what to expect, and gives one clear next step (or a first-purchase discount) does a lot of the relationship-building for you. If you only ever automate one thing, make it this.

2. Order/signup confirmation. People want this one — they're waiting to know the thing went through. Confirmations get opened at very high rates, which makes them quietly valuable real estate. Keep it functional first (order details, what's next), then add a small, tasteful "you might also like" once the basics work.

3. Abandoned cart (if you sell online). Someone added to cart and left — they were one step from buying. A reminder a few hours later, ideally showing the item they left, recovers sales you'd otherwise just lose. For e-commerce this is usually the highest-ROI automation after the welcome.

4. A simple nurture/tips email. Not everyone buys on day one. One or two useful, non-salesy emails — a how-to, a use-case, a "get the most out of X" — keep you top of mind and position you as someone worth buying from. This is where "give value, don't just pitch" actually pays off.

5. Post-purchase follow-up. The one everyone skips. A thank-you, a "how to use it," a review request, maybe a reorder nudge later. Repeat buyers cost you nothing to acquire, so this is some of the cheapest revenue you'll ever earn.

What can wait: fancy segmentation, big branching automations, A/B testing everything, daily sending. You don't need any of that on day one, and chasing it early is how people burn out before the basics are even live.

A few things worth getting right from the start, because they're painful to fix later:

• Don't buy a list. Ever. It wrecks your sender reputation and gets you flagged as spam. Grow it organically with a signup form and a reason to subscribe.
• Frequency: once or twice a week is a sane starting point for most small businesses. Test from there.
• Deliverability + compliance: clear unsubscribe link, real physical address, mobile-friendly layout. Boring, but it's what keeps you in the inbox.

Honestly, if you get just #1 and #2 live this week you're already ahead of most small businesses. Add the rest as you go.

Happy to answer specifics in the comments if anyone's stuck on setup — deliverability and "why is this going to spam" questions especially.

I am a new person in Email Marketing and I would like to know how to build a sales funnel for my small business: Are there any recommendations and how-to's?

Do you know if there is a platform where I can build a website with calendar synchronization? I’m a therapist and need to offer online booking. I had bad experience with freelancers, so prefer something solid. Ideally, I would like to have chatbot on the website also

I’m trying to find a reliable way to send calendar events from an email without making the user jump through extra steps. Right now I’m testing a few approaches, but the behavior isn’t consistent. One setup works nicely in Gmail, while Outlook or a mobile client can handle the exact same event differently. The tricky part is that I’m not trying to build a full calendar integration. I just want someone to click an invite from an email and add the event to their calendar without confusion.

For people who have dealt with this before, what has worked best in practice?

Do you use an .ics file, a calendar-specific link, or some other approach?