10 AI Prompts Every Salesforce Admin Should Know
Copy-paste AI prompts for Salesforce admins — with concrete examples, bonus prompts for Flow debugging and permission set design, prompt engineering tips, and an FAQ.
If you're a Salesforce admin, you can save hours every week with the right AI prompts. Here are 10 prompts I use regularly — all tested with ChatGPT and Claude — plus 5 bonus prompts, concrete examples for each core prompt, and tips for getting better results.
How to Use These Prompts
Copy any prompt below, replace the text in [brackets] with your specific details, and paste into ChatGPT, Claude, or any AI tool. That's it.
1. Write a Salesforce Flow Description
Write a clear, concise description for a Salesforce Flow with the following behavior:
[Describe what the Flow does — trigger, actions, outcome]
The description should be understandable to non-technical stakeholders and under 100 words.
When to use: Every time you build a new Flow. Good descriptions save future admins hours of reverse-engineering.
Example in practice:
Your input:
Write a clear, concise description for a Salesforce Flow with the following behavior:
Trigger: Opportunity updated, Stage changes to "Closed Won"
Actions: Creates a follow-up Task for the Opportunity owner due in 30 days; posts a
Chatter notification to the Sales Ops group
Outcome: Ensures post-close follow-up is never missed
The description should be understandable to non-technical stakeholders and under 100 words.
Sample AI output:
When an Opportunity moves to Closed Won, this Flow automatically creates a 30-day follow-up Task for the owner and posts a notification to the Sales Ops Chatter group. Ensures post-close activities are tracked and no follow-up falls through the cracks.
2. Explain a Salesforce Error
Explain this Salesforce error message in plain English.
List 3 possible causes and step-by-step instructions to fix each one.
Error message: [paste error here]
When to use: When you hit an error and the Salesforce docs aren't helping.
Example in practice:
Your input:
Explain this Salesforce error message in plain English.
List 3 possible causes and step-by-step instructions to fix each one.
Error message: FIELD_CUSTOM_VALIDATION_EXCEPTION, The billing country must be USA or Canada: []
Sample AI output:
This error means a validation rule on the Account object is rejecting the Billing Country value provided. Three likely causes: (1) A user manually entered an unsupported country — go to Setup > Object Manager > Account > Validation Rules, find the rule, and temporarily disable it to fix the affected records; (2) A data import included country values outside the approved list — re-map the import file before re-uploading; (3) An API integration is passing the full country name instead of the expected code — update the field mapping in the integration settings.
3. Write a Validation Rule
Write a Salesforce validation rule formula that:
- [Describe the condition that should trigger the error]
- Show an error message saying: "[Your error message]"
- Only apply when [any conditions, e.g. "the record is being edited, not created"]
Include comments explaining each part of the formula.
When to use: When you need to enforce data quality rules but don't want to guess at formula syntax.
Example in practice:
Your input:
Write a Salesforce validation rule formula that:
- Triggers an error if Close Date is blank when Stage is "Closed Won"
- Show an error message saying: "Close Date is required when Stage is Closed Won."
- Only apply when the record is being saved
Include comments explaining each part of the formula.
Sample AI output:
/* Fires when Stage is "Closed Won" AND Close Date is empty */
AND(
ISPICKVAL(StageName, "Closed Won"), /* Stage must equal Closed Won */
ISBLANK(CloseDate) /* Close Date must not be blank */
)
Error message: "Close Date is required when Stage is Closed Won."
4. Create User Training Documentation
Write step-by-step training documentation for Salesforce users covering this process:
[Describe the process]
Target audience: non-technical sales reps with no Salesforce experience.
Format: numbered steps with screenshots placeholders labeled [SCREENSHOT: description].
Include a "Common Mistakes" section at the end.
When to use: Onboarding new users or documenting processes after a release.
Example in practice:
Your input:
Write step-by-step training documentation for Salesforce users covering this process:
Converting a Lead to a Contact, Account, and Opportunity in Sales Cloud.
Target audience: non-technical sales reps with no Salesforce experience.
Format: numbered steps with screenshot placeholders labeled [SCREENSHOT: description].
Include a "Common Mistakes" section at the end.
Sample AI output excerpt:
Step 1: Open the Lead record by clicking the Lead's name in your Lead list view. [SCREENSHOT: Lead list view with cursor on Lead name] Step 2: Click the Convert button in the top-right action bar. [SCREENSHOT: Convert button highlighted in the action bar] Step 3: In the conversion dialog, search for an existing Account before creating a new one. [SCREENSHOT: Account lookup field in the Convert Lead dialog] ... Common Mistakes: Selecting "Do not create an Opportunity" when the Lead is sales-ready; creating a duplicate Account instead of matching to an existing record.
5. Draft a Change Management Email
Write a professional email announcing this Salesforce change to our sales team:
[Describe the change — what's changing, why, and when]
Tone: friendly but clear. Keep it under 200 words.
Include: what's changing, why it's happening, what reps need to do differently.
When to use: Before any significant Salesforce release or process change.
Example in practice:
Your input:
Write a professional email announcing this Salesforce change to our sales team:
Change: A new required field "Competitor" is being added to the Opportunity object.
Why: Leadership wants to track win/loss data by competitor.
When: Going live Monday, October 6.
Tone: friendly but clear. Keep it under 200 words.
Include: what's changing, why it's happening, what reps need to do differently.
Sample AI output:
Subject: Quick heads-up: New required field on Opportunities starting Monday
Hi team — starting Monday, October 6, you'll see a new required field called Competitor on every Opportunity. This helps leadership understand which deals we're winning and losing against specific competitors so we can invest smarter. What to do: When you create or edit an Opportunity, select the relevant competitor from the dropdown. If you're unsure, choose "Unknown." Questions? Reply to this email. Thanks for making this easy!
6. Write an Apex Class Description
Write a clear Javadoc comment block for this Apex class.
Explain what it does, its key methods, and any important notes for developers.
Class code:
[paste Apex code]
When to use: Documenting Apex code you inherited or writing new code docs.
7. Create a Test Scenario List
Generate a comprehensive list of test scenarios for this Salesforce feature:
[Describe the feature]
Include:
- Happy path scenarios
- Edge cases
- Error scenarios
- Negative tests
Format as a table with columns: Scenario, Steps, Expected Result.
When to use: Before any UAT or when building a test plan.
8. Summarize a Salesforce Release
Summarize the key new features from the [Season Year] Salesforce release notes
that are most relevant for [Sales Cloud / Service Cloud / Admin].
Focus on: what's changing, what's new, and what admins need to do before go-live.
Format as bullet points, grouped by product area.
When to use: Every Salesforce release (3x per year). Save this prompt for November, March, and July.
9. Write a Report Filter Description
Explain what this Salesforce report filter logic does in plain English:
[paste filter logic]
Then suggest 2 alternative filter configurations that would give similar results.
When to use: When you inherit a complex report and need to understand it quickly.
10. Draft a Business Requirements Document
Draft a Salesforce Business Requirements Document (BRD) for this feature request:
Feature request: [describe what the stakeholder wants]
Business goal: [why they want it]
Users affected: [who will use it]
Include sections for: Overview, Business Requirements, Technical Requirements,
Acceptance Criteria, and Out of Scope.
When to use: When stakeholders ask for something vague and you need to get it in writing.
5 Bonus Prompts
These prompts cover tasks that come up in nearly every admin's quarterly cycle but rarely get documented.
11. Debug a Salesforce Flow Error
I have a Salesforce Flow that is throwing this error at runtime:
[paste the exact error message, including any fault path details]
Flow name: [Flow name]
Flow type: [Record-Triggered / Screen / Scheduled / Autolaunched]
The error occurs when: [describe the trigger condition or the step the user was on]
List the most likely causes of this error, how to diagnose each one inside Flow Builder,
and the recommended fix for each.
When to use: When a Flow fails in production and the error message alone isn't pointing you to a root cause. Always paste the full error — including the fault path message if one exists. For a deeper workflow, see our guide to using ChatGPT with Salesforce Flow.
12. Write a Report Summary Formula
Write a Salesforce report summary formula that calculates:
[describe what you want — e.g., "win rate as a percentage of Closed Won vs. total Closed opportunities"]
Fields available in this report: [list the key field API names and their data types]
Format the result as: [currency / percentage / number with X decimal places]
Include a brief inline comment explaining the formula logic.
When to use: When you need a custom metric in a report but aren't sure of the summary formula syntax. Pair this with the strategies in How to Write Better Salesforce Reports Using AI to get from question to dashboard in minutes.
13. Design a Permission Set
Recommend a permission set configuration for this user role:
Job title: [title]
They need to be able to: [describe required access in plain English]
They should NOT be able to: [describe restrictions — e.g., "delete records, export data, modify reports"]
Relevant Salesforce objects: [list the objects involved]
Provide a table with columns: Object | CRUD Permissions | Key Field-Level Security | Special Permissions.
Flag any permissions that carry security risk.
When to use: When provisioning a new role or auditing existing permission sets before a security review. The table format pastes directly into a requirements doc or Jira ticket.
14. Extract Admin Action Items from Release Notes
I'm pasting a section of Salesforce [Spring/Summer/Winter] '[YY] Release Notes below.
Extract only the items that require admin action before the release goes live in production.
Format as a numbered checklist: [Action required] | [Feature area] | [Estimated effort: Low / Medium / High]
[paste the release notes section here]
When to use: Every release cycle. Paste sections from the official Salesforce Release Notes PDF and get a prioritized action list in seconds instead of spending an afternoon reading the whole document.
15. Write an Apex Test Class Description
Write a concise class-level comment block for this Apex test class that describes:
1. Which feature or production class it tests
2. What test scenarios are covered (happy path, negative, bulk)
3. Any obvious gaps in coverage
Also suggest 2 additional test methods that would meaningfully improve coverage.
For each suggestion, include: method name, what it tests, and one sentence on why it matters.
Test class code:
[paste test class]
When to use: When inheriting undocumented test classes or preparing for a code review. Helps developers (and future you) understand what is and isn't tested without reading every assertion line by line.
How to Get Better Results from Any of These Prompts
These prompts work out of the box, but a few small habits will significantly improve the output quality.
1. Always name the Salesforce object. Instead of "a record," say "an Opportunity" or "a custom object called Project__c." Most AI tools know Salesforce's standard schema and will tailor their output — including correct field API names — when you're specific.
2. Describe your data model briefly. If your Opportunity has non-standard stages or custom fields that affect the logic, mention them. Even one sentence — "We use a custom Stage value called 'Legal Review' between Proposal and Closed Won" — prevents the AI from suggesting something that doesn't fit your org.
3. Always ask for numbered steps. Add "format as numbered steps" to any prompt where you need actionable output. Paragraph-style answers are harder to follow during a live training session or a debugging sprint. Numbered steps are easy to hand off, copy into documentation, or check off in a meeting.
4. Paste the actual error text or code — never paraphrase. AI tools are dramatically better at diagnosing problems when they see the exact error string or the raw formula. Copy-paste beats summarizing every time. If the error message is long, paste all of it.
5. State your audience upfront. "Explain this to a non-technical sales manager" produces a completely different answer than "explain this to a senior Salesforce developer." One sentence about who will read the output changes the tone, vocabulary, and level of detail significantly.
Frequently Asked Questions
Can I use these prompts with Einstein Copilot? Some of them, yes. Einstein Copilot (now part of Agentforce) is designed for in-CRM actions like summarizing records, drafting emails from the record context, and triggering automations. For heavier admin tasks — writing validation rule formulas, generating BRDs, or debugging Flow errors — a general-purpose AI like ChatGPT or Claude gives you more flexibility and detail. The two tools complement each other well rather than competing.
Do I need a paid ChatGPT plan? No. Every prompt on this list works with the free tier of ChatGPT. That said, GPT-4o (available on ChatGPT Plus at $20/month) produces noticeably better results for complex formula writing, multi-step debugging, and longer structured outputs like BRDs or permission set tables. If you're using these prompts daily, the paid plan pays for itself quickly.
Are these prompts safe for sensitive org data? Never paste real customer data, production record IDs, PII, or confidential business information into a public AI tool. When working through the examples above — error messages, Apex code, Flow descriptions — use anonymized field names or sandbox data. If your company has a private ChatGPT Enterprise instance, a Microsoft Copilot deployment, or an internal AI tool with a data processing agreement in place, that is the appropriate environment for production-level context.
Bonus: The Meta-Prompt
When you're not sure what to ask, use this:
I'm a Salesforce admin. I need help with: [describe your problem].
What are 3 different ways I could solve this? For each option, list pros, cons, and effort level.
Want 40+ more prompts organized by category? Check out our AI Prompt Library for Salesforce — free tier available.
📬 Enjoyed this article?
Subscribe to our free weekly digest — AI tools, Salesforce tips, and prompts every week.