Hey everyone, Dan here again with another episode of the Tech Marketer newsletter! First off, a huge thank you for the awesome feedback from last week. It’s great to hear that you found last week’s topic on using conditional logic inside Gravity Forms useful. Many of you mentioned that you use JotForm and would like to see how to set up conditional logic in it. Your feedback is invaluable and today, we’re diving into just that.
Right now, I’m currently inside JotForm building a Service Request Form. Unlike last week’s Gravity Forms setup, I’m experimenting with JotForm’s Card feature to give our form a more streamlined and user-friendly experience. Instead of displaying everything on one long page, the Card feature breaks the form into individual steps, making it easier to navigate.
Form Details: The Basics of Custom Forms for Insurance
To get started, I’m setting up some basic fields that will be required for any type of service request. These fields include name, email, and phone number—pretty much the standard information you need to get your clients’ details down. It’s critical to make these fields mandatory to ensure we always get this essential information. To make a field required in JotForm, simply click on the Field, go to Properties, and set it to required.
Next, we’ll connect this form to an agency Zoom account so that a service ticket is created automatically through their system. This integration helps streamline the workflow, ensuring that no client request slips through the cracks.
Creating Service Request Forms
For a more tailored approach, I’m creating two separate service request forms: one for personal lines and one for commercial lines. This distinction helps to keep the questions relevant to the type of insurance service the client needs.
For the Personal Lines Form, the options are more about individual coverage needs, such as adding or removing a driver or vehicle, and other similar options. Users select specific options, triggering conditions based on their choices. Personalizing forms this way keeps them relevant and concise.
Example Conditions in Detail
One of the examples we’re setting up is adding or removing an additional insured. When a user selects this option, additional fields will appear prompting for more information. For instance, a client might need to specify which policy the change should be associated with or decide how the additional insured should appear on the policy.
Additional triggers for conditions will involve queries like “Which policy should it be associated with?” and “How should they appear on the policy?” These prompts help guide the user and gather precise information that’s crucial for processing their request without needing back-and-forth communication.
Enhancing User Experience
To see how clients will interact with the form, it’s helpful to use the preview option. This way, you can experience the form from their perspective, ensuring it’s intuitive. A progress bar at the top will track the steps, so clients know how far along they are in the process.
For example, if a client is adding or removing an additional insured, the form will automatically adapt, prompting additional steps. These steps could include entering the policy number, name, and any applicable mortgage information. Such dynamic adjustments make the form smart and responsive, improving usability.
Setting Up Conditional Logic
To set up conditional logic within JotForm, go to the Settings and then Conditions. The first condition I’m creating is tied to a personal line request and handles “add or remove an additional insured.” When selected, another question appears asking, “Are you adding or removing an additional insured?” Based on the user’s response, further fields will be shown.
If the answer is “adding,” fields will appear to capture details like “Which policy?” and “How should they appear?” Conversely, if the answer is “removing,” fields will prompt for the “Name of the additional insured to remove” and the associated policy. This keeps the form concise yet adaptive to the user’s needs.
Handling Additional Coverage Requests
Similar conditional logic setups can be applied for scenarios like adding or removing coverage. Conditions can trigger fields based on user input, ensuring that each form remains relevant while capturing all necessary details for efficient processing.
General Insights and Final Thoughts
I’ve also gathered that many of you prefer JotForms for its visual appeal, even though WordPress and Gravity Forms might provide more powerful options. It’s a balance between ease of use and functionality, and choosing the right tool often comes down to personal preference and specific needs.
As always, if there are specific topics or content you’d like to see covered in the newsletter, please let me know. Your feedback is super helpful in tailoring the content to what you find most beneficial.
Till next time, don’t hesitate to drop your questions or future requests. Thanks for reading and see you in the next issue!