The Anti-Churn Architecture: 6 Plain-Text Emails to Keep Customers (and How to Build Them)

When a customer is frustrated by a delayed order, hesitating at checkout or not opening a single email, the last thing they want to see is an impersonal, generic HTML email.

In those key moments, polished graphics look like a textbook corporate reply, when what the customer is looking for is human contact.

We touched on this recently in an article I wrote for the official Omnisend blog on unconventional email flows. That article breaks down the exact technical execution of some of these plain-text strategies, alongside new high-impact flows.

At STRAT, as an official agency partner of Omnisend and Klaviyo, we analyse millions of customer touchpoints. The data shows a clear pattern. Whether you are resolving a logistics friction or looking after your best customer, the plain-text email beats HTML by a notable margin. It sidesteps the Promotions tab, builds immediate trust and triggers a specific psychological response: that the customer is talking directly to a person.

Here, step by step, are 6 ideas for how to automate plain-text flows that turn logistics nightmares, abandoned checkouts and VIP purchases into long-term brand loyalty.

Plain text does not replace HTML, it complements it

Before we get into it, an important nuance so the idea is not misread. This is not about getting rid of designed email. HTML is still king for selling products, telling brand stories and showing off product, which is exactly what is needed in verticals like fashion, beauty or home decor.

Plain text plays in a different league, that of operational and relational moments: an incident, a doubt, a thank-you, a goodbye. There, design gets in the way. The key is knowing which strategy fits each moment, not always using the same one.

The psychology of plain text in ecommerce

Most ecommerce brands lean heavily on the visual. And it makes sense for selling. But post-sale operations and technical support call for a different tone.

When you send a plain-text email from a real person (for example, "Alex from [Brand]" or "Alex García" instead of "Customer Service" or "Brand"), you start a one-to-one conversation. The customer assumes someone wrote that email specifically for them. That perceived effort creates an emotional connection HTML cannot replicate.

Scenario 1: the "proactive delay" flow

In an era where deliveries are expected in under 24 hours, shipping delays are the number one cause of poor brand perception. The worst strategy is silence. If the customer has to write to you first to ask "where is my order?", you have already lost the battle for trust.

You do not need third-party tracking apps to solve it, you can build it with your online store's own fulfilment data.

The technical setup

1. The trigger: use the order-placed metric as the starting point.
2. The delay and the logic: set a delay in the flow (for example, 10 to 15 days, depending on your usual shipping times). Add a conditional filter, so it only continues if the order-shipped metric has occurred ZERO times since the flow started.
3. The exclusion: leave out anyone who has already opened a ticket in your support tool, so you do not duplicate the communication.

The plain-text template

Scenario 2: the "intercept the review" flow

A 1-star review is not the end of a relationship, it is a cry for help. Handled well, an unhappy customer can become one of your biggest advocates.

The technical setup

1. The trigger: integrate your reviews platform (Yotpo, Okendo, Judge.me...) with your email marketing platform.
2. The logic: trigger the flow when a customer leaves a 1 or 2-star review.
3. The delay: set a delay of 30 to 60 minutes. An immediate reply looks automatic; a slight delay looks like a person has just seen the alert and is getting in touch.

The plain-text template

Scenario 3: the "checkout friction" flow

Most abandoned-cart flows lean on scarcity ("your cart is expiring!") or on an aggressive discount. But a lot of people do not abandon over price, but over a technical friction (a declined card, a confusing size guide or a checkout glitch).

Sending a plain-text customer-service message as the second email in your abandoned-checkout sequence captures the high-intent shoppers who just need a hand. We develop it in full in our guide to recovering abandoned carts.

The technical setup

1. The trigger: checkout started, filtered by order-placed equal to zero times (since the checkout began).
2. The delay: send this email 24 hours after your first HTML cart reminder, and send it in the morning (so it feels more real).
3. The logic: filter out anyone who has already received this specific email, because getting it more than once gives away that it is automated. (You could also make slight variations and send one or another depending on how many times they have entered the flow.)

The plain-text template

Scenario 4: the "high-value VIP welcome" flow

When a customer spends a significant amount of money on your brand, dropping them into a generic HTML post-purchase flow is a letdown. You want them to feel like an investor in your brand.

The technical setup

1. The trigger: order placed.
2. The logic: add a value filter, so it triggers only if the total order value exceeds X (for example, the threshold of your top 5% highest-value orders) or if the historical LTV crosses an important milestone (for example, more than €2,000 spent).
3. The exclusion: cancel the standard "thanks for your purchase" email for this specific segment, so you do not clutter their inbox.

The plain-text template

Scenario 5: the "zero-party data" flow (feedback)

Long Typeform-style surveys tend to have low completion rates. If you want quality qualitative feedback on your products, stripping out the design and asking a single question gets huge results.

The technical setup

1. The trigger: order placed.
2. The delay: 30 to 45 days after shipping (giving the customer time to really use the product; you can adapt it to how long the customer takes to use it).
3. The logic: exclude anyone who has started a return or left a negative review (they have already given their feedback).

The plain-text template

Scenario 6: the "goodbye" flow to win back (sunset)

List hygiene is key to deliverability. If a customer does not open an email or visit your store in 6 to 12 months, keeping them on your active list damages your sender reputation. But before removing them entirely, a plain-text "goodbye" email usually achieves the highest open and reactivation rate of the whole year.

The technical setup

1. The segment: customers inactive for 180 days or more (0 opens, 0 clicks, 0 site visits).
2. The position: this should be the last email in your win-back or sunset flow, sent after they have ignored your last discount offer.
3. The action: if they do not open or click this email within 7 days, an automation rule should suppress their profile automatically or add a tag to remove them manually.

The plain-text template

Deliverability, the hidden benefit of plain text

Beyond the psychology, plain text is a great asset for deliverability. Email clients like Gmail and Apple Mail constantly analyse emails to classify them. An email loaded with HTML, with many links and images, is instantly flagged as commercial and ends up in the Promotions tab.

Because operational plain-text emails do not carry that heavy HTML and usually have very few links, they are far more likely to land straight in the primary inbox.

Stop treating operations like marketing

Automation should not only serve to drive the next sale, it also has to protect the sales you have already made. With well-designed plain-text flows, you reduce your volume of support tickets, soften negative reviews, gather very valuable product feedback and protect your customer lifetime value (LTV).

The underlying question is simple: do your automated flows protect your margin or damage your brand?

Frequently asked questions

Why does a plain-text email work better than an HTML one in these cases? Because it looks written by a person, not by a marketing department. In operational or delicate moments (a delay, an incident, a thank-you) that lowers the tension, builds trust and creates a connection design does not replicate. It also tends to reach the primary inbox rather than Promotions.

Does plain text replace designed emails? No. HTML is still best for selling collections, telling the brand story and showing off product. Plain text is for operational and relational moments. The smart thing is to use each where it performs, not to replace one with the other.

When is it worth using plain text? For shipping delays, replies to negative reviews, abandoned-checkout check-ins, welcomes for high-value VIP customers, feedback requests and goodbye or reactivation emails. In general, for anything that is operations or relationship, not promotion.

Does plain text improve deliverability? It usually helps. By not carrying heavy HTML or many links and images, filters classify it as commercial less often, so it stands a better chance of reaching the primary inbox.

Can these flows be automated in Klaviyo and Omnisend? Yes. All six flows are built with triggers, filters and delays in platforms like Klaviyo or Omnisend, connected to your store's data. At STRAT, as an agency partner of both, that is exactly what we build.

Do your automated flows protect your margin or damage your brand? Let our retention team analyse your customer journey and tell you where you are losing customers. We look at it in our ecommerce email marketing agency.