Both records belong to one enrollment, but they answer different questions. Open Coaching → Member monitoring and select the enrollment before recording either one. An organization owner/admin, an organization-scoped program director, or a coach assigned to that enrollment or its program can document this follow-up. A reviewer assignment alone does not grant that access.
| Record | Use it when… | What remains visible |
|---|
| Coaching session | A 1:1 conversation already happened | What was discussed, decided and committed to on the enrollment timeline |
| Intervention | The team plans a concrete act to unblock the member | The responsible person, due date, and closure with the outcome of the action |
| Live session | A workshop is scheduled for a cohort | The collective agenda and attendance, managed separately under Management → Lives |
Nina speaks with Maya after seeing her overdue follow-up in the Coach queue. She records the conversation on Maya's Agentic AI Developer enrollment: the demo's failure case is unclear, and Maya commits to showing a reproducible example. If Nina also needs to arrange a targeted check-in, she plans an intervention with an eligible owner and due date, then closes it with what happened. The intervention keeps its original plan and its outcome; it is a tracked action, not the member journey's Next action object.
A request for changes on Maya's demo remains a submission review decision. Recording a coaching session does not submit a revision, decide a review or book a future meeting. A live for October Builders is collective delivery, not a substitute for this enrollment history.
The Coaching sessions API lists and reads sessions and records a conversation that already happened. The Interventions API lists, plans and closes interventions. Both enforce the enrollment's access boundary; consult each endpoint for its fields and idempotency rules. Neither API is a meeting-booking flow.
