Input labels and AI context

Every form input has an Input Label — the short name for the answer it collects. Two audiences read it: you (in your Answers tab and on lead records) and the AI (when it writes each lead's report). The AI sees each answer as label plus value, so "Biggest obstacle: time" produces a better report than "question4: time".

For anything the label can't say on its own, each input also has an AI Context field — a place to tell the AI what an answer really means. Leads never see it.

Write a good Input Label

  1. Open a form step and find its Input Label.
  2. Ask: if I saw this label next to an answer with no other context, would I know what was asked?
  3. Make it short and readable — "Weekly hours available", not "q2" and not a copy of the whole question.

When to add AI Context

Leave it blank when the label says it all — "Email" needs no explanation. Add it when the answer carries meaning the words don't:

  • "'Just exploring' means low urgency — keep recommendations light and don't push a purchase."
  • "This is their monthly ad budget in USD; under 500 means recommend organic strategies only."

Keep it to a sentence or two. You're briefing an assistant, not writing documentation.

Good to know

  • The biggest wins are on Choice steps where options encode strategy: the option says "Option B", the context says what choosing B implies.
  • If generated reports keep misreading an answer, that's the signal to sharpen the label or add context.

Related articles

Was this helpful?