Use form template without it creating custom fields that need deleting
J
JP Hogbin
Form templates are great for creating good looking forms quickly but you just want the styles, not all of the custom fields from the form template.
It's a pain to have to go and delete all of the custom fields the normal user does not realise are being created when choosing a form template.
Log In
S
Sales & Marketing
Merged in a post:
Form / Survey Object Approach
B
Bryan Stafford
We were looking to move a few clients into GHL given the update to the form and survey builder but I'm realizing that it doesn't truly replace an external form builder due to the requirement that (nearly) all information submitted needs to be mapped to a field on another object.
I don't really understand why this was approached this way.
The use case (and I know I'm not alone here) would be a client that offers a variety of services that require often extensive intake. Think: 1:1 coaching that requires a pre-session assessment, yearly client assessments, applications for higher level programs, etc.
Sure, some of that info you might want to save on the contact object but if you even have a modest amount of services that clients repeatedly consume, that puts you in the position of having to create an extremely heavy and unwieldy contact object, and even then, only the last submissions response values are saved to the field.
Forms and surveys already record historical submissions, so they already have their own object. I don't see why the form builder couldn't function more in line with the industry standard in which:
- You have all the same element types that custom fields can have (already built)
- Elements can either map to an existing field or... not. OR, of course, leave as is in terms of how custom fields are added to forms and just open up general elements of each type that don't map, etc.
This change would decimate the need for an external builder and would open up a ton of possibilities.
I don't really understand why it's not like this already. I could understand the implemented approach IF the reason was to avoid having to give forms and surveys their own object, but that's already the case.
Collaterally related: The form and survey submitted trigger in workflows - You should be able to access the information from the submission rather than having to rely on custom field mapping. I imagine that you can already do this by combining a webhook step or two, but as I've said.. the object already exists.
S
Sales & Marketing
Merged in a post:
Create form fields not related to custom fields.
A
Andrew Peters
Not every field should then have to be connected to a custom field. If I'm taking in a form that just has a message field, there's no reason that a message HAS to be connected to a custom field. This just clutters up the contact area across multiple forms.
Instead, we should have access to form fields that don't have to be connected to a custom field. On form submission these forms should create a note or (ideally) be populated as a form submission in conversations and have a tab on the contact area for 'form submissions' similar to notes.
S
Sales & Marketing
Merged in a post:
Create custom form fields without having to create a custom field
I
Ino Uy Yco
It would be amazing to have an option to create fields without having to create a new custom field specially for those question that we only use specifically on that form. A drag and drop option for text box, radio button, etc. instead of creating a new custom field for those one off.
Canny AI
Merged in a post:
custom form builder for notes for contacts within CRM
m
mark barrett
wouldnt it be awesome to create a custom form on the notes tab under contacts within the CRM.
So that way any employees you have or clients who have employees can customize what notes they want written down about their leads that are being cold called or texted when prospecting.
This would lead to higher conversions for you and your clients and put more money in all our pockets
M
Mark Hoffman
This! So annoying for everything to be a custom field. Because of this I still use an external form builder so I can store the info of the submissions separately.
S
Sara Talbert
We run 130+ workshops a year and each registration page has a different location which requires a different custom field to show- so that is 130+ custom fields living on a contact record. We don't need this field to show on the contact record. We just need the field to know what workshop they picked for a workflow automation.
We have the same issue with food options for these workshops.
It would be nice to just have form fields.
F
Frank Obregon
These 3 ideas are all asking for the same thing:
F
Frank Obregon
These 3 ideas are all asking for the same thing:
F
Frank Obregon
These 3 ideas are all asking for the same thing:
S
Shawn Hugh
Thankyou for bringing this up... make the custom fields OPTIONAL... not mandatory...
I agree it is a pain to delete those in the Custom Fields nesting... (ONE AT A TIME) which is another thing to update
Load More
→