4 results found
-
Character limit on forms fields - phone number, name
Currently, there is no validation on the Phone field, which can lead to users entering incorrect or overly long numbers. For businesses that serve only U.S.-based clients, the system already adds the country code (+1) automatically.
To prevent users from mistakenly entering additional digits (e.g., duplicating the country code or adding invalid characters), it would be helpful to implement a character limit on the Phone field. This would ensure more accurate data entry and improve overall form validation.
8 votes -
Forms should be a separate asset that can be used in multiple meeting types
Forms now should be the same in Legacy, where they're a separate asset and can be used in multiple meeting types. This allows the admin to create a global form and apply changes if necessary in just one place
6 votes -
Native Chili Piper Forms
Having forms within Chili Piper and not needing to integrate with another form provider. It's something that a lot of people assume we have and are surprised we don’t.
4 votes -
Maintain Question Order in Meeting Description Using {{CP.DataField.AllFormFields}} Tag
When using a booking link that contains a series of form questions arranged in a specific order, the {{CP.DataField.AllFormFields}} tag currently does not preserve that order in the meeting description. Instead, the questions and answers appear in a seemingly arbitrary order.
Request:
It would be highly beneficial if the meeting description displayed the form responses in the same sequence as configured in the booking form. This would improve readability, maintain logical flow, and reduce confusion, especially in use cases where the order of questions carries context or priority.
This enhancement would help teams ensure consistency in how form data is…
1 vote
- Don't see your idea?