Automated flows
Welcome, abandoned cart, post-purchase, win-back and reorder, triggered on behaviour and branched on what the customer did next
flows that keep sending through a week nobody is in the office
Email marketing · UAE
A rented list carries somebody else's consent, not yours. Webzenia settles what your list actually is, authenticates the domain it sends from, and builds the flows that run without anyone touching them.
Get a straight answer on your listWhat the programme runs on
Email is the one channel where you own the list, the domain and the record. In the UAE that ownership is the whole argument, because consent here belongs to the sender.
An Al Quoz fragrance producer on a DET mainland licence usually holds two lists: one built from its own orders, and one somebody sold it two years ago. Only the first is an asset, and the difference is a record showing who opted in, when, and to what.
A JLT commodities firm under DMCC sending a monthly newsletter from an unauthenticated domain is invisible to itself and to half its recipients. SPF, DKIM and DMARC decide whether the send arrives, and no platform subscription supplies them for you.
One campaign, two language variants, one window, keyed on a preference the subscriber gave you. The flows underneath it run on behaviour rather than on someone remembering, which is what makes the channel worth owning at all.
Why the monthly send keeps underperforming
A blast is one bet placed on one morning. In a market where your reachable list is small, a bad bet costs more than a bad month.
| The monthly blastOccasional, and to everyone | Behavioural flowsAlways on, always narrow | |
|---|---|---|
| When it sends | On the morning somebody finally had time to write it. | At the hour the customer did something that says they are ready. |
| Who receives it | Everyone, including the people who stopped opening a year ago. | The segment the trigger defined, a few hundred people at a time. |
| What a bad send costs | Standing with the mailbox providers, across the whole list at once. | One segment, and the flow is edited the same afternoon. |
| Who has to be there | Somebody, every time, or the channel goes quiet. | Nobody. It runs on the trigger, through a holiday week. |
| What it becomes | A recurring task competing with everything else that week. | An asset that keeps working when the calendar is empty. |
Into the list and the domain, before a single flow is built. A programme built on an unverified list and an unauthenticated domain will underperform for reasons no subject-line test can find, and both are fixed once rather than tuned forever. Flows come second, campaigns third. What the same list is worth as an advertising audience, and how it is fed back to the platforms, is set out on digital marketing in Dubai.
The UAE context
Webzenia has worked with Gulf clients since 2018. None of these is about the template, and each one changes the programme before the first send.
The PDPL makes consent the primary lawful basis, given to a named controller for a named purpose. An address collected by somebody else, for somebody else, was never given to you, which is why a two-million-contact database is a liability someone charged you for.
Most companies selling here arrived rather than started, so the sending domain is often months old or newly split from a group one. A mailbox provider has no history to judge it on, and the first large send is where that shows up, as a spam folder.
Registered sender IDs, the AD- prefix and the calling window are SMS and telephone rules. Email answers to the PDPL and to the mailbox provider, which wants authenticated sending and an unsubscribe that works. Programmes here regularly end up compliant on the channel they do not use.
A UAE list holds both readerships at once, so language is captured at the opt-in and stored on the contact. Split it into two lists and the segments drift apart within a quarter: a Dubai Marina clinic on a DHA licence ends with two versions of the same patient.
What the work includes
Six pieces of work, each producing something you keep. The first two decide whether the other four are worth building.
Welcome, abandoned cart, post-purchase, win-back and reorder, triggered on behaviour and branched on what the customer did next
flows that keep sending through a week nobody is in the office
Segments defined by what people actually did, with the language preference sitting alongside the behaviour so a send never has to guess
live segments with the rule written beside each one
The same lifecycle across email and a chat thread, where the thread genuinely helps. The escalation here is a message, never a call: WhatsApp marketing owns that surface
one lifecycle, two channels
The campaign layer on top of the flows, with subject lines tested against each other and both language variants shipped inside one send rather than as two jobs
a tested campaign, in both scripts
SPF, DKIM and DMARC on your sending domain, a double opt-in record carrying the date and the source per subscriber, and the capture point rebuilt with landing page design where one is needed
sending you can evidence
Each flow reported on its own line with the revenue it produced, so a flow that has stopped earning is rebuilt rather than left running quietly
a monthly read of the programme, flow by flow
Our stack
The kit behind a send that is lawful, authenticated and readable in both scripts. Select one to see why it earns its place, and where we argue against it.
Klaviyo holds the order history, the behaviour and the consent on one profile, which is what lets a flow branch on what somebody bought rather than on which list they sit in.
We store the opt-in source and its date as profile properties, so a consent claim is answered by opening the record instead of by remembering the campaign that collected it.
How the engagement runs
The first two weeks are spent establishing what the list is. Everything after that is build, and nothing is built on a list we cannot stand behind.
We trace every segment back to where it came from and what the person agreed to, then separate the part you can evidence from the part you cannot. Where a list was bought, rented or inherited, you get that in writing along with the two honest routes out: a re-permission campaign to the part that is still reachable, or starting clean. Most engagements find at least one segment nobody in the building can account for.
SPF, DKIM and DMARC go on the sending domain, the subdomain is separated from the one your invoices go out on, and volume is warmed rather than switched on. The opt-in is rebuilt at the same time, so every new subscriber arrives with a date, a source and a language against their name. This is the phase that decides whether anything built afterwards is ever seen.
Welcome, cart, post-purchase and win-back go in first, each branching on behaviour and sending in the language the subscriber chose. Campaigns are layered on afterwards, tested against each other, and the whole programme is reported flow by flow with the revenue beside each one. A flow that has stopped earning is rebuilt rather than left running quietly in the background.
Reported flow by flow, against the revenue each one produced.
Our commitment
Email is the easiest channel to run badly and the hardest to repair afterwards. These are the four things we hold ourselves to.
We will not send to a bought list
If we cannot evidence how a contact opted in, that segment does not receive a campaign from us. You get that before you have paid for a send, with the two routes actually open: re-permission what is reachable, or start clean.
Authentication before the first send
SPF, DKIM and DMARC are configured and verified on your sending domain before a campaign goes out, not after the first batch lands in a spam folder. Warm-up is treated as work with a schedule, rather than as something the platform handles.
We will argue for sending less.
When the complaint signal says a list is being over-mailed, we will say so and cut the frequency, including on a campaign you asked for. A list you can still send to next year is worth more than one extra send this month.
Unsubscribe works on the first click
One click, honoured immediately across every flow and campaign, with the Arabic saying exactly what the English says. A list somebody cannot leave is a list that generates complaints, and complaints close a sending domain.
Sent on a record we can produce, from a domain that is yours.
Common questions
Keep exploring
Search and Performance Max, built on what you may legally advertise.
Facebook and Instagram, built for an audience that saturates fast.
Reach a named few by title, once you know how many there are.
The ads buy the view. The channel is what keeps earning it.
A pool built on a basis you can produce, and on what it excludes.
Own accounts in two scripts, worked for enquiries not followers.
A cost per customer agreed in writing, then held to.
Enquiries captured, evidenced, and answered on a permitted rail.
Pipeline from the accounts your licence can actually invoice.
Next step
Tell us where the list came from and what you send today. We will come back with what is safe to send, what is not, and which flows are missing.
Tell us what you need.