The ServiceNow community is an amazing place for administrators and developers to ask questions relating to the various product disciplines and receive snappy informative replies from leading experts. You have access to thousands of people who are more than willing to help you on your journey, so take a second to read the below tips for writing a question that'll allow for that quick and snappy response we know and love!

Search

Before asking your question, have you searched the community, product docs and the developer site? There's a chance your exact question has either been asked or the answer is within the two other reference libraries. A quick search saves you typing your question and having to wait for a response.

Your Issue

Describe your issue in detail providing references and supporting material where possible. It's almost always better to provide more detail than less. Don't forget mentioning whether you're working inside a scoped application.

Your Goal

Describe your goal / requirement. Doing so allows us to get an idea of what you're wanting to achieve and possibly offer an alternative solution. Remember, the customer isn't always right and you can say no!

Your Attempts

What have you already done? Tell us. Otherwise we might provide an answer to which you've already tried adding delay to helping you with your issue.

Clear Title

Don't post your entire question in the title, as with a lot of fields in ServiceNow there's a max length so it'll likely be cut off resulting in someone having to ask you to repeat your question.

Separate Questions

If you have multiple questions, raise them separately rather than all in one question post. It can quickly become confusing if multiple conversation streams are occurring in a single post. This also applies to when your question is answered; don't go asking another in the same post! If you've come from a service desk background, you'll understand the annoyance.

Images Help

An image speaks a thousand words and provides context. Although providing information on a field or specific script is great, the platform has grown dramatically in the past few years and therefore that little bit of context from a screenshot goes a thousand miles.

Code Snippets

When posting code snippets, use the code sample inserter. This makes the code so much easier to read and means people who view your post aren't going to get eye fatigue from a block of unformatted text.

Don't Spam

Some questions are complicated and people might be working in the background testing a solution before proposing it. Allow some time for a user to reply before you go deleting and re-creating the question, or worse....spamming the same question across different forums.

Mark Helpful

If the solution proposed by a user works, or the advise helps; don't forget to mark it either helpful or correct. Not only does this provide the user with some lovely community points for their effort, it closes off your question and makes it easier in the future for people searching the community for an issue to come across your question which may contain the answer they're looking for.

I hope this helps! If you have any suggestions, do leave them down in the comments and I'll add them onto the list. After all, the idea of this is to ensure everyone receives the full benefit of the community.

Regards,

K