Skip to content
Prevent

See the duplicate
before you create it

Matches appear while a record is still being typed, on the record page, and on web forms. Warn the person, or block the save.

What changes when a duplicate shows up

Before Plauti

  • A rep re-types a customer who is already there. Nobody notices until two reports disagree.
  • A web form creates a second record every time a returning visitor comes back.
  • Someone works a record for a week before spotting the same customer under a second one.

WithPlauti

  • Matches appear on the form as they type, with a score and the fields that matched.
  • Submissions run the same check. Clear matches resolve on arrival, the rest queue for review.
  • Opening a record lists the duplicates it already has, with a merge right there.

Set it up once. It runs in three places.

One scenario decides what counts as a duplicate, wherever the record comes from.

  • The create and edit form

    Matches and their scores appear while the form is still being filled. Per object: a warning to dismiss, or a block they cannot save through.

  • The record page

    A component lists the duplicates a record already has, as it opens. Users merge from there, or discard with a reason so it stops coming back.

  • Web forms

    Above the score you set, a match is merged on arrival. Below it, it waits in a queue.

Does it work the way you need it to?

The four things admins check before prevention goes near production.

  • Control

    Configured per object and per surface.

    • Separate scenarios for creates and for edits.
    • A different threshold per entry channel.
    • Cross-object matching, with fields mapped between types.
  • Permissions and override

    Enforcement runs inside the permission model you already have.

    • Override depends on access to one field.
    • The check never merges or deletes by itself.
    • Who changed what, and when, is recorded.
  • Your users, not just your admins

    The people who know the data resolve it, inside your guardrails.

    • Shown to the teams you choose, hidden from the rest.
    • Users resolve duplicates without admin involvement.
    • What they discard is stored centrally for review.
  • Fits the workflow you have

    It sits in the flow of work, not beside it.

    • Replaces the standard create and edit form.
    • Or sits on its own button, so inline editing keeps working.
    • Restore puts merged records back.

Watch a duplicate get caught.

Interactive product tours — no install, no sales call.

More product tours

Customer quote

Prevent bad data

“I just really like that it's all built in. As you enter a new lead, it tells you right there there's a duplicate or the email is wrong. Again, we're just saving time and making everything a little more efficient.”
Wedgewood Weddings logo

Alex Casey — Sales Technology Innovator

Wedgewood Weddings

Wedgewood Weddings

Frequently asked questions

Does a duplicate get blocked, or just flagged?

Your choice, per object: a warning the person can dismiss, or a block they cannot save through, with an override granted through one field permission. Web form submissions are never blocked — they are written, then merged or queued.

Why are web form submissions not blocked?

An incoming record often carries something the existing one does not: new consent, recent activity, a changed field. It is let in, then resolved.

Does replacing the entry form break inline editing?

Yes, for any object where you override the standard edit button. Where it matters, leave that button alone and add a separate one for the checking form.

What if the matching is too aggressive?

Each scenario shows the fields it compares, their weights and the threshold, so you can see why two records matched and tighten it per object.

What happens if an automatic merge was wrong?

Merged records can be brought back, down to a single field, with related records reattached and a full audit trail.

See how it works

Talk with one of our experts to see how that works for your use case.