Skip to main content
Contributor ⭐️⭐️
February 4, 2020
New Idea

Have the ability to make person fields required

Related products:CS C360 & R360 & P360
  • February 4, 2020
  • 17 replies
  • 267 views

When a CSM creates a new person account they usually add in the minimum fields that help them. It would be great to have first and last name fields required to maintain the quality of our person records.

    17 replies

    pgeorge
    Gainsight Employee ⭐️
    Gainsight Employee ⭐️
    June 8, 2021

    Hi @Wayne 

    Allowing to set mandates to the fields in the Person create form is in the roadmap. Will keep you posted on the timelines.

     

    Thank you 

    Preethi

    Contributor ⭐️⭐️
    March 23, 2023

    Any updates on this? I’m surprised that the initial request was made 3 years ago yet isn’t done as of today.

     

    saltamash
    Helper ⭐️⭐️
    June 26, 2026

    Hi Team,

    Has there been any progress on this? Wild that this is 6 year old and still isn’t fixed

    romihache
    VIP ⭐️⭐️⭐️⭐️⭐️
    June 26, 2026

    Since this was noted as being on the roadmap 5 years ago, has there been any movement or an updated timeline on releasing it?

    We are currently looking into setting up a bi-directional sync with Salesforce to upkeep our contact database, and not having this feature is a complete deal-breaker for us. Being able to create a contact with just an email address is bananas. It completely compromises data integrity.

    Even though this specific idea thread might not have hundreds of upvotes, I really hope the PM team can see how foundational this is. For anyone managing a CRM integrations ecosystem, having the ability to make first and last name fields mandatory is standard data hygiene.

    Would love to get an official status update on this!

     

     

    Continuous improvement is better than delayed perfection
    jrich
    Contributor ⭐️⭐️⭐️⭐️
    June 26, 2026

    For years, our Admin team has been stuck servicing custom CTAs just to catch Person records that are missing a first or last name. Because Gainsight allows this out of the box, we have to manually block these records from entering our other systems to protect our data integrity.

    Frankly, it reflects poorly on our data governance—and on Gainsight—that we have to build complex workarounds for standard validation.

    Gainsight is rolling out cool updates like automated email matching and AI contact sentiment. But AI requires clean data. By not enforcing basic name requirements natively, Gainsight is inadvertently contributing to bad AI data.

    Support has told us the community is the only way to get this in front of the product team, but this feedback has been here for 6 years. Product & Dev team: please give this the visibility it deserves and add native field validation to the roadmap!

    dayn.johnson
    VIP ⭐️⭐️⭐️⭐️⭐️
    June 26, 2026

    It reflects poorly on our data governance—and on Gainsight—that we have to build complex workarounds for standard validation.

    Gainsight is rolling out cool updates like automated email matching and AI contact sentiment. But AI requires clean data. By not enforcing basic name requirements natively, Gainsight is inadvertently contributing to bad AI data.

    If we don’t have clean data, we can’t truly take advantage of all the new AI features. Please, we need a LOT more controls around our person records. There’s got to be a way to get this updated.

    Staff CS Content & Comms Manager, 2x Gainsight CS Ops Product Council Member
    TMaier
    Helper ⭐️
    June 26, 2026

    Requiring an update to stale data is another great idea. Title is 18 months out of date? Confirm or update that before you can log that EBR buddy!