Ask for help in team chat

Questions in busy team channels get answered when a helper can understand them in one read and answer without a round of follow-ups. They go unanswered when they ask to ask ("anyone know about the VPN?"), describe an attempted fix instead of the goal (the "XY problem": asking how to do X when the real need is Y), leave out the error message or what was tried, or hide the urgency. A good question states the goal, what happened versus what was expected, what was tried, the specific question, and how urgent it is, in a short first message, with longer details in the thread. Posting the answer back afterwards turns the thread into documentation for the next person.

Write a team chat question.Only if [CHANNEL_AUDIENCE] is given: Channel and readers: [CHANNEL_AUDIENCE]. Urgency: today.

Only if [WHAT_WAS_TRIED] is given:

1. If you cannot tell what the person is trying to achieve, ask one question about the goal and stop.
2. Check for the XY problem: if the problem describes a workaround or a means, state the underlying goal first so helpers can suggest a better route.
3. Remove any secrets or sensitive data in the problem (passwords, API keys, tokens, customer personal data, financial account numbers) from the message, replace them with placeholders, and say so under Tips.
4. Main message, at most about five short lines:

• The goal and the problem in one sentence.
• Expected versus what actually happens, with the exact error text in a code span if there is one.
• The specific question.
• Urgency stated honestly: for "blocking", say what is blocked and since when; for "low", say it can wait.
• Where to reply ("in thread, please").

1. Thread details: what was tried, environment or context (device, system, account, document link placeholders), and screenshots to attach, as a short list. Omit if there is nothing beyond the main message.
2. Tips: whether to tag a specific owner or team (only if the channel audience suggests one, and never tag a whole channel for a non-urgent question), and one line on searching the channel history first if that was not tried.
3. After it is answered: a one-line follow-up template that posts the solution and thanks the helper.

• Use only the facts given; never invent error messages, system names or steps tried. Use [need: …] where an error message or link would help.
• No "anyone around?", "quick question" or apology for asking.
• Do not inflate urgency; "blocking" only when the input says work cannot continue.
• Keep the tone friendly and matter-of-fact; suitable for a new joiner who does not know people yet.

Main message

The message, ready to paste.

Thread details

The thread reply, or "Not needed".

Tips

Two or three bullets.

After it is answered

One line.

Weak: "Hey, does anyone know about the VPN?" Strong: "I can't reach the staging dashboard from home: the VPN connects, but the page times out (ERR_CONNECTION_TIMED_OUT). Is there an extra step for staging access for new starters? Blocking my onboarding tasks since this morning. Details in thread 🧵"