Salesforce admins are expected to be technical, strategic, and politically skilled—simultaneously.
You're managing flows and SOQL queries in the morning. By afternoon you're explaining to an SVP why their dashboard doesn't show the numbers they expected. Before you leave, you're writing release notes for a deployment that changes how the sales team does their job. Nobody warned you the hardest part of being a Salesforce admin would be the writing.
The open web has almost no ChatGPT content targeted at Salesforce administrators. The few productivity articles that exist are generic "write better emails" advice. None address the Salesforce-specific workflows that actually eat your time: documenting flows before they become unmanageable, writing training materials that sales reps will actually read, or communicating org changes to stakeholders who barely know what Salesforce is.
Here are 35 prompts—organized into 7 categories—built around the real documentation and communication workflows Salesforce admins deal with every day.
1. Flow and Automation Documentation
Undocumented flows are technical debt with a fuse. These prompts help you capture what you built before you forget why you built it.
Prompt 1 — Flow documentation
"Write technical documentation for a Salesforce Flow. The flow name is [Lead Routing Flow v3]. Its purpose: route new leads to the correct sales rep queue based on territory (state), lead source, and company size (employees > 500 = Enterprise queue). Document: trigger condition, decision logic at each element, error path handling, and the record updates made on success. Include a Limitations section."
Prompt 2 — Flow change log entry
"Write a change log entry for an update to our [Account Tier Classification Flow]. What changed: added a new tier ('Strategic') for accounts with ARR > $500K, updated the Account_Tier__c field picklist, and added a task creation step notifying the account manager. Include: date, change summary, reason for change, testing approach, and who approved deployment."
Prompt 3 — Automation inventory description
"Write a one-paragraph description for our Flow Inventory document. Flow: [Opportunity Stage Change Notification]. This flow runs when an Opportunity stage changes to 'Closed Won' or 'Closed Lost.' It sends an email to the opportunity owner's manager, creates a follow-up task if the deal is Closed Lost with amount > $50K, and updates the Win_Loss_Reason__c field if empty. Make it readable for a Salesforce admin who didn't build it."
Prompt 4 — Process documentation for handoff
"Write a process documentation document for handing off our [Territory Assignment automation] to a new admin. Include: what the automation does, what triggers it, the objects and fields involved, known edge cases and how they're handled, what to check in testing before any changes, and a list of related automations that might be affected by changes to this one."
Prompt 5 — Flow deprecation notice
"Write a technical deprecation notice for [Old Lead Assignment Rules — Workflow Rules]. We're replacing this with a new Flow in our next deployment. The notice should cover: what's being deprecated, the replacement (with flow API name), timeline, any impact on existing records, and what admins should stop using/referencing."
2. Training Materials and User Enablement
Salesforce training that doesn't get read is money spent to create confusion. These prompts help you write materials reps actually use.
Prompt 6 — Quick reference guide
"Write a one-page quick reference guide for sales reps explaining how to log a call activity in Salesforce correctly. Include: where to find the Log a Call button, required fields and why they matter (especially Call Type and Description), how to relate the activity to the correct record (Account, Contact, or Opportunity), and the top 3 mistakes reps make that cause reporting errors."
Prompt 7 — Feature announcement email to users
"Write an announcement email to our 120-person sales team introducing a new Salesforce feature we've just deployed: [automatic email capture from Gmail via Salesforce Inbox]. Tone: enthusiastic but clear. Cover: what it does, why it matters for them (no more manual logging), how to activate it, and who to contact if they have questions. Keep it under 250 words."
Prompt 8 — Walkthrough script for training session
"Write a 15-minute walkthrough script for training sales managers on our new [Forecast Hierarchy dashboard]. The audience knows Salesforce basics but has never seen this view. Script should include: what to click at each step, what each section means in plain English, how to identify deals at risk using the red/yellow indicators, and 3 questions to ask to check comprehension."
Prompt 9 — FAQ document
"Write a FAQ document for our sales team about our Salesforce data hygiene initiative. Include at least 8 questions covering: why we're enforcing required fields now, what happens if they don't fill in fields (we're tying it to bonus eligibility reporting), how to handle contacts they don't have full info for, and how to report data they can't correct themselves."
Prompt 10 — Release notes for users (non-technical)
"Write user-facing release notes for our Spring '26 org update. Changes being released: (1) Opportunity Products are now required before moving to 'Proposal' stage. (2) Account phone field is now required. (3) New 'Partner Deal' record type for channel sales. Write for sales reps who don't know what 'record type' means technically — explain what changed and what they need to do differently."
3. Stakeholder Reports and Executive Communication
Salesforce admins own reporting that executives misread, misquote, and make decisions from. These prompts help you communicate what the numbers actually mean.
Prompt 11 — Dashboard interpretation memo
"Write a memo explaining our Q1 Pipeline Health dashboard to our VP of Sales. The dashboard shows pipeline coverage is 2.8x (target is 3x), average deal age in 'Proposal' stage is 47 days (benchmark: 21 days), and 23% of opportunities have no activity logged in 30+ days. Explain what these metrics mean, what they suggest about Q1 risk, and what levers the VP can pull with their team."
Prompt 12 — CRM adoption report
"Write a monthly CRM adoption report for our Chief Revenue Officer. Data: 78% of reps logged at least one activity this week (target: 90%), 34% of closed opportunities are missing close notes (target: < 10%), and our forecast accuracy for Q1 was 71% vs. 80% target. Include: what's driving the gaps, what we're doing about it, and what we need from leadership to close the gap."
Prompt 13 — Org health summary
"Write a quarterly Salesforce org health summary for our executive team. Cover: total active users (312 licensed, 287 active), automation count (47 Flows, 3 legacy Workflow Rules remaining), technical debt highlights (the 3 things most likely to cause problems in the next 90 days), and our top priority project for next quarter with business justification."
Prompt 14 — Data quality report
"Write an executive summary of our Q1 data quality audit. Findings: 18% of Contacts missing email address, 31% of Accounts missing Industry classification, and 7 duplicate Account records identified (3 are tier-1 customers — risk of split history). Prioritize by business impact and recommend a data steward model as a long-term fix."
Prompt 15 — ROI report for Salesforce investment
"Write a 1-page ROI summary for our Salesforce investment for our CFO. License cost: $240K annually. Quantifiable value delivered this year: (1) reduced manual reporting time by ~8 hours/week across 4 ops staff = $48K saved, (2) improved forecast accuracy from 60% to 80% (reduce over-hiring by 2 reps = $280K avoided), (3) 3 new automations eliminated 15 hours/week of rep admin work = $92K in recovered selling time."
4. Technical Documentation and Architecture
The documentation that survives admin turnover is the documentation that was written for the admin who comes after you.
Prompt 16 — Object and field documentation
"Write the data dictionary entry for a custom Salesforce object: [Renewal_Opportunity__c]. Include: object purpose (one sentence), key fields and their data types/purpose, the relationships to other objects (Account, Contact, Opportunity), business rules enforced by validation rules or flows, and who owns data entry for this object."
Prompt 17 — Integration documentation
"Write technical documentation for our [Salesforce-to-Marketo] integration. Cover: what data flows in each direction, sync frequency, the fields that are mapped and in what direction, what happens when a conflict occurs (Salesforce wins on lead status, Marketo wins on email preference), and the monitoring process to catch sync failures."
Prompt 18 — Permission set documentation
"Write documentation for our [Sales Manager Permission Set]. Include: what access this grants that the standard Sales User profile doesn't (view all records in territory, edit Opportunity close dates on other reps' deals, access to Forecast module), who should be assigned this permission set, the approval process to grant it, and any conflicts with other permission sets to watch for."
Prompt 19 — Validation rule documentation
"Write the documentation comment for a Salesforce validation rule named [Require_Close_Note_on_Lost_Deal]. Rule logic: fires when Stage = Closed Lost AND Close_Note__c IS NULL. Error message shown to user: 'Please enter a close note before marking this opportunity as Closed Lost.' Document: business reason for this rule, edge cases it doesn't handle, and how to bypass it in data migration scenarios (admin bypass field)."
Prompt 20 — Release planning doc
"Write a release plan document for deploying our [Spring Cleanup Release] to production. Changes included: 3 new Flows, 1 updated page layout, 2 new validation rules, and permission set updates for 12 users. Include: pre-deployment checklist, deployment order (specify dependencies), rollback plan if something breaks, communication plan for affected users, and post-deployment validation steps."
5. User Management and Access Requests
Access requests are low-stakes decisions that compound into high-stakes security problems. These prompts help you handle them systematically.
Prompt 21 — Access request policy
"Write a Salesforce access request policy for our IT/security team. Cover: how users request access (ticketing system vs. direct request), required approvals by access level (standard user vs. elevated permissions), SLA for provisioning (48 hours standard, 4 hours emergency), documentation requirements, and quarterly access review process. Tone: clear, enforceable, not bureaucratic."
Prompt 22 — Offboarding checklist
"Write a Salesforce user offboarding checklist for when an employee leaves. Include: steps to deactivate account, how to handle their open activities and pipeline (reassign vs. archive), what to do with their list views and dashboards (assess, reassign, or delete), how to handle their active automation subscriptions, and the 5 things to check 30 days after offboarding to confirm nothing broke."
Prompt 23 — Bulk user provisioning communication
"Write the internal communication to IT and HR announcing our new Salesforce user provisioning process. New process: all new sales hires are provisioned by day 1 via an automated onboarding flow triggered when HR marks the employee as Active in Workday. Existing manual provisioning process is deprecated. Cover: what changes, who does what, exceptions to the automation, and the go-live date."
Prompt 24 — License audit report
"Write a license audit report for our Salesforce account executive. We have 150 licensed users. Findings: 18 users haven't logged in for 90+ days, 7 users have Sales Cloud licenses but only use Service Cloud features (potential downgrade), 4 users have Platform licenses doing Sales Cloud tasks (compliance risk). Recommend license reallocation that saves $24K annually."
Prompt 25 — Security health review
"Write a summary of our annual Salesforce security health review for our CISO. Cover: current security score (we scored 73/100 in Salesforce's Security Health Check), the top 3 failing items and their risk level, our remediation plan and timeline, and the 2 items we've chosen to accept risk on (with business justification). Length: 400 words."
6. Change Management and Process Improvement
Salesforce changes that break rep workflows without warning are how admins lose credibility. These prompts help you manage change before it manages you.
Prompt 26 — Change impact assessment
"Write a change impact assessment for a planned Salesforce process change: [making Industry a required field on Account]. Affected users: all 120 sales reps. Impact: any account without Industry will throw a validation error during save. Assessment should cover: user count affected, workflows that might break, data gaps we need to backfill before go-live, communication needed, and our go-live recommendation (batch backfill first or enforce immediately)."
Prompt 27 — Rollback post-mortem
"Write a post-mortem for a failed Salesforce deployment that required rollback. We deployed a Flow update that caused Opportunity records to be stuck in 'Validation Error' status. Impact: 47 open opportunities were affected for 3 hours on a Friday afternoon during our end-of-quarter push. Document: what happened, root cause, immediate fix, 5 process improvements to prevent recurrence."
Prompt 28 — Admin council proposal
"Write a proposal to create a Salesforce Admin Council — a monthly meeting with power users from each team (Sales, Marketing, Service, Finance) to triage requests, prioritize the roadmap, and communicate upcoming changes. Cover: problem this solves (siloed requests, competing priorities), proposed structure (who attends, agenda format, decision authority), and expected outcome for the first 90 days."
Prompt 29 — Feature request triage document
"Write a feature request triage template for our Salesforce backlog. Each request should be documented with: the request (in user story format), the business problem it solves, who's asking and their priority level, estimated effort (T-shirt sizing), dependencies on other work, and the admin's recommendation (build, buy, defer, decline). Include a scoring rubric for prioritization."
Prompt 30 — Roadmap communication
"Write a Salesforce roadmap communication for our sales leadership team covering the next 2 quarters. Q2 priorities: (1) Opportunity scoring model, (2) LinkedIn integration, (3) SPM module pilot for 10 reps. Q3 priorities: (1) Revenue Intelligence rollout, (2) Territory realignment support, (3) CPQ evaluation kickoff. For each initiative: what problem it solves, who benefits, and what we need from leadership to deliver."
7. Vendor and Contract Communication
Admins often negotiate and manage Salesforce account relationships with less support than they need. These prompts help.
Prompt 31 — Renewal negotiation prep
"Write a memo preparing me for our Salesforce renewal negotiation. Our current contract: $340K/year, 150 Sales Cloud licenses. We're at 78% utilization. Leverage points I have: competitor pricing from HubSpot (28% lower for comparable seats), 3 years as a customer, and we're being asked to expand to Service Cloud which would increase ACV. Write the top 5 asks I should make and my BATNA for each."
Prompt 32 — Support escalation email
"Write a formal support escalation email to our Salesforce account executive. We've had a critical integration bug open for 14 days with no resolution (case #[number]). The bug is causing 40% of our Salesforce-to-ERP sync operations to fail. Business impact: $180K in orders processed manually per day. Tone: firm, professional, specific about escalation timeline."
Prompt 33 — ISV evaluation document
"Write an evaluation document for three Salesforce AppExchange ISV solutions for [CPQ functionality]: Salesforce CPQ (native), DealHub, and Conga. Evaluation criteria: implementation timeline, total cost of ownership over 3 years, complexity for our use case (subscription products with usage tiers), admin overhead post-implementation, and vendor stability. Format as a structured comparison with a recommendation."
Prompt 34 — Implementation partner RFP
"Write an RFP for a Salesforce implementation partner for our [Service Cloud] deployment. Include: scope (4,000 agent licenses, omni-channel routing, Einstein Bot for tier-1 deflection), timeline (8 months to go-live), our current org complexity (17 custom objects, 4 existing integrations), and the 8 evaluation criteria we'll use. We're requesting proposals from 3 partners."
Prompt 35 — Executive briefing on platform update
"Write an executive briefing for our VP of Technology on Salesforce's Spring '26 release. Filter the release notes to 5 items most relevant to our org: (1) Enhanced Einstein Copilot GA, (2) Flow changes affecting our automation library, (3) Security update requiring MFA for all API users, (4) Deprecated features we're using (list them), (5) The one beta feature we should watch. Keep it to one page."
The 5 Prompts Worth Starting With Today
If you're going to pick five prompts and build a habit before trying the rest:
- Flow documentation (Prompt 1) — document one undocumented flow before you touch it next time
- Feature announcement email (Prompt 7) — your next deployment goes out with a real announcement, not a Chatter post
- Dashboard interpretation memo (Prompt 11) — stop letting executives misread reporting and blame you for it
- Change impact assessment (Prompt 26) — make this standard before every validation rule or required field you add
- Rollback post-mortem (Prompt 27) — turn every deployment failure into an org that deploys better next time
Salesforce admins are the connective tissue of their organizations. The best ones communicate like executives, document like engineers, and train like teachers. These prompts give you the scaffolding—you bring the org knowledge.
Want the complete Salesforce Admin prompt pack with 100+ prompts covering SOQL documentation, security audits, and full release management workflows? Find it at gumroad.com/PENDING_SF_ADMIN.
Top comments (0)