What is JotForm?
JotForm is a free online form builder which helps you create online forms without writing a single line of code. No sign-up required.

At JotForm, we want to make sure that you’re getting the online form builder help that you need. Our friendly customer support team is available 24/7.

We believe that if one user has a question, there could be more users who may have the same question. This is why many of our support forum threads are public and available to be searched and viewed. If you’d like help immediately, feel free to search for a similar question, or submit your question or concern.

  • Profile Image

    Auto Responder Email + Condition Problem

    Asked by mediaroad on May 18, 2010 at 08:25 AM

    (1) I have setup Auto-Responder email alert with conditions associated with the checkbox.  Since there are bugs with checkbox (confirmed with another thread),   I deleted all the conditions and re-created the checkbox.  However, the form still sends out Auto-Responder email !!!!!   Something is seriously wrong...   Finally I had to delete all the Email Alerts in order to stop the email going out.

    (2) I found that something always messes up whenever I delete something,  last week I deleted 1 of 6 conditions, and then what happened was...  part of condition 2 was mixed with condition 3, and then 3 mixed with condition 4.  It was bad.  

    (3) Related to (1),  I have both  "Notification Email" and "AutoResponder Email" setup.  After I deleted all the "Auto Responder",  my "Notification Email"  email address "FROM" frield was changed from {name}   to "JotForm default" email.   Arrrrr...  Auto Responder and Notification Email are mixed up.

  • Profile Image

    Answered by MassArt on May 19, 2010 at 12:22 PM
    I believe these are the problems I'm having as well. I've made changes to conditions or email alerts and had other settings I'd set blank out.

    The notification email always goes to the formSubmitter rather than to anyone in my conditions.
  • Profile Image

    Answered by serkan on July 10, 2010 at 09:08 AM

    This problem is fixed now. Thank you all for reporting.