Email automation that runs itself.
Overvio flows are the emails that send themselves. You set one up once: a welcome for new subscribers, a nudge for a cart left behind, a check-in after a first order. And it runs on its own, day and night, greeting the right shopper at the right moment. And no flow takes credit on its own say-so. The order has to come back confirmed by your store before it counts. WooCommerce or custom-built, every flow is yours to shape.
Deepest on WooCommerce, where a left cart or a first order can start a flow the moment it happens, and custom-built stores join in a few clicks.
See the WooCommerce integrationRunning now
The flows already working for you.
- Welcomenew subscribers
- Cart nudgeleft carts
- Thank-youafter a first order
Each one runs on its own, day and night, without you touching it.
And when she buys
Confirmed: this flow earned this order.
It counts once your store says the order is real, with refunds subtracted.
You set it up once. It works forever.
A flow is a small set of emails that sends itself when a shopper does something. You build it once; from then on it runs for every shopper on her own clock. Here it is, piece by piece.
You set it up once.
Start from a ready-made flow: a welcome, a cart nudge, a post-order thank-you, a win-back for shoppers who have gone quiet. Or build your own. You do the thinking once; you never have to sit and send these by hand again.
What starts a flow
- A new subscriber
- A cart left behind
- A first order
- A date you chose
It waits for the right moment.
A shopper joins your list, leaves a full cart, places her first order, or a date you chose comes around, and that is what starts her flow. It begins for her alone, timed to land when she is likely to read it, not the second the tab closes.
Welcome series
Automatic- First hellothe moment she joins
- A gentle nudgeif the first goes unread
- The thank-youafter she buys
The emails send themselves.
The flow runs its course on its own: a first hello, a gentle follow-up if the first goes unread. Each email is written, on-brand, and carrying whatever it should. Edit any step whenever it suits you: what it says, how it looks, how long it waits before the next one.
See the cart-recovery flowHouse rules
- She buys: the flow ends.
- She opts out: she stays opted out.
It knows when to stop.
The moment she buys, her flow ends on its own. Nobody is chased over something they already did. Anyone who opts out stays opted out, and no shopper is ever caught in two flows saying the same thing twice.
Flow result
This flow earned this order.
Confirmed by your store · net of refunds
The receipt, not a guess.
An order that follows a flow is not waved through. It is checked against your store, matched to the flow that caused it, and entered with refunds already off. What a flow earned while you slept is written down where you can read it in the morning.
Automated revenue you can defend.
An automation that runs day and night produces a lot of 'maybe that was us' sales. Overvio refuses the maybe: a flow is credited only for orders your store confirms it caused, and everything vaguer is kept apart.
Confirmed: counted
She came back through a flow, and your store confirmed the order.
Only confirmed orders make this line, already net of refunds. Flow revenue means nothing less.
Counted: set aside
She got a flow email, then bought later through another door.
Maybe the flow nudged her, maybe not. Your store never confirmed the link. It stays visible, kept apart, and out of the revenue line.
In your analytics each flow shows exactly what it can prove: the confirmed orders it earned, and separately, the sales it merely preceded.
See how it is proven in analyticsThe whole automation kit, in plain words.
| What you get | What it does |
|---|---|
| Ready-made flows | Start from a welcome, a cart nudge, a post-order thank-you, or a win-back: proven shapes, yours to change. |
| Your own triggers | Start a flow when someone joins, leaves a cart, places a first order, or a date comes around. You choose. |
| Written emails | Every step arrives laid out and on-brand; adjust the copy, the design, or the gaps between emails at any time. |
| Knows when to stop | The moment a shopper buys or opts out, her flow ends on its own: no chasing, no two flows saying the same thing. |
| Runs for everyone at once | Each flow runs for every shopper on her own clock, day and night, without you sending a single email by hand. |
| Proof on every order | Each order a flow earns arrives with its receipt: the flow named, the sale store-confirmed, refunds out. |
| Consent, handled | A flow never writes to someone who declined, and an opt-out ends the conversation for good. Data requests are ready the moment they arrive. |
A flow is only as strong as what it can reach, and here it reaches your list, your coupons, and your proof in one place.
Before you switch one on.
Before you let emails send themselves, you deserve straight answers. These are the ones owners ask first. Anything further, just write in.
No. Overvio ships ready-made flows: a welcome, a cart nudge, a post-order thank-you, a win-back, already written and ready to switch on. Reword them, restyle them, retime them. Or run them exactly as they ship.
A shopper joining your list, leaving a full cart, placing a first order, or a date you chose: a birthday, an anniversary of their first purchase. You pick what starts each flow, and it begins only for the shopper who did that thing.
No. The moment your store confirms her order, her flow ends on its own. Nobody is chased over something they already did, and no shopper is caught in two flows saying the same thing twice.
Cart recovery is one kind of flow, the one that starts when a full cart is left behind. Flows are the wider idea: welcomes, thank-yous, win-backs, and more, each running on its own.
When your store confirms an order and the flow can be shown to have caused it, that, minus refunds, is flow revenue. Nothing looser makes the cut; the near-misses stay listed in a column of their own.
WooCommerce stores plug in deepest: the moment a cart is left or a first order lands, the right flow can start, and setup is a few clicks. A shop built just for you can run the same flows. That kind of store is familiar ground here, not an exception. A developer never enters into it.
Your next flow can run itself.
Connect your WooCommerce store, switch on a ready-made flow, and it starts greeting the right shoppers the same day, with a number you can stand behind.
Prefer to ask something first? Ask a question