Pillar guide
Learn how to write a clear help request on TrySomebody so the right people can understand your situation and respond usefully.
A clear help request makes it easier for the right helper to understand your situation, judge whether they can help, and respond with something useful. On TrySomebody, seekers do not need to classify their request by service type. They only need to explain the real problem, the context, the desired next step, and what a useful outcome would look like.
Begin with what you want to move forward, not only what feels frustrating.
A good request tells people what result, decision, task, or next step you are trying to reach.
Instead of saying only that you are confused, explain what you need help deciding, doing, checking, finding, learning, or understanding.
Give enough context for someone to judge fit. Mention the category, city or location if relevant, timeline, current stage, and what you have already tried.
You do not need to share private or sensitive details at the start. Share only what is needed for a helper to understand the problem.
Clear context helps helpers decide how they can respond through their direct ability, network, or a better next step.
You do not need to choose Direct Help or Network Assist. Describe the need clearly; helpers decide how they can help.
Your job is to explain what needs to happen, where it needs to happen, why you are stuck, and what kind of result would help you move forward.
For example, write what you need, when you need it, where it matters, what you have already tried, and what useful next step would help.
Useful details often include location, deadline, budget range if relevant, expected outcome, preferred communication style, and any limits the helper should know.
For local help, mention the area clearly. For guidance, mention the decision you are trying to make. For paperwork or process help, mention your current stage and blocker.
The goal is not to write a long request. The goal is to make the next useful response obvious.
A helper can offer effort, guidance, practical support, referrals, introductions, observations, or context.
Requests that ask for realistic help usually attract better responses than requests that ask for shortcuts or guaranteed results.
Use this structure: I need help with [problem] in [location/context]. I am currently at [stage]. I have tried [what you tried]. A useful next step would be [specific outcome].
FAQ
A good help request explains the problem, context, location if relevant, current stage, desired next step, and what outcome would be useful. The request does not need a service-type label; helpers choose that when offering services.
No. A request should be clear, not necessarily long. Include enough detail for someone to judge whether they can help.
Avoid vague asks, sensitive personal details too early, unrealistic guarantees, bribery, influence requests, or shortcuts around legitimate processes.
You do not need to choose Direct Help or Network Assist. Describe the need clearly; helpers decide how they can help.
Explain the situation and blocker clearly. Helpers can decide whether their direct ability, network, local context, referral, or guidance fits your need.
TrySomebody is a platform where people help each other solve problems - directly or through people they know.
Learn the difference between Direct Help and Network Assist on TrySomebody, and when each type of practical help makes sense.
Review public requests to understand how people describe real situations and outcomes.
Compare public capabilities and see how helpers explain the kind of help they offer.
See helper profiles and the public work they are connected to.
