Prior to Inquiring, Let’s Explore How to Craft Questions for Clear and Prompt Responses
Considering posting a question on the Kore.ai Community Forum?
Excellent! This forum is an integral part of our community, primarily designed to foster collaboration among Kore.ai Developers, enabling us to assist each other and exchange knowledge and expertise. Every question represents a chance for collective learning!
However, prior to asking your question, let’s pause for a moment to explore how you can frame it in a way that encourages concise and prompt responses.
Have you completed the training?
To formulate a meaningful question, you should have some prior knowledge about the subject.
It’s crucial to emphasize a significant point here.
Many enthusiastic individuals aspire to create impressive Kore.ai Chatbots.
but in their excitement, they may overlook the fact that learning how to wield a tool is a prerequisite to its effective use.
Indeed, before posting any inquiries in the forum, it’s essential to ask yourself whether you’ve already completed the Kore.ai Product training.
If not, it’s time to enroll and get started!
It’s because undergoing proper training is the quickest route to begin creating impressive chatbots with Kore.ai’s product suite.
How about the documentation?
Kore.ai offers a wealth of documentation that you can delve into whenever you require assistance, want to acquire new knowledge, or simply for your enjoyment – whatever suits your needs.
Don’t overlook this crucial link:https://developer.kore.ai/
The community is likely to be more inclined to offer assistance when the question demonstrates that the asker is actively making an effort to resolve the issue beyond just asking the question itself.
Is this question being asked for the first time?
While it is a possibility, the likelihood of receiving a resounding “NO” as the answer to this meta-question is quite high. This is especially true unless your inquiry pertains to something that diverges from your own logical understanding.
So, what is the recommended course of action?
Utilize the search functionality extensively. Keep refining your search by trying various combinations of keywords, and if you prefer using external search engines like Google or Bing, remember to include the keyword “Kore.ai” in your queries.
Mastering the art of effective searching is a valuable skill for any developer.
When your search efforts yield no results, that’s the appropriate time to pose your question on the forum.
What the question entails is…
Each question may require a different approach, depending on what is being asked. So, in order to make it easy to understand what would be (possibly) the best approach for a question, let’s group typical questions into three different categories:
a) “How to…?”. In the Kore.ai Community forum, these questions appear very often.
They usually come in two types: “How to implement something” (logic) and “How to use something”. Usually, both are not really difficult to answer.
However, you need to show that you are trying (and where you searched for documentation, etc). For this type of question, this is very important.
b) “It does not work…”. These are questions one asks when there is a code, but it is not working as expected.
When facing a problem with your code that you are unable to solve, you need to provide all the most important information in the right way, or it will take a lot of time from the community to just figure it out what’s happening.
c)“Could someone explain…?”. Questions like this are usually about the way the platform itself works. Theory, you could say. Usually, they are posted when one needs to get to know the “innards” of the platform because it can have an impact on the application behaviour, and this information was not found anywhere.
These questions are hard to answer because not everybody knows how things work under the hood.
It may take longer to get an answer for these questions.
What is the proper way to pose a question?
By adhering to the following guidelines when formulating your question, you’re on the right track to receive a valuable response:
- Avoid extremes:
Providing too little information or an excessive amount can hinder understanding.
- Specify the environment:
Indicate whether the issue pertains to a Prod, Dev Environments, channel Details, personal or enterprise settings, cloud or on-premise servers, and include the Product versions.
- Offer context:
Briefly describe your objective. Providing an overview of what you’re trying to achieve enables the community to suggest alternative approaches.
- Detail your efforts:
Summarize what you’ve already attempted, including the anticipated and actual outcomes.
- Share error messages and debugging data:
If you’re encountering an error or issue, provide relevant error messages and debugging information. It’s advisable to debug before posting the question, as you might be asked to do so.
- Reproduce the problem:
If you’re dealing with a unusual behaviour, create a minimal working example application that replicates the problem. This not only aids in clarifying the issue but also enhances the chances of finding a solution.
- Visual aids:
Images can be helpful; feel free to include them, but ensure they are accompanied by context to aid interpretation.