◆ Salesforce

Send custom notifications to new places

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 taskSend a custom notification to the sales team, 'New Lead Assigned', when a lead from the Q4…+
Send a custom notification to the sales team, 'New Lead Assigned', when a lead from the Q4 marketing campaign is assigned to them.
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 acceptWhen a high-priority support case is escalated, create a custom notification that goes to both…+
When a high-priority support case is escalated, create a custom notification that goes to both the assigned agent and their manager, not just the agent. Make sure it highlights the case number and the client name, like 'Urgent: Case 12345 for GlobalTech'.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentInnovate Solutions, a tier-1 client, just reported a critical outage, but the usual escalation…+
Our key account, Innovate Solutions, just had a critical system outage, and the right people weren't notified immediately.
Innovate Solutions, a tier-1 client, just reported a critical outage, but the usual escalation notification only went to the primary support agent, not the account manager or our VP of customer success. I'm worried about losing their trust due to slow communication. What's the fastest way to ensure all relevant stakeholders are immediately notified for future critical cases, and what did I miss in our current setup?
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 feedback that critical updates, whether for sales opportunities or support…+
I'm always getting complaints that important updates aren't reaching the right people in time.
I keep getting feedback that critical updates, whether for sales opportunities or support cases, aren't reaching the right people quickly enough, leading to missed opportunities or delayed responses. I'm constantly scrambling to manually inform teams. What habit should I change to ensure our notification strategy is proactive and comprehensive, so everyone gets the right information at the right time?
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.