[📝 Docs]: Discussion on Feedback Form Usage and Increasing Conversion

[DarhkVoyd]

What Docs changes are you proposing?

Description: We have identified a recurring pattern where users are submitting questions through the feedback form on the website. But, users are not following up by raising an issue or joining the Slack server for further discussion. We do not take email or name, as this isn't a support form. Any ideas on how we can increase conversion on this?

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[DarhkVoyd]

Suggestions:

• Make it clear at the beginning of the form that it is intended for feedback, not for support or questions.
• Include a message in the form confirmation reiterating that the feedback form is for feedback only. For questions, direct users to join the Slack server for discussion.
• Modify the current form response to clearly inform users that their feedback will be published in the Slack channel #website for further discussion.

[benjagm]

What I think we can easily do is clarify muy better the feedback alternatives we provide:

• To provide feedback and engage in discussion with us the should use the create issue button.
• To provide anonymous feedback they should use the submit feedback button.

[gregsdennis]

I think instead of "submit feedback" we should use something more explicit, like "Yeah I'm not looking for a response."

Seriously though, if people are asking a question, then the assumption is they want an answer, not for the page to just update. Many of the questions we've received don't have answers that necessarily fit on the page where they submitted it.

Personally, it's frustrating when a user has a question and I have an answer but I can't provide it because they just clicked "submit feedback" without actually looking at their options.

---

What I'd like to see is a form showing fields for all the contact details that we'd need to reply and a pre-checked checkbox with "I'd like a reply." Then the contact fields are required as long as the checkbox is checked.

Unchecking is opting out, and they don't need to provide contact details.

The opt-out model is the approach I typically see websites use, but the checkbox is usually something like "I want to receive the newsletter" or "I want to receive offers".

[benjagm]

What I'd like to see is a form showing fields for all the contact details

I am totally agains converting this feedback component into a contact form. Again, I think your as speaking amore about your feelings because of not being able to reply, rather than the actually feedback we get.

You said we get mostly questions, but that is not accurate:

• So far we received 98 replies. 74 positive and 24 negative.
• From the 24 negative, only 6 are questions and most seems rhetorical questions to express an opinion.

My point is, this is all about the user, not us and how do we feel with the comments. The best path forward is to turn all this feedback into actionable improvements and improve our docs the best way we can and later communicate it.

Additionally we'll make sure we explain better the options for transparent feedback.

This article express my approach here: https://customerthink.com/what-are-the-benefits-of-anonymous-customer-feedback/

[gregsdennis]

turn all this feedback into actionable improvements

This can't be done with the ones I'm talking about. The one that sparked this entire debate was a question about how to use a specific implementation. We can't include that in our docs or tools list.

[benjagm]

This can't be done with the ones I'm talking about. The one that sparked this entire debate was a question about how to use a specific implementation. We can't include that in our docs or tools list.

I strongly disagree.

If this user started its JSON Schema journey in the getting started page which focus is to teach you how to create a schema and validate it, but they were looking for a schema generation tutorial and ended up doing this question, we can improve this page to better explain that there are other uses cases and where to find answers for those questions and making it clear that we are implementation agnostic.... so we don promote any tool over others.

[benjagm]

I think everything is a matter of balance between individual support and broader feedback. You seems to be focused on individual support which is great, while I am focused on capturing as much feedback as possible to turn it into improvements and help the broader community.

As I said it is a matter of balance and I think we can do it without having to create a contact form. We'd like the discussion to happen in the community and not in an email thread.

I have just made some changes in the component to prioritize the feedback section so the first question available is "Do you have a question?". The next option available will be Feedback ... se we are explicitly presenting the user to option to ask a question before anything else.

My proposal:

Current version:

With this proposal we are prioritizing the option to get support and make a question to the Community. If this works we'll reduce the number of questions received in the feedback form.

[Relequestual]

If we might fix this problem simply be re-ordering the footer, that feels like a simple win.

Although, maybe we could change "often confusing" to "sometimes confusing"? 😅

[gregsdennis]

We'd like the discussion to happen in the community and not in an email thread.

I think this may be the disconnect. DV's solution in slack was to create an issue or discussion in GitHub and respond there. No one is suggesting we respond via email. At most, they get an email with a link to the issue/discussion that was created so they know where to find a reply.

I'm also not saying we should be collecting people's data. We absolutely should not be doing that.

I still think we need to prioritize providing support.

[gregsdennis]

Let's start with your suggestion @benjagm. See if that improves things.

[github-actions[bot]]

Hello! :wave:

This issue has been automatically marked as stale due to inactivity :sleeping:

It will be closed in 180 days if no further activity occurs. To keep it active, please add a comment with more details.

There can be many reasons why a specific issue has no activity. The most probable cause is a lack of time, not a lack of interest.

Let us figure out together how to push this issue forward. Connect with us through our slack channel : https://json-schema.org/slack

Thank you for your patience :heart:

[gregsdennis]

This is still very much needed.

[benjagm]

This is still very much needed.

Agreed.

[harshsbhat]

@benjagm maybe #841 that I created tries to fix something similar

[jagpreetrahi]

Hey @benjagm , what if we collect minimal optional data e.g. feedback type & topic , to tailor the responses and suggest relevant resources. or even we can suggest FAQs, articles, or GitHub issues dynamically based on the user’s input.

I think it would be user-centric experience , if we think about it.

[idanidan29]

I agree with @benjagm’s proposal it makes a lot of sense and it would be easy to test its efficiency. for support i really like @jagpreetrahi idea, I think linking to an easy to navigate FAQ section or dynamically suggesting relevant FAQs based on user input would really improve the user experience and help users find answers faster.

[Kashika23]

@benjagm can i work on it further.