◆ Salesforce

Enroll contact in nurture campaign

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 taskEnroll 1,250 contacts into the Q4 nurture stream called Mid-Market Renewal Nurture, start date…+
Enroll 1,250 contacts into the Q4 nurture stream called Mid-Market Renewal Nurture, start date October 10, cadence weekly emails for eight weeks, and set the enrollment source as Webinar Follow-up. Add the nurture membership as Active and ensure contacts on the Do Not Contact list are excluded. Confirm the first email goes out on October 10 and send me a preview.
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 enroll these contacts in the nurture path, make enrollment easy to approve. Show the…+
Before I enroll these contacts in the nurture path, make enrollment easy to approve. Show the expected open and click assumptions, surface how many lack email or consent and will be excluded, highlight which contacts are already in other active nurtures, and call out the unsubscribe risk for lists we’ve mailed in the last 30 days.
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 noticed some contacts are already in the Prospect Nurture stream and I may have enrolled…+
Contacts were accidentally double-enrolled
I just noticed some contacts are already in the Prospect Nurture stream and I may have enrolled them again into Mid-Market Renewal Nurture. I don’t know if double-enrollment will send duplicate emails or skew engagement metrics. What likely happened in my enrollment step, and what immediate actions stop duplicate sends and correct reporting before the first email goes out tomorrow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEach nurture launch I spend half a day checking consent, de-duping lists, and resolving…+
Enrollment prep eats up a day every launch
Each nurture launch I spend half a day checking consent, de-duping lists, and resolving concurrent enrollments. It’s a recurring bottleneck that delays send dates. What single persistent change to my enrollment workflow or checklist would save me that time and reduce errors?
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.