Five ways the right panel can respond as the agent learns Content, Demographic, Budget and Timing. Step through to see each fill in.
Tell me about your content to begin.
Why: the empty state previews the real output, so the user sees what they are working toward. Chips double as shortcuts to start a dialog on that topic.
Why: reads as a conversation, not a form. The blank still waiting gets a teal outline, so the user knows what the agent needs next. Needs very little UI.
Why: leans on the Flight Plan name. The route is the progress indicator, so there is no ring or bar to explain. The plane lands on each stop as it is learned.
Why: stacks the answers over the numbers they unlock, so nothing competes for width. Ties the checklist to the header fields (Timing, Estimated Households) and the footer (Impressions) so the whole screen reacts. Each answer visibly earns a number.
Why: ties to the Flight Plan name with a familiar object. Empty fields read as a form waiting to be filled, the next needed field is underlined in teal, and the barcode prints as answers land.