Not a playbook CMS and not “describe intent → AI publishes an offer.” Events are necessary but not sufficient; golden paths define what gets evaluated, then the coach guides users in-product.
No. Glance Intelligent Detect still needs you to say which workflows matter, then it labels sessions and (with triggers) decides when to speak.
| If you only… | You get… | You still need… |
|---|---|---|
| Stream events | Live activity pipe | Workflow ontology (golden paths) |
| Define golden paths | Sessions scored vs ideal sequence | Triggers + delivery (coach / chat / tour) |
| Connect a support agent | Context-aware reactive + proactive chat | FSM / cooldown so it doesn’t spam |
Admin is not primarily “write CSS steps” or “prompt an offer into existence.” Deep trigger authoring can live in SDK / eng config.
Click through the mock in this order.
Open the activity pipe before anything “smart” happens.
Tell the system which journeys matter. Glance Intelligent Detect labels sessions against them.
Sessions show workflow + completion %. Off-path / stalled can fire proactive help.
Those may exist later as advanced / eng escape hatches — not the default happy path.