Connected transaction and communication drafts before implementation
Free route
Headline: „Nézzük meg a saját beszédedet.” Instruction: select a spontaneous short video, preview it, give a demo contact name, distinguish service updates from optional useful newsletters. Deliberate button „Beküldöm a bemutatóban”. Receipt says no real upload occurred and explains a personal response would follow. The clearly fictional feedback names one observation and one useful next focus, then offers the 14-day programme voluntarily.
Wireframe: task summary → recording guidance → chooser/player/replace/remove → service purpose → optional marketing consent → submit → receipt/wait → sample response → optional programme.
Criticism: an automatically successful file picker could imply a real upload and evaluation. Validate a playable video before submission, keep the prototype label at the outcome, and start the feedback follow-up after that state.
Paid route
Headline: „14 napos beszédkihívás”. Proposed one-time 24 900 Ft. Includes source-based practice tasks, daily video and daily personal feedback, then online consultation. Source practice load is about 20 minutes, integration days about 30 minutes, not one minute total. Main button „Sikeres fizetés bemutatása”. No real card details or financial transaction. Branches: success→confirmation→demo entry→overview; cancel→matching A/B offer; pending/error→retry; sold-out→honest local waitlist demonstration.
Wireframe: chosen variant/offer → proposal/inclusions → demo payment fixture → result → access. Branch choice visible and labelled as prototype tooling.
Criticism: disconnected payment screenshots cannot show continuity. Preserve chosen variant across query parameters and saved local state. Success must open access and show simulation, cancellation must recover the originating offer.
Email and notification previews
Preserve the substantive 41 existing paired email topics, source bodies and A/B distinction, rewriting material inconsistencies. Each full preview includes trigger, recipient stage, subject, preheader, body, real demo CTA and a second full alternative. Service receipts/daily delivery/feedback/access/consultation remain separate from optional newsletters/promotion. No preview sends anything. Paid participants are excluded from sales reminders. During a cohort promotion, those promotional emails replace the weekly newsletter.
Wireframe: recipient/trigger → subject/preheader → full A/B message → CTA destination → eligibility and suppression. A selector gives in-app/email/Messenger notification preview where relevant, with no integration.
Criticism: a list of subjects and feature snippets leaves the reader guessing why a message arrived. Show each whole message and its timing in the journey. A follow-up must not imply Rita saw a video that was never submitted. No arbitrary placeholder CTA or automatic client message.