Describe the screens you want in plain language and Wavy AI builds or rewrites them inside the quiz / paywall editor. Review, preview, then publish.
Building a funnel screen by screen is the slow part of launching a new offer. Wavy AI is the assistant built into the quiz and paywall editor: you describe what you want in plain language, and it creates new screens or rewrites the ones you already have — without leaving the editor.
It works in both directions:
- Generate — start from a short brief and get a set of screens you can keep editing by hand.
- Modify — point Wavy AI at what you already have and ask for a rewrite, a restructure, or a different tone.
Wavy AI is in Beta. The button is labeled Wavy AI with a Beta badge in the editor. Results are a strong first draft, not a finished funnel — always review and preview before you publish.
Where to find it
- Open your project in the cabinet.
- Go to Quizzes & Pages and open the quiz or paywall you want to work on. Wavy AI acts on the funnel you have open, so open the right one first.
- In the editor, click Wavy AI (marked Beta).
- Describe what you need, then send the request.
Don't see the button? Wavy AI is a Beta feature and may not be switched on for every project yet. Contact web2wave support via your chat or
[email protected]and ask to have it enabled.
Start on a copy, not on a live funnel
While you're learning what Wavy AI does well, work on something you don't mind breaking:
- New funnel — create an empty quiz or paywall and let Wavy AI fill it in.
- Existing funnel — make a copy of it first and experiment on the copy. If the result is good, you can move the winning screens into the original or point your traffic at the copy.
This matters most for a funnel that is already taking payments or running in an experiment — an unreviewed rewrite can quietly change wording, screen order, or a call to action that your ads and analytics depend on.
What to ask for
Wavy AI is aimed at funnel content — the screens, the copy, and the look. Typical requests:
| You want | Ask for something like |
|---|---|
| A quiz from scratch | "An onboarding quiz for a sleep-tracking app: goal, current sleep quality, bedtime routine, stress level, then email capture." |
| More screens in an existing quiz | "Add two screens after the goal question: one about past attempts, one about how much time they can commit per day." |
| A rewrite of the copy | "Rewrite every question in a warmer, more personal tone. Keep the answer options as they are." |
| A different audience | "Rework this quiz for men 45+ who want to lower blood pressure, not for weight loss." |
| Paywall structure | "Build a paywall with a value block, before/after visualization, testimonials, an FAQ, and a money-back guarantee under the pay button." |
| Paywall copy | "Make the headline and the plan labels shorter and clearer, and add a one-line reassurance under the subscribe button." |
| A visual pass | "Use a calmer palette based on deep green, softer corners, and larger headlines." |
Write the brief like you'd brief a copywriter
The quality of the output follows the quality of the request. Useful things to include:
- Who it's for — "women 30–45 who want to lose weight without strict diets" beats "our users".
- What the funnel is selling — the product, the plan, the promise.
- How many screens and roughly what each one covers.
- Tone — warm and coaching, clinical and factual, playful.
- What to leave alone — say so explicitly if prices, an email capture screen, or a legal block must stay untouched.
Good brief:
"7-screen quiz for a beginner running plan. Audience: complete beginners 25–40 who have tried and quit before. Ask about goal, current activity, injuries, available time, and motivation, then capture email. Encouraging tone, no shaming. Don't change the last screen."
Weak brief:
"Make a fitness quiz."
Ask for one thing at a time
A request that bundles "add three screens, rewrite everything, change the colors, and shorten the paywall" is hard to review, because you can no longer tell which change caused which difference. Work in small passes and check the result after each one — it's faster overall than untangling one big rewrite.
Review the result before it goes live
Wavy AI writes into the quiz or paywall you have open, the same way a manual edit does. Two things follow from that:
- Nothing reaches your visitors until you publish.
- Everything Wavy AI produces is ordinary editor content, so you can adjust it by hand afterwards — no different from a screen you built yourself.
Run through this before publishing:
- Read the screens in order. Check that the flow still makes sense and that nothing important was dropped or duplicated.
- Check the things money depends on — prices and plans on the paywall, the pay button, the email capture screen, and any legal or guarantee wording. Confirm your plans and prices are still the ones you meant to sell (see Plans and prices).
- Check screen logic. If your funnel branches on answers, confirm the conditional logic still points at the right screens after screens were added, removed, or reordered.
- Preview on mobile. Quizzes and paywalls are mobile-first, and generated copy is often longer than the copy it replaced — watch for text that overflows or pushes the button below the fold. See Quiz & paywall design requirements for the sizes to check against.
- Publish when you're happy with it.
Rolling back. web2wave keeps earlier versions of every quiz and paywall, so an AI edit isn't a one-way door — you can go back to a previous version of the funnel. If you can't find the version you need, contact support before you keep editing over it.
Beta caveats and limits
- It's a draft, not a launch. Generated copy has not been fact-checked, and it is not a legal, medical, or advertising-compliance review. Claims about results, health, or refunds are your responsibility.
- The feature is still changing. Because Wavy AI is in Beta, wording, buttons, and the shape of the results may change between releases.
- Results vary between runs. The same brief can produce different output twice. If a result was close, refine it with a follow-up request rather than starting over.
- Review every rewrite of a live funnel. Wavy AI doesn't know which sentence your ad account was approved against or which screen your experiment is measuring.
- Translations are a separate step. Generate in one language first, get it right, then create your localized versions — see Auto-redirect: language and country.
- Analytics need traffic. A regenerated funnel starts a fresh page of data. Give it enough visitors before you compare it with the old version, and prefer an A/B experiment over a gut call.
Wavy AI or the MCP server?
web2wave has two ways to work on funnels with AI. They do similar things from different places:
| Compare | Wavy AI | MCP server |
|---|---|---|
| Where you work | Inside the web2wave editor | In your own AI client (Cursor, Claude, Codex, Windsurf) |
| Setup | None — it's in the editor | Connect the server with your project API key |
| Best for | Quick generation and edits while you're already building a screen | Bulk work, cloning a funnel from a URL, rebuilding from a Figma file, funnel and experiment read-outs |
Use whichever fits the moment — both act on the same quizzes and paywalls in your project.
Related pages
- Quiz & paywall design requirements — sizes, blocks, and structure your generated screens should respect.
- Plans and prices — how prices, trials, and intro offers work on a paywall.
- Conditional logic for fields and screens — branching after you add or reorder screens.
- Experiments (A/B testing) — compare a generated funnel against your current one before you commit.
- MCP server — drive the same quizzes and paywalls from your own AI client.