◆ Salesforce

Debug a flow

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 taskThis flow for new customer onboarding isn't assigning the welcome task to Michael. Check the…+
This flow for new customer onboarding isn't assigning the welcome task to Michael. Check the assignment logic and make sure it triggers when the 'Customer Status' field changes to 'Active'.
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 acceptThe 'New Lead Qualification' flow is creating too many unqualified tasks for sales. Before it…+
The 'New Lead Qualification' flow is creating too many unqualified tasks for sales. Before it goes live for the whole team, add a step that checks if the 'Lead Source' is 'Referral' or 'Event' before assigning a follow-up task, otherwise send an email to marketing for review. We need to focus sales on the best leads.
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 'Contract Renewal' flow for Acme Corp just failed and didn't send the renewal notice. The…+
The 'Contract Renewal' flow just failed for a key account, and I'm not sure why.
The 'Contract Renewal' flow for Acme Corp just failed and didn't send the renewal notice. The finance director is asking about it, and I'm afraid of missing the renewal window and losing the client. I can't tell if it's a data issue or a logic error in the flow itself. What's the most likely cause for a renewal flow failing, and what's the fastest way to diagnose it so I can get that notice out today?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep getting pulled into urgent calls because a flow didn't trigger, or it did something…+
I keep getting calls about flows not triggering or doing unexpected things.
I keep getting pulled into urgent calls because a flow didn't trigger, or it did something unexpected, costing us time and sometimes even a sale. It feels like I'm always reacting to problems instead of preventing them. What habit should I change in how I build or test flows to catch these issues before they impact the sales team or our customers?
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.