◆ Salesforce

Log support cases from customers

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 taskA customer just emailed about a broken reporting widget; log the support case for Jenna Morales…+
A customer just emailed about a broken reporting widget; log the support case for Jenna Morales at Brightwave Inc. Store the customer's contact, tag the case as 'Reporting Bug', set priority to High, link it to opportunity BW-2025-Q3, and include the full error text they sent. Assign it to Tier 1 support and notify Jenna that we've logged her case with an expected 24-hour initial response. Ensure the SLA start time reflects the email timestamp.
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 hand this case to support, make it easy for them to act. Put the customer-impact…+
Before I hand this case to support, make it easy for them to act. Put the customer-impact summary (what's broken, how many users affected and the error text) at the top, show recent deployments or config changes in the last 14 days, surface any open incidents for Brightwave Inc., and flag missing access details or logs that would make an engineer hesitate to triage. Highlight what the support lead must ask Jenna to unblock work fast.
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 filed the reporting widget case for Jenna and assigned Tier 1, but she just called saying she…+
I opened a case but the customer called furious that nothing changed.
I filed the reporting widget case for Jenna and assigned Tier 1, but she just called saying she hasn't received our acknowledgement and the widget is still down. I'm afraid the assignment missed the right support queue or the SLA clock didn't start. I can't tell if the notification failed or if there is a queue misrouting. What's the most likely reason and the immediate steps to confirm the assignment, start the SLA, and reassure Jenna before escalation?
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 month I keep creating cases that sit untriaged because they lack logs, deployment…+
Cases keep getting logged with missing logs or context.
Over the last month I keep creating cases that sit untriaged because they lack logs, deployment context, or contact access, which costs us credibility and extra calls. What routine should I adopt to capture the critical three items every time I log a case, and what two habits with product and support will reduce back-and-forth while keeping the customer informed?
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.