Help Us Help You: How to get a forum answer 3 times faster

This article is here to help you, while at the same time emphasising the importance of providing a standard set of information to each of your FOEX forum question.

One of the things that we’ve learned throughout all the years of doing customer support is that: we can’t help you find the right answer if we know just part of the problem. While helping others, one crucial thing that we’ve learned is that you need to be prepared if you require someone’s help.


What to do before asking a question?

Search and research before you consider writing any question. The FOEX Forum is several years old and there’s a good chance that someone else has already asked the question and received an answer.

If you haven’t found a suitable answer, make sure that you bookmark every similar question/answer you find. You may need them as a reference point for when you start writing your question.


What not to ask?

Do not ask (or expect) for someone else to do your job. Try solving the issue yourself, stumble and then reach out for help.


The question’s title

The title of your enquiry should summarize everything you want to know about that topic.


The question’s content

There are several pieces of information that would make it so much easier for our support staff to provide a timely solution. I’ll just list them below:

  • Your workspace number on – it may seem simplistic, but you’d be amazed just how many users forget to provide us with this piece of information. Also make sure that there is a test case we can actually check on that workspace.
  • The page number within the application – it’s much easier if we know where to look within your application, rather than exploring each page in order to find the problem you signaled.
  • Issue description – be specific about what type of error are you encountering. Also, pointing to the ‘What not to ask’ question above, describe how you have attempted to solve the issue. This helps us understand your current situation and where we can look further for a solution.
  • Expected behaviour – this part is quite simple. Let us know what you’re trying to achieve or how you’d like the application to behave. There might be a quick fix or we could highlight a more effective way to get the desired result.


To keep this short, we’re more than happy to answer any enquiries and help find the best way to solve your issue. If you want to ensure a timely and well documented response, please use this article as a guideline for when you want to ask a question on our support forum.

Categories FOEX
Add your comment

Your email address will not be published. Required fields are marked *