◆ Salesforce

Expose Flow in Community

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 taskMake sure the 'New Customer Onboarding' flow is visible and runnable for all users in the…+
Make sure the 'New Customer Onboarding' flow is visible and runnable for all users in the Customer Success Community, so they can kick off the process directly when a deal closes. Set it live by end of day.
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 expose this 'Customer Support Request' flow to our partners in the portal, make it…+
Before we expose this 'Customer Support Request' flow to our partners in the portal, make it easier for them to use. Can we simplify the first few screens, pre-fill their account info, and ensure the status updates are clear and actionable for them?
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 'Product Feature Request' flow isn't showing up for our key beta users in the partner…+
The new 'Product Feature Request' flow isn't showing up for our key beta users in the partner community.
The 'Product Feature Request' flow isn't showing up for our key beta users in the partner community, and I'm getting calls. I made sure their profile had access, but it's still missing. I can't tell if it's a sharing setting, a license issue, or something else entirely. What's the most likely culprit here, and what's the first thing I should check to get it live for them 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 troubleshooting for community flows that aren't visible or…+
I keep getting pulled into urgent troubleshooting for community flows that aren't visible or working as expected for users.
I keep getting pulled into urgent troubleshooting for community flows that aren't visible or working as expected for users, especially after deployments. It's eating into my project time. What habit should I change in how I test or deploy community flows to catch these visibility and access issues before they become emergencies for our users?
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.