Mediana Smart Campaign

Designing AI a shopkeeper can trust

About Project
Mediana is a B2B omni-channel communications platform (SMS, email, VOIP, marketing automation) serving ~500K business users who send 250–300M messages a month. Most of them are not marketers. The Smart Campaign lets them state a goal and receive a complete, editable campaign plan, and it was designed against the obvious 2025 answer, a chatbot, because a 30-participant study told us to.

Year
2025 – 2026
My Role
Product Design Director: design direction,
product structure,
AI-experience strategy, research design
Hands-on design: Faezeh Taheri, Principal Product Designer

The problem

A form that asks questions our users can't answer
Mediana's users are not marketers. They are shopkeepers, clinic managers, the PR person at a language school — people who know exactly what they want (“bring back my old customers”, “sell this product”) but not how to translate it into a campaign: which segment, what copy, which channel, what budget. The classic campaign builder assumed that translation was the user's job. Every question it asked — audience? copy? schedule? — was a question our users couldn't confidently answer. Campaigns didn't get made, or got made badly, and Mediana stayed what it had been for 14 years: a place to send raw SMS, not a place to do marketing. The business goal was equally clear — move Mediana from selling messages to being the tool where marketing decisions get made.

The research

Two prototypes, thirty people, one hour each
In 2025 the obvious answer was a chat box: describe your goal, get a campaign. It would have been fast to build and it would have demoed beautifully. We had one hypothesis in each hand — a conversational canvas versus a structured, step-by-step flow with AI at the decision points — and no evidence for either. So before committing engineering to a direction, we built both as prototypes and put them in front of users.
30 participants, 4 segments, one 60-minute session each — both prototypes, same person. Thirty-three were recruited: 11 existing Mediana Next customers, 8 brand-new users, 6 VIP accounts, and 5 resellers, who run campaigns for their own customers from the same panel. The first two sessions were treated as a pilot and one more was excluded as unusable, leaving 30 in the analysis.

Every task had two parts: build the campaign, then correct the system's proposal. Both prototypes had a lightweight model behind them so responses arrived at realistic speed, and each came with its own business scenario: a beauty clinic running a Mother's Day offer for the chat prototype, a café running a football-tournament promotion for the structured one. First, build: a defined audience, a defined offer, a deadline. Then, correct: the proposal comes back with the wrong budget, the wrong channel, too many recipients, or copy in the wrong tone; fix it, and press confirm only when you're sure. The second part matters, because real users don't just create campaigns, they argue with proposals. Participants thought aloud throughout.
The pilot changed three things. We counterbalanced the order of the two prototypes across participants to cancel learning and fatigue effects. We cut the buffer interview between tests from 30 to 15 minutes, because think-aloud sessions ran long. And we rewrote the tasks to include real constraints, after the first two sessions showed that generic tasks produce generic behavior.

What we measured
Three behaviors we watched for, named up front.

Prompt paralysis: long pauses; typing a sentence, deleting it, typing it again, because the user doesn't know what the system wants.

Losing the map: "if I write this, what happens next? Where do I say which channel?"

Perceived effort: the sigh. Does a long form, or an empty chat box, feel heavier?

We scored each prototype on six metrics, half behavioral (what people did), half attitudinal (what they told us afterwards), weighted into a single 0–100 score.

What we found
The structured path won on every metric, for every participant.
Each of the six differences was significant (paired t-test, n = 30, p < 0.001 across the board), and the composite moved from 41 to 76. The largest gap was clarity, "how clear was it where to start and what steps lay ahead?", from 35 to 81. That is the number behind the whole design decision: the chat box wasn't harder to use; it was harder to place yourself in.

Facing the chat box, the median participant waited 15.9 seconds before doing anything; on the structured path, 8.4. Eighteen of thirty waited longer than 15 seconds in chat; nobody did on the structured path. In the chat prototype, nobody finished a task with fewer than two errors (deleted prompts, back-steps, dead clicks), and 23 of 30 reached for a suggestion or placeholder three or more times just to get started.
What we heard
The numbers say what; the think-aloud said why. Three moments, from three different participants.

“Oh, come on. Here too I have to chat? This is for the generation after mine.
My son only works with these things; I can't make sense of them.”
— on first seeing the chat screen

“So… what happened? Why isn't it loading? Is it stuck?”
— after a 16-second pause on the empty chat box, waiting for the system to make the first move

“If I type this, won't it just go ahead and send the message to those five million people?”
— mid-task in the chat prototype

The third quote was the most important sentence in the study. It wasn't about usability. It was about irreversibility: on a platform where every send costs money and cannot be unsent, an interface that might act on its own is frightening no matter how easy it is. That fear shaped the trust architecture below more than any usability score did.

The defining decision

Rejecting the chatbot
Thirty out of thirty. We rejected the trend and named what we built instead: AI-Assisted UX. The structure stays familiar, with visible steps, clear progress and everything inspectable, and AI enters only at the decision points where users actually get stuck: writing the copy, choosing the audience, framing the marketing approach. The user always sees a plan before anything runs, and always decides.
The user states the goal, the system drafts the plan, the human approves the plan. What the research changed was not just the interface pattern but the order of priorities. Clarity of the path scored higher than ease of use in every session, so the design optimizes first for "I know where I am and what happens next", and only then for speed.

How it works

Three entry routes, not one prompt box
Three ways in: a product URL, nothing at all, or a plain-language request. The smart campaign is one of four campaign types on the platform — its siblings cover manual audiences, VIP-curated banks, and retargeting by behavioral tags — but it's the one built for the user who has a goal and nothing else. With a product URL, the system reads the page and infers the campaign's intent from the artifact itself. With nothing online at all, the user enters raw product details and the AI generates a landing page — for many offline businesses, their first usable digital asset. Or the user simply describes what they want.

Three ways in, one screen: a product link, a landing page the system builds for you, or a plain-language request. The rest of the flow waits until the user has chosen.

A goal goes in; an editable plan comes out
The system doesn't execute; it proposes. From that intent it drafts complete campaign packages, each bundling a suggested audience, message copy, and the marketing approach behind them. The approach is stated explicitly, because a plan you can't interrogate is a plan you can't trust. Every part of a package is editable, and the parts stay honest with each other: edit the message, and the audience is re-proposed to match it. The campaign's intent lives in the message the user actually sends, not in a form they filled three steps ago.
Mediana smart campaign: online-product route with collapsed steps

The online-product route. Paste a link and the system reads the page before it proposes anything; each step below opens into an editable proposal.

The plan you approve
Nothing runs until the user says so. Before anything is sent, the whole plan is laid out on one screen — the message, the proposed audiences with the reasoning behind them, the channels, the schedule, the cost — under one heading: “Needs your approval.” It is the least glamorous screen in the product and the most important one: it is where “AI proposes, the human decides” stops being a principle and becomes an interface.
Mediana smart campaign: the campaign review screen — message, proposed audiences, channels and cost under 'Needs your approval'

The approval screen. Message, proposed audiences with the reasoning behind them, channels and cost on one page — nothing is sent until the user confirms.

The trust architecture

“AI proposes, human decides” has to be engineered, not promised. “Won't it just send it to five million people?” On a platform where every send costs real money and cannot be unsent, four mechanics carry the weight, and each one answers a specific fear we heard in the room:
1. Subset control. “It will send to everyone.” After audiences are proposed, the user chooses to send to all of them or only part. The system's output is a starting point, never a commitment.
2. Exclusion. “It will bother people I already messaged.” Users exclude groups such as recipients of previous campaigns, turning mass sending into relationship management.
3. Gradual delivery. “Once it goes, it's gone.” Alongside “now” and “scheduled”, a campaign can run gradually, so the send becomes a monitorable process instead of a single irreversible action.
4. A report that talks back. “I won't understand what happened.” After (and during) a campaign, users get delivery, engagement, cost and demographic breakdowns plus an AI-written summary they can question conversationally. On gradual campaigns that closes the loop: analyze mid-flight, adjust, continue.
Mediana campaign analytics report with AI-written summary, delivery, engagement and demographic breakdowns

The campaign report. Delivery, engagement and demographic breakdowns, with an AI-written summary the user can question in plain language.

The offline route

A landing page as a first digital asset
This is the one place we kept a conversation, on purpose. Many of Mediana's customers have no website, no product page, nothing to point an AI at. For them the smart campaign generates the missing artifact: the user describes the product in plain terms, a short conversational assistant shapes the details, and the system produces a landing page, then runs the same propose-and-approve flow on top of it. The first version of this step was a form; it never shipped. Instead we chose the lowest-risk step in the flow, one with no money on the line and a visible outcome, and left the chat there as a live experiment. If people are comfortable talking to the system when nothing can go wrong, a fully conversational option becomes something we can offer later, backed by evidence rather than by trend. For an offline shop the result is often the first digital asset they have ever owned.
Mediana smart campaign: AI landing-page generator for offline businesses

The offline route. A short, bounded conversation collects product details before the system builds a landing page — the one place we kept chat, on purpose.

Where it stands

Live on both panels; results claims on hold until the rollout completes. The smart campaign runs on the direct Mediana Next panel and the reseller-facing IPPanel, which puts it in front of the platform's full base of ~500K business users. The signal we watch most closely is the edit rate: how often people correct the system's proposals is the truest measure of whether those proposals deserve the trust the interface asks for.
Mediana smart campaign: request submitted confirmation

Request submitted. The campaign is queued, and the user knows exactly what happens next.

What I'd tell another design team

1. The prompt box is not the product. Our users' problem was never typing; it was decision confidence. Structure gives confidence; AI fills the gaps inside it. Thirty out of thirty told us so before we wrote a line of production code.
2. Explain the plan, not just the output. Bundling the marketing approach with each proposal did more for trust than any accuracy improvement.
3. Listen for the fear, not just the friction. The most useful sentence in the study wasn't about ease of use; it was "won't it just send it?" Usability metrics would never have surfaced that. Think-aloud did.
4. Keep intent and execution coupled. Re-proposing audiences when the message changes is one small interaction, and it's the difference between a form with AI sprinkled on it and a system that understands what you're trying to do.
Sequencing autonomy
Each release, the system earns the right to one more decision. The same philosophy is expanding deliberately, one decision at a time: channel selection is next in line to move from the user to the system. That sequencing, more than any single feature, is what I'd call the design of the product.

Want to get in touch?
Drop me a line!

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.