◆ Salesforce

Use custom labels in VisualFlows

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 taskUpdate the custom label 'Invoice_Status_Pending' to read 'Approval_Required' in all active…+
Update the custom label 'Invoice_Status_Pending' to read 'Approval_Required' in all active VisualFlows by end of day Friday, ensuring no existing flows break.
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 update the 'Invoice_Status_Pending' label, review all flows that use it. Suggest a new…+
Before I update the 'Invoice_Status_Pending' label, review all flows that use it. Suggest a new label that will be clearer for new sales reps and won't cause confusion if the approval process changes again next quarter.
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 just updated 'Invoice_Status_Pending' to 'Approval_Required' in a VisualFlow, and now new…+
I just updated a custom label in a VisualFlow, and now a critical automation isn't firing for new opportunities.
I just updated 'Invoice_Status_Pending' to 'Approval_Required' in a VisualFlow, and now new opportunities aren't triggering the follow-up task for Sarah in finance. I'm afraid I've broken the handoff. What's the most likely reason this flow stopped working, and what's the quickest way to diagnose it without impacting other sales activities?
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 breaking our VisualFlows whenever I update a custom label. It causes a ripple effect of…+
I keep breaking flows whenever I update custom labels, leading to missed tasks and angry finance people.
I keep breaking our VisualFlows whenever I update a custom label. It causes a ripple effect of missed tasks and angry calls from finance. What habit should I change to prevent these errors and ensure I'm catching potential breaks before they go live?
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.