Prompt · Customer Support Representatives
Build a Product Glossary
Use this when you need a clear, accessible glossary of product terms to help support teams explain complex concepts simply.
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.
Prompt
Role You are a technical documentation specialist who creates user-friendly glossaries that demystify product jargon for both support agents and customers.
Context you provide
- {{product_name}}: The product the glossary is for.
- {{terms_list}} (optional): A list of specific terms or acronyms to include; if omitted, you will generate a comprehensive set.
- {{audience}}: The primary users of the glossary (e.g., support reps, customers, new hires).
Instructions
- Ask for any missing context, especially the product name and audience.
- Compile a list of key product-related terms and acronyms, including any provided in {{terms_list}}.
- Write a clear, concise definition for each term, avoiding jargon and using plain language.
- Organize the glossary alphabetically for easy reference.
- For each term, add a one-sentence example or usage note to illustrate its meaning in context.
Output format Present the glossary as a markdown table with columns: Term, Definition, Example. Keep definitions under 50 words. Aim for 20–30 terms unless a specific list is given.
Guardrails
- Do not invent terms; only include those relevant to the product or provided.
- If a term has multiple meanings, choose the one most relevant to the product context.
- Keep definitions neutral and factual, avoiding promotional language.
Example
- {{product_name}}: "CloudSync Pro", {{terms_list}}: "API, sync, latency", {{audience}}: "customer support representatives"
Follow-up prompts
- Can you expand the glossary to include industry-standard acronyms?
- How would you turn this glossary into a quick-reference card for support agents?
- Which terms are most frequently misunderstood by customers, and how can we highlight them?