Why We Killed the Campaign Wizard (And What Replaced It)

The first version of our campaign builder was a proper wizard. Four steps. Audience → Message → Channel → Schedule. Every SaaS tool ships one. We were proud of ours.

Then we watched customers try to use it.

What we saw in the recordings

Real footage from real sessions:

• A boutique owner opened the audience picker, scrolled through six filter options, closed the modal, and messaged support: "how do I send to only Cairo?"
• A real estate broker built a segment, wrote a message, then abandoned the wizard because he forgot which of his three WhatsApp numbers he wanted to send from.
• A restaurant owner made it all the way to "schedule" and then didn't know if 8 PM meant Cairo time, Riyadh time, or her local time. She scheduled at 5 PM by accident.

The wizard was clear. The customers were not confused about the wizard. They were confused about mapping their intent to the wizard's structure. The translation was the problem.

The first fix we tried (and it failed)

We tried making the wizard "smart." Autocomplete on the segment picker. Suggested messages. A time-zone helper. The abandonment rate did not change. We had polished the wrong object.

The second fix — throw the wizard out

We removed the wizard entirely and replaced it with a chat. Same AI that answers customer conversations, but pointed at the campaign task instead. You describe what you want to run in your own words. The AI translates.

Abandonment collapsed. Not by 20%, not by 40%. Nearly to zero. Because there is nothing to abandon in a chat — you just say what you want, and the AI meets you where you are.

What we learned

Three things:

1. The best interface for a rich task is the interface humans already use to describe rich tasks. That is a sentence.
2. Wizards optimize for control the software wants, not control the user needs. The user needs "did I send to the right people?". The wizard asks "which enum did you pick in step 2?"
3. Chat is not lazy design. It is a lot harder to build a chat that behaves reliably than to build another wizard. But the result is a tool that actually gets used.

What we did not throw out

Some things still deserve UI. The preview that shows before you send. The estimated cost. The reply queue. Anything you want to see, not configure, is still a proper visual surface.

Only the configuration went. It turns out configuration was the whole problem.

Try the chat

See the result: the chat-driven AI Campaign Manager. Or sign up free and text your first campaign into existence.