Request Form Settings

The name of the request form.

The way in which the registrant entered the database. Choose a registration source from the drop-down list.

If you do not select a registration source, it will not be updated for existing contacts and no source will be recorded for new contacts.

Choose a permalink that is unique to your project. For example, if your form is named “Request Form” you might use “request-form” as your permalink. Be sure that your permalink contains only lowercase letters, numbers, dashes (-), and underscores (_).

By default, successful submissions will be directed to a generic Spark success page, but you can direct successful submissions to a webpage by entering the full URL (must include http). This allows submissions to be directed to a custom, project-branded page.

By default, unsuccessful submissions will be directed to the Spark-hosted version of the form you are using, but you can direct unsuccessful registrants to a webpage by entering the full URL (must include http).

This section is prepopulated with “Request” and cannot be updated.

Choose an interaction type to be automatically logged to the Primary Purchaser’s contact profile for each successful request form submission.

If this field is left blank, no interaction will be recorded.

Set the maximum number of selections that can be submitted on each request form. For example, “3” will allow up to 3 individual units or floorplans to be selected on each form.

If multiple selections are made, they are ranked by input order.

Set the maximum number of separate requests that can be submitted by a Purchaser on the same request form.

If no limit is specified, a Purchaser may submit an indefinite number of request forms.

Note: The form submission limit only restricts the number of submissions for the individual form it is applied to; if you have multiple forms, the Purchaser may submit each form up to its individual limit.

If you are building a custom request form,  your web developer will need to to dynamically fetch inventory and floorplan data from Spark. Toggle on the inventory or floorplan endpoint as needed, which will return the ids and names of the inventory and floorplans, which will supply as configured on the form.

More complex implementations can be achieved using the Spark API.

If you are using the Spark-hosted request form or an iframe, you do not need to turn either toggle on.

Indicates whether submissions to this form's URL should be accepted without a recaptcha response. This is only for users who are creating custom forms from the raw HTML and have added the Google Recaptcha widget. 

Do not toggle this setting on if you are using an iFrame, the Spark-hosted form or your form does not contain this widget because none of your submissions will post successfully. See the Recaptcha & Anti-Spam article for more information.

Select which rating to apply to new contacts using the request form. If the form includes an agent section, you can choose to apply one rating to agents and another rating to all other contacts. 

If the contact already exists in your database, their rating will not be updated when they submit a Request Form.

Fill in the form address and name, choose an email template to automatically send to successful respondents and fill in the subject line field. If this section is left blank, no email will be sent. 

Note: if anyone replies to the auto email, the reply will be directed to the from address, so be sure to use a valid, monitored email.

Choose to assign new contacts using the request form to a specific team member or to assign to a group of team members on a rotating basis (team members must have auto assign turned on in Team Settings to be included in the rotation). If no assignment is chosen, the registrants will not be assigned.

You can also select follow up schedules to automatically apply to contacts and agents upon request form completion. For more on this topic, see the Follow Up Schedules article.

Choose a team member to be notified each time someone registers using the form. If no team member is selected, users will not be notified of new registrants by email.