◆ Salesforce

Leverage duplicate matching in Apex

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWhen a new Lead record is created, check if a Contact with the same 'Email' already exists. If…+
When a new Lead record is created, check if a Contact with the same 'Email' already exists. If it does, prevent the Lead from being saved and display an error message.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore we go live with the new lead capture process, make sure our duplicate matching is…+
Before we go live with the new lead capture process, make sure our duplicate matching is robust. We need to prevent duplicate leads and contacts based on 'Email' and 'Company Name', but also allow for exceptions if a sales rep explicitly overrides it. How can I configure this to be both effective and flexible for the sales team, without creating false positives or hindering legitimate new records?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentSarah from the sales team just called, frustrated that she can't create new lead records for…+
Sales reps are complaining they can't create new lead records, even for legitimate new prospects, because the system is flagging them as duplicates based on partial matches.
Sarah from the sales team just called, frustrated that she can't create new lead records for prospects she knows are unique. The system is flagging them as duplicates based on a partial company name match, even when the email is different. I set up the matching rules to catch similar company names, but now it's too aggressive. I'm afraid we're losing potential leads. What's the most common pitfall when configuring duplicate matching rules that causes over-flagging, and how can I quickly refine the rules to be more precise without letting actual duplicates slip through?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe consistently struggle with duplicate records across Leads and Contacts, leading to…+
Our database is riddled with duplicate records, causing inaccurate reporting and wasted sales effort.
We consistently struggle with duplicate records across Leads and Contacts, leading to inaccurate reports, wasted outreach by sales, and frustration. I've tried to implement matching rules, but they either catch too little or too much. This ongoing data mess impacts our credibility. What habit should I change in how I approach duplicate management to proactively prevent duplicates from entering the system and effectively merge existing ones, so we maintain a clean and reliable database without constant manual intervention?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.