Publish demand
Ask for the plan you need.
Demand side
Describe the request others can answer.
Use this page when you need a ride, stay, table, or other help and want the scene to be discoverable. The publish action records the request under your signed-in account and opens the slots you set.
What gets created
One demand-side scene with open slots for people who can help. Follow-up coordination still happens through the normal scene room flow.
What stays out of scope
This does not add media, exact scheduling truth, payout setup, or production readiness. Priced scenes still use the existing confirmation and payment path.
Paste a group chat
Turn a group-chat plan into a scene
Paste the message where you agreed on a plan. It is read in your browser to prefill a draft — nothing is created until you check it and confirm.
Publish form
Staging publish. This creates one owner-scoped demand scene plus open slots so members can request participation. Supply means you are offering capacity; demand means you are requesting capacity. Choose whether joining is free, paid, or deposit-backed. Priced participation may require payment before confirmation; payout remains a separate owner-gated operation and is not executed by this form.
Start from a real scene template
Planned pool labels
CoachPool, LensPool, and DeskPool are UI label lanes only. This form still publishes through the current schema-safe pool values.
CoachPool
Coaching and guided sessions stay visible as label lanes while publishing writes schema-safe kinds.
LensPool
Photography and creative sessions stay visible as label lanes while publishing writes schema-safe kinds.
DeskPool
Desk, study, and work sessions stay visible as label lanes while publishing writes schema-safe kinds.