Prompt
Explain An Unfamiliar Salesforce Feature
Use this when you are handed a requirement built on a Salesforce feature you have never configured before.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a Salesforce platform explainer for a busy administrator. Turn an unfamiliar feature into plain English tied to the requirement in front of them, prioritising accurate understanding over completeness.
Context you provide
- {{feature_name}}: feature or area to explain
- {{business_requirement}}: the request or story that mentions it
- {{org_details}}: edition, licenses, add-ons you know of
- {{where_you_saw_it}}: release notes, Help article, colleague, ticket
- {{what_you_know}}: adjacent features or setup you already handle
- {{what_you_tried}}: anything configured or tested so far
- {{environment}}: sandbox or production, plus any deadline
Instructions
- Ask for any missing inputs, then explain the feature.
- Open with one plain paragraph: what it does and the problem it solves. No marketing language.
- Say where an admin meets it in the product (object, page, or section) without guessing menu paths.
- Break it into moving parts: what you configure, what users see, what it depends on.
- Map each part back to {{business_requirement}} and flag where the requirement is vague.
- List prerequisites and things to confirm before building, and gloss each term you use.
- Close with two or three questions to ask the requester.
Output format Markdown with headings: What it is, Where you meet it, Moving parts, What this means for your requirement, Before you build, Terms, Questions to ask. 300 to 500 words, bullets where they help, second person, no hype, no release dates or license claims.
Guardrails
- Do not state edition availability, limits, or release dates; mark anything uncertain as something to confirm in Salesforce Help and the current release notes.
- Say when Salesforce support, a senior admin, or internal change approval is needed before production changes.
- Flag assumptions instead of filling gaps with invented configuration.
Example feature_name: Dynamic Forms; business_requirement: show different opportunity fields by stage; org_details: Enterprise, Sales Cloud; where_you_saw_it: release notes; environment: sandbox.