Hello, since the new update I can't find the settings where I can make the button for OK or Next disappear until someone writes me an answer in the field. Does this setting still exist at all? Because now I have 3 surveys in the classic version and 3 in the new version. In the first three there is no way to get to the next question without writing something in. But in the other 3 surveys there is, where can I change this? In the introduction video this option is shown but it doesn't appear for me where I can make this button disappear.
Best answer by Liz
Hi @KMU Media We donβt have a guaranteed way to have the βokβ button disappear either in the new builder or the old builder, but Iβd suggest giving this a try, especially if you want to be sure that the respondent answers the question.
Hi @KMU Media thanks for asking! This is a great question. We havenβt had a setting like this in either the classic or new builder, but if you want to hide questions until the previous have been answered, you can use the following logic jump setup to prevent questions from appearing (and thus hiding the buttons until they enter their response). Would that help?
Hello Liz Thank you for your reply, so when I click on the "question settings" in the classic version.Then I have the option to click on Required and my button disappears on the page. As soon as someone writes something in, the butto appears.
Hi @KMU Media We donβt have a guaranteed way to have the βokβ button disappear either in the new builder or the old builder, but Iβd suggest giving this a try, especially if you want to be sure that the respondent answers the question.
I do have a question for you : the βnextβ / βOkβ button just disappeared from all my typeforms, resulting in a very poor UX for the very specific use i have from typeform.
Do you know how if itβs possible to parameter typeform to have this βnextβ/βOkβ button again ?
Thanks, but making the question required is not quite what I was looking for as I have done that already.
What I want is that when a number is selected on this type of question that the person ALSO has to tap the OK button before jumping to the next question. This gives them a moment to change their minds.
Why even have an OK button if it doesnβt do anything?
If I am misreading or not fully understanding these posts, please let me know.
Hi @Craig Carr Our product team tested this last year and found that the questions that had the βokβ button and were required had higher rates of completion than those that had the question required but didnβt have the βokβ button.
Hi @Craig Carr Our product team tested this last year and found that the questions that had the βokβ button and were required had higher rates of completion than those that had the question required but didnβt have the βokβ button.
Hopefully that helps clarify!
It doesnβt really - the OK button is absolutely useless if the question moves on as soon as the user has made their selection. This is the case even for required questions, I just tested it, the question moves on instantaneously, as soon as the user has made their choice. Iβm with Craig here, I want my user to be able to select their answer - say in a multiple choice set up - have a moment to change their mind if needed, then click OK to move on. As it is currently, the OK button is, quite literally, pointless.
In editing mode, the OK button is not visible. But as soon as I publish my form, it appears, rather erratically. With multiple choice fields set to required it makes absolutely no sense and is even misleading.
This is definitely a serious misconception that is keeping me from buying a Pro plan or use typeform at all.
Hi @BensonH thanks for stopping by and sharing your experience. Iβll share this feedback with the product team to help provide a bit clearer of an explanation as to why the βokβ button is rather awkward.
Hello, One month ago BensonH (see below) posed the same PROBLEM with the OK button that users have been asking about for TWO YEARS.
I just signed on for the PLUS plan. If this problem has not been solved for two years even with the new version, itβs appearing to me that fixing problems for users is not a priority or even on Typeformβs corporate radar.
Do you see this problem with the OK button being fixed within the next month? I donβt want a workaround. I want the problem fixed. If this glitch is not going to be repaired within the next 30 days, I will find another platform that is focused on USER success not simply corporate success.
Thank you. PS I understand that youβre the messenger and have no control/power over corporate focus. Iβm hoping they support their employees better than they are supporting users.
In editing mode, the OK button is not visible. But as soon as I publish my form, it appears, rather erratically. With multiple choice fields set to required it makes absolutely no sense and is even misleading.
This is definitely a serious misconception that is keeping me from buying a Pro plan or use typeform at all.
Hi @KaliMa Thanks for stopping by the community and sharing your feedback. I understand itβs frustrating not to have this feature implemented. At the moment, our product team is working on partial responses and captcha, two features which are highly requested and require quite a bit of work. Because of this, removing the ok button is not on the roadmap in the near future.
I totally get that this may mean you need to find a different service thatβs more fitting towards what youβre looking to build, but if you do decide to hang around Typeform, Iβll be happy to answer any questions you have!
Hi @KaliMa Thanks for stopping by the community and sharing your feedback. I understand itβs frustrating not to have this feature implemented. At the moment, our product team is working on partial responses and captcha, two features which are highly requested and require quite a bit of work. Because of this, removing the ok button is not on the roadmap in the near future.
I totally get that this may mean you need to find a different service thatβs more fitting towards what youβre looking to build, but if you do decide to hang around Typeform, Iβll be happy to answer any questions you have!
I donβt understand why there is an OK Button, if when the user selects an answer, it already skips to the next questionβ¦
What is the point of the OK button? (the user will never click on it)
In product teams, there are squads for new features and squads for bugs and low hanging fruits. I honestly think this request is not really a new feature
As a result of the OK button, I have no other choice but to use Jotform. Your product teamβs research that an OK button shows better completion rates is subject to the clients that build forms. In such a case as a quiz whereby answers are based on logic, an OK button distracts users and allows them to move on without answering. In the case of a quiz, it does me no good to use your product teamβs research theory that having an OK button will lead to more completed results. Tell your product team that itβs not Typeformβs responsibility to decide what makes a user complete a form; after all, the users that complete these forms arenβt Typeform clients-- I am Typeformβs client and I am trying to build a form for my users-- not yours.
As a result of the OK button, I have no other choice but to use Jotform. Your product teamβs research that an OK button shows better completion rates is subject to the clients that build forms. In such a case as a quiz whereby answers are based on logic, an OK button distracts users and allows them to move on without answering. In the case of a quiz, it does me no good to use your product teamβs research theory that having an OK button will lead to more completed results. Tell your product team that itβs not Typeformβs responsibility to decide what makes a user complete a form; after all, the users that complete these forms arenβt Typeform clients-- I am Typeformβs client and I am trying to build a form for my users-- not yours.
I agree with that 100%. We want to implement Typeform in our big company of 750 employees but the OK button is a problem for us. Also I want to add to @Liz that what we observed is that sometimes people click too fast and skip the next questions by accident.
For instance when there is Yes / No answer. They select βYESβ and while they are heading to click βOKβ the page moves to the next question and they accidentaly hit βOKβ for the next question that they left unintentionally blank. This is really big issue that criples the entire survey. Please, add the βhide buttonβ functionality or disable the βautomove to the next questionβ when the user clicks on answer!
Has this been fixed? I have a form that show yes and no answer but with an ok button. Makes no sense to have 3 buttons. I want to pay again for typeform but can't use it like this?
Hi β@Caio thanks for dropping by with your question. The OK button still appears on Yes/No questions (unless itβs the final question in the form, in which case it will display a βSubmitβ button). Iβll follow up with our product team about this request and let you know as and when we hear something...
Hello, since the new update I can't find the settings where I can make the button for OK or Next disappear until someone writes me an answer in the field. Does this setting still exist at all? Because now I have 3 surveys in the classic version and 3 in the new version. In the first three there is no way to get to the next question without writing something in. But in the other 3 surveys there is, where can I change this? In the introduction video this option is shown but it doesn't appear for me where I can make this button disappear.
Page 1 / 1
Hi @KMU Media thanks for asking! This is a great question. We havenβt had a setting like this in either the classic or new builder, but if you want to hide questions until the previous have been answered, you can use the following logic jump setup to prevent questions from appearing (and thus hiding the buttons until they enter their response). Would that help?
Hello Liz Thank you for your reply, so when I click on the "question settings" in the classic version.Then I have the option to click on Required and my button disappears on the page. As soon as someone writes something in, the butto appears.
Hi @KMU Media Ah, if youβre looking for the required setting in the new builder, you can find it as shown below:
Yes, thank you, but when you do this with the classic version, the OK button disappears. does this not work with the new version?
Thank you !
Hi @KMU Media We donβt have a guaranteed way to have the βokβ button disappear either in the new builder or the old builder, but Iβd suggest giving this a try, especially if you want to be sure that the respondent answers the question.
Hello dear typeform users,
I do have a question for you : the βnextβ / βOkβ button just disappeared from all my typeforms, resulting in a very poor UX for the very specific use i have from typeform.
Do you know how if itβs possible to parameter typeform to have this βnextβ/βOkβ button again ?
Thanks a lot in advance,
Amaury
Hi @Brousse Springsteen Thanks for stopping by! Iβve responded to your post on this. :)
I notice there is an βOKβ button on these type of questions, but as soon as a number on my 1-10 scale is selected, it jumps to the next question.
Basically, the OK button is irrelevant. Iβd really like it to work so if respondent wants to make a change they can do so.
So, is there a way to do that? ie., pick a number than hit OK?
If not, why does typeform bother with putting up an OK button?
Thanks for any clarity you can offer.
Hi @Craig Carr Thanks for stopping by the community! I added your post here where we have the answer.
Thanks, but making the question required is not quite what I was looking for as I have done that already.
What I want is that when a number is selected on this type of question that the person ALSO has to tap the OK button before jumping to the next question. This gives them a moment to change their minds.
Why even have an OK button if it doesnβt do anything?
If I am misreading or not fully understanding these posts, please let me know.
Thanks
Hi @Craig Carr Our product team tested this last year and found that the questions that had the βokβ button and were required had higher rates of completion than those that had the question required but didnβt have the βokβ button.
Hopefully that helps clarify!
Liz wrote:
Hi @Craig Carr Our product team tested this last year and found that the questions that had the βokβ button and were required had higher rates of completion than those that had the question required but didnβt have the βokβ button.
Hopefully that helps clarify!
It doesnβt really - the OK button is absolutely useless if the question moves on as soon as the user has made their selection. This is the case even for required questions, I just tested it, the question moves on instantaneously, as soon as the user has made their choice. Iβm with Craig here, I want my user to be able to select their answer - say in a multiple choice set up - have a moment to change their mind if needed, then click OK to move on. As it is currently, the OK button is, quite literally, pointless.
In editing mode, the OK button is not visible. But as soon as I publish my form, it appears, rather erratically. With multiple choice fields set to required it makes absolutely no sense and is even misleading.
This is definitely a serious misconception that is keeping me from buying a Pro plan or use typeform at all.
Hi @BensonH thanks for stopping by and sharing your experience. Iβll share this feedback with the product team to help provide a bit clearer of an explanation as to why the βokβ button is rather awkward.
Hello, One month ago BensonH (see below) posed the same PROBLEM with the OK button that users have been asking about for TWO YEARS.
I just signed on for the PLUS plan. If this problem has not been solved for two years even with the new version, itβs appearing to me that fixing problems for users is not a priority or even on Typeformβs corporate radar.
Do you see this problem with the OK button being fixed within the next month? I donβt want a workaround. I want the problem fixed. If this glitch is not going to be repaired within the next 30 days, I will find another platform that is focused on USER success not simply corporate success.
Thank you. PS I understand that youβre the messenger and have no control/power over corporate focus. Iβm hoping they support their employees better than they are supporting users.
In editing mode, the OK button is not visible. But as soon as I publish my form, it appears, rather erratically. With multiple choice fields set to required it makes absolutely no sense and is even misleading.
This is definitely a serious misconception that is keeping me from buying a Pro plan or use typeform at all.
Hi @KaliMa Thanks for stopping by the community and sharing your feedback. I understand itβs frustrating not to have this feature implemented. At the moment, our product team is working on partial responses and captcha, two features which are highly requested and require quite a bit of work. Because of this, removing the ok button is not on the roadmap in the near future.
I totally get that this may mean you need to find a different service thatβs more fitting towards what youβre looking to build, but if you do decide to hang around Typeform, Iβll be happy to answer any questions you have!
Liz wrote:
Hi @KaliMa Thanks for stopping by the community and sharing your feedback. I understand itβs frustrating not to have this feature implemented. At the moment, our product team is working on partial responses and captcha, two features which are highly requested and require quite a bit of work. Because of this, removing the ok button is not on the roadmap in the near future.
I totally get that this may mean you need to find a different service thatβs more fitting towards what youβre looking to build, but if you do decide to hang around Typeform, Iβll be happy to answer any questions you have!
Appreciate the honesty, Liz
@KaliMa I try my best! If you do think of any other questions or have any other feedback, feel free to send it our way.
I donβt understand why there is an OK Button, if when the user selects an answer, it already skips to the next questionβ¦
What is the point of the OK button? (the user will never click on it)
In product teams, there are squads for new features and squads for bugs and low hanging fruits. I honestly think this request is not really a new feature
As a result of the OK button, I have no other choice but to use Jotform. Your product teamβs research that an OK button shows better completion rates is subject to the clients that build forms. In such a case as a quiz whereby answers are based on logic, an OK button distracts users and allows them to move on without answering. In the case of a quiz, it does me no good to use your product teamβs research theory that having an OK button will lead to more completed results. Tell your product team that itβs not Typeformβs responsibility to decide what makes a user complete a form; after all, the users that complete these forms arenβt Typeform clients-- I am Typeformβs client and I am trying to build a form for my users-- not yours.
e-talk wrote:
As a result of the OK button, I have no other choice but to use Jotform. Your product teamβs research that an OK button shows better completion rates is subject to the clients that build forms. In such a case as a quiz whereby answers are based on logic, an OK button distracts users and allows them to move on without answering. In the case of a quiz, it does me no good to use your product teamβs research theory that having an OK button will lead to more completed results. Tell your product team that itβs not Typeformβs responsibility to decide what makes a user complete a form; after all, the users that complete these forms arenβt Typeform clients-- I am Typeformβs client and I am trying to build a form for my users-- not yours.
I agree with that 100%. We want to implement Typeform in our big company of 750 employees but the OK button is a problem for us. Also I want to add to @Liz that what we observed is that sometimes people click too fast and skip the next questions by accident.
For instance when there is Yes / No answer. They select βYESβ and while they are heading to click βOKβ the page moves to the next question and they accidentaly hit βOKβ for the next question that they left unintentionally blank. This is really big issue that criples the entire survey. Please, add the βhide buttonβ functionality or disable the βautomove to the next questionβ when the user clicks on answer!
Thanks a lot!
Has this been fixed? I have a form that show yes and no answer but with an ok button. Makes no sense to have 3 buttons. I want to pay again for typeform but can't use it like this?
Hi β@Caio thanks for dropping by with your question. The OK button still appears on Yes/No questions (unless itβs the final question in the form, in which case it will display a βSubmitβ button). Iβll follow up with our product team about this request and let you know as and when we hear something...