Nudge pre-v0.2 Readiness Review Guide

What Changed For This Test

• The hotel website field is available again on the first screen.
• The three visible steps are now Diagnose, Build, and Review.
• The opening question asks for the business problem while still clarifying the behavior that should change.
• The first diagnostic question now asks what the hotel has already tried and what worked or did not work.
• Guest segment and tour-operator split questions come later, only when they help diagnose the problem.
• The final report now includes an assumed reason why earlier attempts underperformed.
• The report explains how to read the output, why touchpoints matter, and how to save it as a PDF.

How To Test

• Add a hotel website link if you have one, then describe a real hospitality behavior problem.
• Answer naturally. Good tests include what was tried before, what happened, and where the behavior occurs.
• Check whether the conversation feels responsive before it asks for segments or channel split.
• Review whether the report connects recommendations to beSMART in a useful, non-salesy way.

What To Watch

• Does Nudge ask enough before diagnosing?
• Does it use the website context without pretending it knows exact numbers?
• Does it explain why previous attempts likely failed?
• Are recommendations feasible for hotel teams?
• Does anything sound too generic, too confident, or disconnected from BehaviorSMART?

What This Is Not Yet

• Not production-grade.
• Not GDPR-complete.
• Not autonomous client advice.
• Not automatic learning from raw conversations.
• Not a promise that every generated idea is already BehaviorSMART-approved.

v0.2 should only be used once Vlad and Milena complete their review tests and the evidence is captured. Technical details are in the Tech README.