◆ Salesforce

Log call outcomes and call duration

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 taskI finished a 12-minute call with Jordan Hayes at AcmeCo about next-quarter renewal. Log outcome…+
I finished a 12-minute call with Jordan Hayes at AcmeCo about next-quarter renewal. Log outcome as 'left voicemail' or 'positive demo interest' only if you heard commitment; set call type to 'Customer Success Check-in', enter 12 minutes for duration, and tag the related opportunity 2026-Q3-Renewal so reports pick it up. Confirm notes mention agreed next step and date before saving.
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 log this call for Jordan Hayes, make it easy for a manager to see whether it advances…+
Before I log this call for Jordan Hayes, make it easy for a manager to see whether it advances the deal: surface the decision-maker status, the agreed next step and date, and any blockers in four words or fewer; flag if duration is over 10 minutes or outcome is ambiguous so I can review.
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 had a 7-minute call with Jordan Hayes where he sounded rushed and promised to 'look' at…+
I just wrapped a call but I'm unsure if it counts as 'conversation' or 'voicemail'
I just had a 7-minute call with Jordan Hayes where he sounded rushed and promised to 'look' at the deck. The contacts listed include Jordan and his procurement lead, I don't know if Jordan can approve, and the CRM only lets me pick one outcome. What's the most defensible outcome to log to keep the forecast honest and the next step clear? Recommend wording for the note and which outcome to choose.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOver the last quarter I keep entering 'Left message' or 'Discussed, follow up' and then…+
I keep logging vague outcomes that managers later question
Over the last quarter I keep entering 'Left message' or 'Discussed, follow up' and then management pushes back in review. I lose credibility and my pipeline looks fuzzy. Where am I getting lazy — outcome selection, note discipline, or contact qualification — and what's one concrete habit to stop this next month so my activity looks clean and reliable?
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.