SMS Confirmation Widget - Is there a way to change the length of the PINs and save them with submission data?

  • alonzo_llamas
    Asked on November 8, 2019 at 1:44 AM
    enght of the PIN this widget is sending?

    And also, the PIN that's send for confirmation, is NOT saved as data when the form is submitted, any way that I can store that? I am using gsheets integration, I was able see the phone number only.

  • AndrewHag
    Replied on November 8, 2019 at 2:21 AM

    I am afraid it is not possible to change the length of the PIN and also we cannot store the PIN that was generated.

  • alonzo_llamas
    Replied on November 9, 2019 at 2:34 PM

    I tried to find the builder of this widget but couldnt find any info, in case its you, can I raise a feature request to add this as a parameter?


    As well the ability to store the returned PIN while capturing on the confirmation input

    And the option to customize the text on each of the buttons and error messages for the widget.


    That would be just awesome.


    Thanks!

  • Mike
    Replied on November 9, 2019 at 7:30 PM

    Could you please explain the purpose of saving PINs?

    Your inquiry about the customization of the SMS Confirmation widget's texts and errors has been raised to our developers via the next support thread:

    https://www.jotform.com/answers/2033142

  • alonzo_llamas
    Replied on November 9, 2019 at 8:22 PM

    Hi Mike,


    I can, I need a way for my process to demostrate that the user captured the PIN that I sent through SMS, I can get it from twilio, but I do want a double check.

    My thought process on this widget was that, since it's being captured on the form by the user, there was a way to get the data, store it and save it, in my case store it at the end on a google spreadsheet.


    Thanks, hope this clarify

  • jherwin
    Replied on November 9, 2019 at 10:46 PM

    Hello @alonzo_llamas - Can you please create a test form and add Twilio SMS and email field only and send the form link to this thread?

    We will try/see if we can find a workaround for your needs. If needed, I will forward this to our developers as a feature request.