Community sits on the path, not beside it
A peer thread gets someone to the answer without a ticket, because community sits on the path instead of beside it.
The useful community is not an engagement side-channel. It is a routing layer.
Someone asks in the customer’s own words. A peer answers with the step that actually works. The thread is visible to the next person with the same intent, and to the team that should turn it into knowledge.
When community is on the path, the ticket is the exception. When it sits beside the product, every question becomes a queue.