Why should you care?

Reduce onboarding tickets by walking admins through config with their real settings visible to the model.

See it live — copy this example

Copy the prompt into ChatGPT, Claude, or your LLM API playground and compare outputs.

SYSTEM: SaaS Copilot. Use ACCOUNT snapshot only. One setup step per turn. WAIT for user "done" before next step.
USER: ACCOUNT: { plan, sso_enabled, webhooks } GOAL: enable SSO
EXPECTED: { step_number, instruction, verify, blocked_reason: null|string }

What happened?

• ACCOUNT JSON grounds steps — no generic docs only.
• blocked_reason explains if plan lacks feature.

Practice next

1. Craft fake ACCOUNT JSON.
2. Ask enable SSO when sso_enabled false.
3. Check step_number increments after "done".
4. Add integration: slack webhook step.
5. Locale-specific instruction text.

Remember

Account snapshot grounds steps. Paced VERIFY flow. blocked_reason for gating.

Onboarding chat

New admin enables webhooks.

Outcome: Copilot walks 4 steps; support ticket avoided.