Prevent Duplicate Form Submissions Based on Name, Email, and Mobile – Client Registration

Hi Softr Community :wave:

I’m building a client registration system using Softr forms connected to Airtable, and I need help with preventing duplicate entries.

What I’m trying to achieve:
I want the form to check if a client already exists based on a combination of Name, Email, and Mobile Number before allowing submission. If a match is found, the form should not submit and instead display a clear error message like:

“A client with this name, email, and mobile number already exists.”

Requirements:

  • Must work natively within Softr + Airtable, no third-party tools like Make/Zapier, custom codes are welcome.
  • Ideally show the error on the form in real-time or on submission.
  • Allow legitimate new entries to go through normally.

Has anyone done something similar or can guide me on the best way to implement this?

Thanks in advance for any help! :pray:

Thanks for this feedback, it’s a good one! I’ve shared with my team so we can discuss forward and potentially implement in the future.

@Jjenglert, doesn’t Softr already do this with sign up (for email)?

Hi there, we’re already planning on offering it for certain input type, such as email & phone number :slight_smile:

However, they’ll be individual field validation. In other words, if you’ve enabled “Don’t allow duplicated value” for Email & Mobile inputs, then if either value is duplicated, submission won’t be allowed.

We don’t plan on offering “combo” logic at this moment. And to be honest, it’s not ideal for your use case. Either Email & Mobile alone is already a good client identifier as they should only belong to one person. You’d know something isn’t right if either value is not unique.

If you only consider it duplicated based on the combination of all 3 value, then it’s going to have the opposite effect (E.g. someone made a typo in one value and the system won’t consider it duplicate :sweat_smile:)

1 Like

Thank you austin for the reply.

What’s the estimated timeframe for this feature to be launched?

Also, I meant Individual Field Validation :slight_smile:

Any custom code to achieve this meanwhile?