Skip to main content

Notifications

Announcements

No record found.

Tuesday Tip: How to Post Questions that Quickly get Answers

Bret Fraser v- Profile Picture Bret Fraser v- Community Manager

Today, in our Tuesday Tips series, we're highlighting best practices for quickly getting the answers you need.

To save time and receive precise responses from your peers:

  1. Log in to your community profile.
  2. Search in the community global search: Find existing answers by entering your question or keywords in the community global search box. (Guide to Community Global Search).
  3. Utilize filters such as category, status, and sorting options like date or recent replies.


     
  4. Ask a new question: If you don't find an answer, post your question. Some may take longer to answer due to complexity.


     
  5. Autosuggest: When typing a new question, check suggested threads for similar relevant information. Icons indicate suggested and verified answers.
  6. Format your question to help receive the best possible answers:
    • Subject line: Keep it concise (5-10 words) but specific
    • Description: Clearly outline your problem with details (versions, error messages, scenarios) and supporting images
    • Formatting: Use bold, italics, links, and bullet points for clarity
  7. Things to avoid:
    • No ads, product/service promotion, or job postings
    • Start a new thread for each question
    • Skip unnecessary phrases like "Please Help" or "Urgent"
    • Don't share emails publicly - connect privately
    • Check that any screenshots don't include PII (personally identifiable information), including domain name URLs, etc.
    • Avoid ALL CAPS; it's considered impolite
    • Report trolling or spam - use the report-abuse option on threads

Important: when your question is answered, remember to mark the answer(s) as verified to help others in the future.

More information about suggested and verified answers.

 

We appreciate your engagement in the community, and all feedback is welcome!

 

 

Comments

*This post is locked for comments