3
\$\begingroup\$

We somewhat regularly get questions posted that we really can't answer and are best directed at the technical support or customer service desk for a commercial entity. For example, we might see questions similar to these:

  • Why did [website/store] reject my game? (best directed at the customer service team for that website/store)
  • Why do I get an HTTP error when I try to upload a build to [website/store]? (best directed at the technical support team for that website/store)
  • Why can't I log in to my [website] account? (best directed at the technical support or customer service team for that website)
  • Why does [professional software/development tool] crash? (best directed at the technical support team for that software/tool)

and so on.

Occasionally these types of questions will get an answer, but often those answers don't solve the question or aren't helpful for future readers. Questions about "why did my app get rejected" can be closed as "opinion-based", but otherwise there isn't a good close category for these questions and we have to select "other". Is this worth adding a close category for?

\$\endgroup\$
1
  • 1
    \$\begingroup\$ Sorry to keep you waiting. Unfortunately, we get only 3 custom close reasons per site, so we can't simply add a new one in addition to the three we have (currently: 1. General programming should be asked on StackOverflow, 2. "how to get started"/"what to learn next"/"what technology to use" are too discussion-oriented, and 3. Questions about debugging a problem must include a minimal, complete, verifiable example). We could try using answers here to propose a new set of 3 reasons, folding in this new one somewhere, and use votes to choose between the proposals. \$\endgroup\$ Commented Jul 27 at 20:52

1 Answer 1

1
\$\begingroup\$

I previously asked if we could get a close reason for "where can I get free resource X"? I was informed that sites generally only get three custom close reasons & we're currently using all three. Some sites have been granted a fourth custom reason but it was doubtful that we'd qualify.

I saw that you recently used a custom close reason & that's generally what I do in these situations.

For others reading this that aren't familiar with the process, from the close menu, first select A community-specific reason:

screenshot of close menu

That will bring up a new menu with an option for Other - add a comment:

screenshot of sub menu

Where you should add a comment explaining why the question should be closed. This comment will get posted publicly to the question, so it's an oppurtunity to explain to the poster why their question isn't on-topic for GDSE and if possible, how they might be able to bring it back on topic.

I like my comments on custom closures to include links to the help &/or Meta to provide context &/or explain why the question isn't a good fit for the Stack Exchange model.

\$\endgroup\$

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.