Sections in this category

Where to Use Forms

Forms allow you to ask customers specific questions and record their answers in CRM. The following article provides an overview of the different places to use forms. Note that depending on your Cobalt version, you may not have access to all the options listed here.

Meeting and Class Registration Forms

While not required, a form can be added to a Meeting or Class Registration Fee as seen above to allow organizations to collect additional data from registrants. This data can remain on a Form Response record related to the registration and/or can be mapped directly to fields in CRM as needed.

Application Forms (Membership and Certification)

Membership Application Types, Initial Certification Application Types, and Continuing Certification Types, can all collect additional data through forms listed on the "type" record. This data can remain on a Form Response record related to the application and/or can be mapped directly to fields in CRM as needed.

Profile Setup and Profile Update

On the settings record you can set a form to collect additional data as part of the profile creation/setup process, and/or the profile update process. This data can remain on a Form Response record related to the contact record and/or can be mapped directly to fields in CRM as needed.

Nomination and Voting Forms

As part of the election process you can collect information from people when they nominate others and/or when they vote for candidates. Forms can be linked to the election record. This can collect information related to the nomination or voting records.  This data can remain on a Form Response record related to the entity specified and/or can be mapped directly to fields in CRM as needed.

Please note that these forms should only be used for logged-in Contacts. Currently form responses submitted by non-logged in Contacts will be cleared.

Stand Alone Forms

When creating a form in the Form Designer you can designate and entity specific form that will show up under the Forms tab of the portal as a stand alone form. This can collect information related to the entity you select in the Form Designer.  This data can remain on a Form Response record related to the entity specified and/or can be mapped directly to fields in CRM as needed.