◆ Salesforce

Optimize SOQL query performance

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskWrite a query to get all open opportunities for accounts located in California, ordered by…+
Write a query to get all open opportunities for accounts located in California, ordered by expected close date, and include the account name and opportunity amount.
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 I run this query for the Q3 sales report, make sure it pulls all open opportunities for…+
Before I run this query for the Q3 sales report, make sure it pulls all open opportunities for accounts in California as fast as possible, ordered by close date, including account name and amount, so the dashboard updates without delay.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm trying to pull all open opportunities for accounts in the Northeast region for the…+
My report query is timing out when I try to pull all opportunities for accounts in the Northeast.
I'm trying to pull all open opportunities for accounts in the Northeast region for the quarterly review, but the query keeps timing out. The dataset is huge, and I'm afraid I'm pulling too much or doing it inefficiently. I need this data for the VP's presentation on Monday. What's the most likely bottleneck, and what's the quickest way to get this query to run successfully without breaking anything else?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur reports and dashboards are consistently slow, and I suspect it's because many of our…+
Reports and dashboards are frequently slow due to complex data queries.
Our reports and dashboards are consistently slow, and I suspect it's because many of our queries are inefficiently written, especially when dealing with large datasets or complex relationships. This impacts everyone's ability to get real-time insights. What's one habit I can change in how I approach writing queries to consistently improve performance across the board?
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.