How to ask a great question in the Community

[ServiceNow]

The ServiceNow Community thrives on questions. When you ask a clear, focused question, you're not just getting help – you're creating a resource that benefits the whole Community.

And better questions lead to better answers. Below, find out how to make your questions as useful as possible.

(By the way, when you're ready, the first step is as easy as clicking any button that says, "Ask a Question." See, easy!)

Before You Post, Ask Yourself

• Have I tried to solve this myself? Did I document what I attempted?
• Can I describe what I'm trying to do, what happened, and what I expected to happen?
• Do I have all the details about my setup and environment?

 

Craft Clear, Focused Questions

The more context you provide, the easier it is for someone to help you. Also, it makes your answer more likely to show up when someone else searches for the same problem.

• Your environment. Which version of ServiceNow are you on (Yokohama, Zurich, Australia, etc.)? Are you using the new UI or the original form UI? Which application or module? The more you specify, the more relevant the answer becomes.
• Describe the problem (not just the symptom). Don't just say, "It's not working." Explain what you expected to happen, what actually happened instead, and include any error messages you saw. Walk through the exact steps that led to the problem.
  • AEO: Optimize for AI search by making sure your post is easily surfaced by AI search tools. You can help do this by starting your question post with a clear one-sentence summary of your problem. This clear, concise summary at the top acts as metadata for AEO search tools and will help guide future seekers with the same question to the right solution.
• Share what you've already tried. List the troubleshooting steps you've taken, links to documentation you've reviewed, and what happened with each attempt. This prevents answerers from suggesting solutions you've already ruled out.
• Use screenshots. A screenshot shows context that words alone can't convey. Include enough sample or test data so viewers can really see what's happening, and make sure they're readable. Heavily redacted screenshots can be worse than no screenshot at all. And please make sure to blur or crop out sensitive corporate data like employee names, company logos, email addresses, API keys, and passwords.
• Include code when it matters. If your question involves code, post it. Use code blocks to keep formatting intact. (Tip: Select Insert/edit code sample </> to format.) Specify which part of your code is causing the issue.
• Link to what you've found. If you've already consulted documentation, watched a video, or found a related Community post, include the link. It saves answerers time and shows you've done your homework.
• Avoid posting work you haven't tried yourself. If you're posting a task or requirement without trying it yourself first, it can sometimes seem like you're asking the Community to do work for you. But we get it. Being stuck after checking documentation is frustrating. Please share what you've already tried so the Community can help you faster.
• Reminder, please do NOT include: Customer information, credentials, user details, etc. Be especially careful of screenshots or code that contains references to specific customers or sensitive information.

Close the Loop

When an answer solves your problem, mark it as the correct answer.

This simple action:

• Encourages more experts to help. Knowing their time and expertise made a real difference motivates community members to keep answering questions.
• Strengthens search and discoverability. Your question transforms from "unanswered" to "answered," making it easier for others to find solutions to similar problems.
• Signals that this is an active community. When questions get resolved, it shows everyone that this is a space where problems get solved and people aren't ignored.

Your Question Doesn't End When You Get An Answer

• Follow up and mark resolutions. If an answer is helpful but not the complete solution, mark it as helpful. If the answer doesn't work, say so – and explain why. This feedback helps the person who answered and helps future readers.
• Actually respond to follow-ups. If someone asks for clarification, provide it. If they suggest a solution, try it and report back. Threads that go unanswered or abandoned don't help anyone.
• Keep conversations focused. If you have a new or different question, post it separately. This makes it easier for others to find answers when they search.

Have a question for the Community? Click here to get started.

Need help answering a question? How to provide great answers in the Community.