◆ Salesforce

Create and assign tasks to reps

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 taskCreate tasks for the Acme account: assign Rajiv Kumar a discovery follow‑up due Tuesday, assign…+
Create tasks for the Acme account: assign Rajiv Kumar a discovery follow‑up due Tuesday, assign Priya Patel in product a demo prep task due Thursday, and assign me a contract clean‑up task due next Monday. Add enough detail so each person knows the exact deliverable and mark priorities in that order.
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 create tasks for the team on Acme, make them easy to act on: put the single next step…+
Before I create tasks for the team on Acme, make them easy to act on: put the single next step in the task title, include the deliverable or attachment link, set a realistic due date, and note who needs to be informed after completion. Flag any task that could block legal or finance so it gets escalated.
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 pushed a batch of tasks to Rajiv and Priya and they’re not getting done. I don’t know…+
I made tasks but reps didn’t complete them.
I just pushed a batch of tasks to Rajiv and Priya and they’re not getting done. I don’t know whether the due dates were unrealistic, the instructions unclear, or they didn’t see the assignment. What’s the likeliest reason and the fastest corrective action to get those deliverables in the next three days?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross deals, tasks I create for other reps often languish because ownership and expectations…+
Tasks keep falling through after handoffs.
Across deals, tasks I create for other reps often languish because ownership and expectations are fuzzy. Which habit to change first: require one‑sentence acceptance from the assignee or enforce SLA due dates with reminders? Recommend the habit change that will restore reliability with minimal overhead and how to check it weekly.
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.