◆ Salesforce

Identify flow from flow ID

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 taskFind the details for the 'New Account Welcome' flow so I can see which email template it's…+
Find the details for the 'New Account Welcome' flow so I can see which email template it's using for the initial outreach to Sarah in marketing.
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 deploy this flow, show me the steps and decision points. I need to make sure it…+
Before I deploy this flow, show me the steps and decision points. I need to make sure it handles the edge cases we discussed for expired contracts, especially for the key accounts like Acme Corp.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe 'Deal Won' flow keeps failing for our enterprise clients, specifically when the account…+
The 'Deal Won' flow just failed for the third time this week for a major client.
The 'Deal Won' flow keeps failing for our enterprise clients, specifically when the account manager is new. It’s supposed to update the opportunity stage and assign tasks, but it's not. I'm afraid we're missing critical follow-ups and upsetting new buyers. What's the most likely cause, and how can I quickly diagnose it without disrupting live deals?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly double-checking flow execution after every deployment, especially for critical…+
I spend too much time manually checking flow execution after a deployment.
I'm constantly double-checking flow execution after every deployment, especially for critical processes like onboarding and renewals. I worry about missed steps and data integrity. What habit can I change to ensure flows are robust and reliable from the start, reducing my post-deployment anxiety?
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.