Create and use forms

Moxie's versatile forms feature helps you connect with your clients from capturing a lead to setting up meetings.

Michelle Lee avatar
Written by Michelle Lee
Updated over a week ago

This guide will help you get the information you need from a potential client to submit a proposal that will impress. Use Moxie's form feature to learn more about the client’s needs and determine if there’s a good fit.

Watch this video or read more about forms below.

Why forms?

Forms can be used throughout your client lifecycle.

1) Lead capture - Use a form embedded in your Web site to capture a lead that can be easily converted to a client in Moxie with just one click.

2) Discovery forms - Find out what a client needs and use it to create the perfect proposal and contract.

3) Requests and ticketing - With a customized form and your client portal, you can create requests and tickets for your clients to complete when they need something from you.
4) Other information - Capture information needed from current clients before a meeting or anytime you're collecting standardized information.

Adding a form

Navigate to "Form builder" from the workspace settings in the lower left corner and select the "Forms" tab. All of your created forms will be saved here for future use. Create a new form or choose one of your previously created forms.

Content blocks

There are three main categories of content blocks.

  • Form inputs - allow you to gather information. This includes text inputs, drop down, radio buttons, check boxes, file uploads, and dates.

  • Content blocks - allow you to add rich text and media, images, and logo placement.

  • Layout elements - allow you to specify page breaks, horizontal dividers, spacing as well as a container which allows creating multi-column forms / sections.

To add content to your form, simply click and drag an element from the left bar into your page. Once it's on your page, you can move elements up and down by simply dragging and dropping them.

When you are ready to customize your form elements, simply click on any of the elements on your form and the element edit window will become available to modify the settings.

The active element will be highlighted with a drop shadow so you can see exactly what you are modifying. When you are done modifying the settings of the form input, simply click done to return to the main element screen.

Pages allow you to break down your form into smaller chunks to make it easier for the individuals filling the form. (Note: pages will be silently ignored when the form is utilized in a meeting scheduler or in the Request/Ticketing module)

To break your form down into multiple pages, simply drag page separators into the areas where you want page breaks.

The outcome for the end user will be a multi page form experience with customizable forward and backward buttons.

Field Mapping

One of the most valuable features of using integrated forms is the ability to map data captured in the form into structured data in the CRM that can be associated with new opportunities, contact records, etc.

Any of the form input fields can be mapped to any element in the client CRM dataset, including custom fields.

Conditional Form Fields

Another handy feature of our integrated forms is the ability to add conditional logic to each form field. This will allow you to show or hide fields depending on answers to previous fields. Let's walk through setting up a few conditional forms.

After inserting a few fields into your form, you can click one of them and select the "Conditional Logic" tab at the top.

Flip the switch to turn on conditional logic, and you will see several settings to add conditionality to the field.

The first option selects the style of conditionality for the field. Selecting AND will make it so the field is visible only if all of the conditions are met, and selecting OR will make it so the field is visible if any of the conditions are met. Don't worry if you forget, because there is a nifty tooltip to describe which setting you chose!

From here, the next step is to start adding conditions! Click on "Edit" to open the condition editor. Opening the editor for the first time will automatically create a new, empty condition to get you started.

Each condition is made up of three fields: Field name, Operation, and Answer:

  • Field name - is the mapping key for the form field that is going to be determining whether this field is shown or hidden

  • Operation - is the way that you want this condition to be checked. There are 6 options for the operation:

    • is - will be true if the answer to the question is exactly the same as the option in the Answer field

    • isn't - will be true if the answer to the question is anything except the option in the Answer field

    • is answered - will be true if the question is answered in any way

    • isn't answered - will be true if the question is not answered at all

    • contains - will be true if the answer to the question in some way includes the option in the Answer field.

    • doesn't contain - will be true if the answer to the question does not include the option in the Answer field. These are most useful for text-input fields.

  • Answer - is the desired (or undesired, depending on the operation) answer that will trigger the condition

NOTE: When using a Checkbox, you must use the "contains" or "doesn't contain" operation to look for one or more options in your checkbox list.

Let's say that we want this field to show if the first field was answered "Yes". To do this, we set the Field name to the mapping key for the first question (Field1), set the condition to "is", and set the answer to "Yes".

If you want to add another condition, you can click "New condition" to create a new line. Otherwise, click "Save Changes" to put your condition into effect! Once your condition is in effect, you can see a green check in the "Conditional Logic" tab as well as a condition symbol next to the question with the condition active.

And now, the condition is live! When someone is answering your form, they'll see this:

Some things to note when creating conditional forms:

  • If there is only one option, it does not matter if you select AND or OR. They will both only show if the one condition is met.

  • Blank/empty conditions will always be false. If you are having problems with your conditions, make sure there aren't any sneaky blank conditions hanging around.

  • Conditionality can be applied to all form fields with the exception of Horizontal Dividers, Page Breaks, and Spacers.

    • This means containers have conditionality, and items within containers can have separate conditionality.

Form Settings

The settings tab in the form configuration allow you to configure what happens after a form is submitted.

  • Confirmation email template - will be the automated email template that is sent out upon submission of the form. Please note that you must include an "Email" mapping in the form answers for the template to be sent successfully.

  • Add submission to pipeline - if a stage is selected here, a new opportunity will automatically be added to the pipeline with all of the information captured in the form associated. This can be used with workflow automations to automatically trigger events as soon as someone submits a form on your website.

  • Redirect URL - Must be a fully qualified URL in format. Note: if your form is embedded in an iFrame, this feature is not supported as the content within an iframe does not have permission to redirect a parent form. You can follow this help article for a workaround when using iframes and redirects.

  • The text block on the settings screen is used to show a confirmation / thank you message after the form as been submitted. If you are using a redirect, this is not required and will not be visible by the end user.

Form Styles

Almost everything in the form is customizable including font, font size, icons, colors, etc.

View results

To view the results of a form, you can click the form itself and the 3 dots in the upper right corner of the form and click "View results." If you have sent the form directly to a client from their client overview, you'll also be able to see these answers in the "form" tab under that client as well.

You can also opt to have answers emailed to you. In the form, click settings and then check the box to "Send results in notification email." You will want to uncheck this box if people will be entering sensitive information that should not be stored in email.

How to think about using forms

Forms can be used to get some basic information from a prospect, scope of a project, or really anything you need to know. Some questions you could ask include:

  • What is your budget for this project?

  • How long will this project last? (e.g. 1 week, 3 months)

  • Briefly describe the project.

  • Which of my services are you interested in? (accompanied by a multiple-option list of services you offer)

The options are limitless here! Ask for any information you’ll need to develop a proposal and write up a contract for the client.

Using your form

Depending on your type of form, you can choose to embed it directly on your website or get a direct link. Click "Share" in the upper right corner and choose the option that makes the most sense for this form.

Moxie allows you to create as many forms as you'd like. Each form can be used as a template for future use.

You can add your form to a meeting scheduler or client ticketing.

Lead capture

Anytime someone completes a form (from a link or embedded in your website), you will get a notification and they will be added to the inquiry column in your pipeline. View answers by clicking the notification or in the column in pipeline.

Add your new lead as a client by opening their submission in pipeline, click "Activity," then the icon for the form submitted. Then select "+ Create Client."

So, what’s next?

If you captured a lead with forms, confirm you are the right fit with your client via email or by creating a meeting to get any questions you still have answered. If you feel you’d be a good fit for the client, go ahead and create an agreement.

Did this answer your question?