Lesson 3: “People are using the feed as operations” reset script

This is the most common cultural drift. It happens when:

• the VT360 entry feels harder than posting
• people don’t remember the rule
• they want fast social visibility
• they’re emotionally activated and seek immediate support

Your job is to correct it without shaming.

A) The pinned post reset (public, calm)

Title: Where to Post Requests (Important) Copy (paste): “Quick clarity: This Space is the companion hub for learning and support. All live requests, offers, and matching happen in VT360 so nothing gets lost and stewards can triage cleanly. If you have a request, please log it in VT360 using the template. If you accidentally posted it here, no worries—just move it over and we’ll match from there.”

B) The comment redirect (on a feed request)

Copy/paste: “Thanks for posting. To make sure this gets supported, please log it in VT360 using the request template. We keep operations out of the feed so requests don’t get lost and matches stay clean.” Add the VT360 link right after that sentence.

C) The private message redirect (when it keeps happening)

Copy/paste: “Appreciate you being here. One quick norm: we don’t run live requests in the feed. The feed is for learning and support. VT360 is where requests get triaged and matched. If you want, I’ll help you log your next request once so it feels easy.” This keeps the person dignified and fixes the behavior.

D) The “friction removal” move (real solution)

If people keep posting in the feed, it usually means VT360 is too hard to access. Fix it structurally:

• Put the VT360 “New Request” link in:
• Create a “Request Intake” shortcut page in Notion with one big button
• Make sure mobile access is smooth (many villagers are mobile-first)

E) The boundary escalation (if someone refuses norms)

If someone repeatedly ignores the rule after reminders:

• steward closes the feed post
• directs them to VT360 again
• if needed, restrict posting permissions or require onboarding completion (depends on your community policies)

No drama. Just clean containment.

Troubleshooting Readiness Check

You’re stable when:

• relations link cleanly and duplicates are under control
• automations have a simple test protocol and failsafe buttons
• the feed stays a companion hub, not the operations lane

If you want, I can now write the Section 7 quiz (Yes/No + link placeholders), plus a “Known Issues + Fixes” living page structure for the space so villages self-serve most problems.