User Flow Mickael Rutembya · Flow Atlas

Office Hours Detail

Visitor inspects a single Office Hours session: date, duration, capacity, agenda slots, confidentiality rule, and registration form (waitlist or payable tier).

User intent

What the visitor is trying to do

« I want to understand this specific session, check if I can join, and register or buy a seat. »

Entry points

Element	Destination
Session card From Office Hours listing	`/ressources/office-hours/<slug>/`
Registration form Submit case	POST to same URL
Access link Related offer tier	`/ressources/produits/<slug>/`
Back link "Comprendre le format complet"	`/ressources/office-hours/`

Flow

Adjacent routes — click a node to open it.userflow

flowchart LR Start(["Visitor from listing"]) --> SessionDetail["/ressources/office-hours//"] SessionDetail --> OfficeHoursPage["/ressources/office-hours/"] SessionDetail --> OfferTier["/ressources/produits//"] SessionDetail --> RegForm["POST registration (waitlist / session)"] RegForm --> Confirmation["Confirmation message (same page)"] OfferTier --> ProductCheckout["/paiement/produit//"] ProductCheckout --> PaymentReturn["/paiement//retour/"] PaymentReturn --> EntitlementDetail["/acces//"] OfficeHoursPage --> SessionDetail SessionDetail --> End(["Registered / seat purchased"]) click SessionDetail "https://mickael-umt.com/ressources/office-hours/session-slug/" "Open Session" click OfficeHoursPage "https://mickael-umt.com/ressources/office-hours/" "Open OH" click ProductCheckout "https://mickael-umt.com/paiement/produit/product-slug/" "Open Checkout" click PaymentReturn "https://mickael-umt.com/paiement/PAY-001/retour/" "Open Return" click End "https://mickael-umt.com/ressources/office-hours/session-slug/" "Open Session"

Screen inventory

ID	Screen	User task
P0	Session detail	Read session info, register or buy
P1	Office Hours listing	Browse all sessions and tiers
P2	Product detail	Choose access tier and pay
P3	Checkout	Pay via Stripe
P4	Payment return	Confirm payment, see entitlements

Flow scenario

Scenario OH2

Visitor registers for a session

Trigger

Visitor finds session from Office Hours calendar
Topic matches their decision

Experience

Session detail loads with date, duration, capacity, confidentiality note.
Visitor sees registration form (case description, availability).
Fills form and submits → confirmation message appears.
Alternatively, visitor clicks access tier link → product detail → checkout → Stripe.
Payment settled → return page with entitlement link.

Trust and safety rules

Session pages never record participant identity in the sitemap; only aggregate counts are shown.
Registration form records a request, not a payment, for free tiers.
Payable tiers use the same checkout component as products.
Confidentiality rule: sessions are never recorded.

Interaction rules

Capacity bar shows participant_count / max_participants.
If session is full, registration form is replaced by "Cette cohorte est complète".
Access links point to related offers with headline prices.

Result states

State	What the visitor sees	What happens next
Registering	Session info + registration form	Form submitted, confirmation shown
Paying	Product detail + checkout form	Stripe redirect, return page
Confirmed	Confirmation with email and details	Visitor attends session