Core Questions: Give the AI Context That Carries Forward
A core question is a step question you've marked as core, so its answer is given to the AI in every step the member completes afterward. Mark them on the question itself; see all of them under Hub Settings → Core Questions.
A core question is an ordinary step question that you've marked as core. Its answer becomes permanent context: OBIE feeds it to the AI in every step the member completes afterward, whether or not those steps are required. Use core questions for the handful of facts that should shape everything — who the member is, what they're selling, what they're working toward — so they never have to repeat themselves and the AI never contradicts what it was already told.
Mark a question as core
Core questions are set on the question itself, not in hub settings.
1. Open the step that contains the question, then open its Questions.
2. Add or edit a question and select the Core Question checkbox. It sits next to Required Question — the two are independent.
3. Save the question.
That's it. From then on, every step the member completes after answering it receives that answer as context.
See every core question in your hub
Open your hub, select Hub Settings, then Core Questions. The page lists every core question in the hub, grouped by journey, then milestone, then step, each tagged Core and — where it applies — Required. Select any question to jump straight to that step's question editor.
This page is read-only on purpose: it's your map of what the AI already knows. If the list is empty, you'll see a prompt explaining where to mark questions instead.
How to choose them
Core and Required do different jobs. Required means the member can't move past the step without answering. Core means the answer travels forward. A question can be either, both, or neither. In practice you usually want your core questions to be required too, because a core question that gets skipped contributes nothing.
Keep the set small. Every core question is added to the AI's context on every later step, so ten of them crowd out the actual work of the step you're on. Aim for the three to six facts that genuinely change the AI's output, and let ordinary questions carry the rest.
Good candidates: the member's business or role, their audience, their offer, their goal, hard constraints they're working within. Poor candidates: anything that changes week to week, and anything only one later step needs — that step can just ask.
Check it
Use Preview as User, answer your core questions, then move to a later step and see whether the AI's response reflects those answers. If it doesn't, confirm the question is actually marked Core on the Core Questions page, and check that your step's own prompt isn't overriding the context with conflicting instructions.
Frequently asked questions
- Are core questions asked when a member first enters the hub?
- No. They're regular questions inside your steps; members answer them when they reach that step. What makes them core is that the answer carries forward.
- What's the difference between Core and Required?
- Required blocks progress until answered. Core makes the answer available to the AI in every later step. They're independent checkboxes, and pairing them is usually the right call.
- Can I edit core questions from the Core Questions page?
- No, that page is a read-only overview. Select a question and it takes you to the step's question editor, where you can change it.
- What happens if a member skips a core question?
- Nothing is passed forward for it. Mark core questions as required if the answer really matters.
- Do core questions work across journeys?
- Yes. The context applies to every step the member completes afterward anywhere in the hub, not just within the same journey.
Related help articles
What Base Prompts Do and How to Set Them
Base Prompts is where you tell the AI who your hub is for, what result it produces, and how it should sound. The Step Base Prompt is prepended to every step generation, and the fields below it are background context reused across steps, offer pages, and offer chat.
Read moreEdit Steps and Questions
Edit a step's name, prompt, questions, and visibility rules from the step editor. You can also use Enhance My Prompt to refine your prompt with AI assistance, optionally referencing your uploaded documents.
Read moreCustomize Your Hub
Hub Settings is where you control how your hub looks and behaves — name and URL, appearance, labels, base prompts, core questions, welcome emails, access, SEO, custom domain, and analytics. This is the map to all of it.
Read more