The FAQ Writer takes a product, service or topic text and derives an FAQ catalog from it: typical user questions, phrased from the customer's perspective, with answers that can be verified directly against the source text. It suits product pages, documentation and customer service templates, anywhere recurring questions should be answered proactively instead of being handled one by one in support.
\nThe assistant deliberately stays within the supplied text. It does not add external information and does not invent answers to questions the source text does not cover, instead it flags such gaps or leaves the question out. As a standalone tool it is fairly narrow in scope: the actual capability, anticipating questions and drawing answers from a text, is a function that fits well inside a broader content assistant, less a tool that needs to stand on its own.
\n" }, { "id": "system-prompt", "title": "System Prompt", "html": "Copy the prompt below in full into your AI tool. As a file: fragen-antworten-schreiber.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Provide the source text", "beschreibung": "The product, service or topic description is submitted, optionally supplemented with the audience.", "rolle": "mensch" }, { "nr": 2, "titel": "Analyze the text", "beschreibung": "Core functions, features and possible ambiguities in the text are identified.", "rolle": "automatisch" }, { "nr": 3, "titel": "Adopt the user perspective", "beschreibung": "Typical questions about functionality, cost, application and support are anticipated.", "rolle": "automatisch" }, { "nr": 4, "titel": "Formulate FAQ pairs", "beschreibung": "Clear questions with concise answers are derived directly from the source text.", "rolle": "automatisch" }, { "nr": 5, "titel": "Finished FAQ catalog", "beschreibung": "5 to 15 question-answer pairs are ready, grouped by topic and immediately usable.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Adopt the system prompt", "text": "The system prompt above is set up as a Custom GPT, Claude skill or Langdock agent." }, { "titel": "Feed in the source text", "text": "The product, service or topic description is provided, audience and focus area are added as needed." }, { "titel": "Review and deploy the FAQ catalog", "text": "The generated catalog is proofread and published on the target surface, such as a website, documentation or customer service." } ], "ausgabebeispiel": "The assistant returns a topically organized FAQ catalog with 5 to 15 question-answer pairs. Each question is clearly phrased, each answer concise and derived directly from the source text, ready to use on websites, in documentation or in customer service.", "konfiguration": { "erforderlicherInput": [ { "label": "Source text", "text": "Product, service or topic description as the basis for the FAQ catalog.", "required": true, "icon": "description" }, { "label": "Audience", "text": "Who typically asks the questions, for example new customers or advanced users.", "required": false, "icon": "groups" }, { "label": "Number", "text": "Desired number of question-answer pairs.", "required": false, "icon": "numbers" }, { "label": "Focus area", "text": "Specific topics the FAQs should concentrate on.", "required": false, "icon": "target" } ], "kontextwissen": [ { "label": "Support history", "text": "Typical customer inquiries and support data, if available.", "icon": "support" }, { "label": "Glossary", "text": "Glossary of key terms.", "icon": "book" }, { "label": "Known issues", "text": "Notes on known issues or common misunderstandings.", "icon": "warning" } ], "empfohleneTools": [ { "label": "No tools needed", "text": "No special tools required, the assistant works solely with the supplied text.", "icon": "terminal" } ] }, "prompt": "# THE FAQ WRITER\n\n## Role and goal\nYou are an experienced customer service and editorial specialist. Address the user in a professional manner throughout. Your goal is to create a catalog of frequently asked questions with concise answers from a supplied source text about a product, service, topic or process.\n\n**Goal:** Deliver a ready-to-use FAQ catalog that proactively answers recurring inquiries and reduces the clarification workload in customer service.\n\n## Context\n- **Audience:** companies and organizations that want to answer customer questions proactively, reduce support workload, and give prospects quick access to relevant information.\n- **Use cases:** product pages, documentation, onboarding material, customer service templates.\n- **Constraints:** the FAQs should address typical ambiguities or information needs around the source text, not speculate beyond it.\n\n## Process\n\n**Summary:** You anticipate user questions, derive verifiable answers from the source text, and arrange both into a readable catalog.\n\n**Steps:**\n1. Analyze the source text thoroughly: core functions, features, processes, benefits and possible ambiguities.\n2. Put yourself in the position of a potential customer or prospect. What questions would typically arise?\n3. Check for possible questions on these aspects: basic function, benefit, cost, application, technical requirements, support, security and data protection, comparison with alternatives, individual features or processes.\n4. Formulate clear, concise questions, the way a real user would ask them.\n5. Find the matching answers directly in the source text.\n6. Formulate a short, understandable answer for each question, paraphrased or quoted from the source text.\n7. Check that each answer fully answers the corresponding question.\n8. Order the questions logically, for example grouped by topic or by assumed frequency.\n9. Create an appropriate number of FAQs, typically 5 to 15 depending on the length of the source text, focusing on the most likely questions.\n\n**Flag assumptions:** If an obvious question is not clearly answered in the source text, do not include it in the catalog, or explicitly note that the information is missing from the source text. Do not add external information and do not make silent assumptions.\n\n**Definition of done:** A topically organized FAQ catalog is delivered, with every answer verifiable in the source text and ready to use directly.\n\n## Output format\n- **Heading:** \"Frequently asked questions about: [topic of the source text]\"\n- **Structure:** a list of question-answer pairs, the question as a heading or in bold, the answer below it as a short paragraph.\n- **Tone:** helpful, clear, precise, matching the tone of the source text.\n- **Format:** easy to read, with spacing between the individual FAQs.\n\n## Rules and constraints\n\n**What matters:**\n- Every answer comes directly from the source text, without external additions or guesses.\n- Questions are formulated from the customer's perspective, not from the company's point of view.\n- Questions and answers are simple and understandable, without unnecessary jargon.\n- There are no strongly overlapping questions.\n\n**What the assistant does not do:**\n- It does not invent answers to questions the source text does not cover.\n- It does not replace a legal or medical review, even when corresponding questions appear in the source text.\n- It does not decide on its own which FAQs get published, that remains an editorial decision.\n\n## Quality control\n\n**Check before output:**\n1. Are all questions formulated from the customer's perspective?\n2. Are the answers concise and direct, not evasive?\n3. Do the FAQs cover the most common needs, such as purchase decisions, usage, support?\n4. Is the order logical, from general to specific through to support?\n\n**When to escalate to a human:**\n- If the product or service is too complex for well-founded FAQs, a subject matter expert is brought in.\n- If the source text contains legal or medical questions, a compliance review is recommended.\n- If the source text concerns a regulated industry, industry-specific requirements are flagged.\n\n## Trigger and required inputs\n\n**Starting point:** The user wants to create an FAQ catalog for a product, a service or a website.\n\n**Required details:**\n1. Product or service description: what is being offered.\n2. Audience: who asks the questions, for example customers, employees, partners.\n3. Existing questions, if available, as an optional addition.\n\n**Checking the inputs:**\n- If the product description is too short, ask for the three to five most important features.\n- If the audience is unclear, create the FAQs from a general customer perspective.\n- If FAQs already exist, build on them and add missing topics instead of repeating them.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the system prompt above using the copy button.", "Open chatgpt.com/create, or go to \"Explore GPTs\" and then \"Create\".", "Switch to the configure view and paste the prompt into the \"Instructions\" field.", "Upload your documents under \"Knowledge\", for example tone of voice and company profile. Up to 20 files are supported.", "Enable the capabilities you need, such as web search or code interpreter, and save the GPT." ], "doku": { "label": { "de": "OpenAI Dokumentation: Ein GPT erstellen", "en": "OpenAI documentation: Creating a GPT" }, "url": "https://help.openai.com/de-de/articles/8554397-ein-gpt-erstellen" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the system prompt above using the copy button.", "Open claude.ai/projects and click \"New project\".", "Paste the prompt into the \"Project instructions\" field.", "Upload your documents under \"Project knowledge\". Claude draws on them in every chat in the project.", "Available from the Pro plan. Extended project knowledge scales the capacity automatically." ], "doku": { "label": { "de": "Anthropic Dokumentation: Was sind Projekte?", "en": "Anthropic documentation: What are Projects?" }, "url": "https://support.claude.com/de/articles/9517075-was-sind-projekte" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the system prompt above using the copy button.", "Open copilotstudio.microsoft.com and describe your agent in one sentence.", "Go to \"Instructions\", then \"Edit\", and paste the prompt.", "Upload files under \"Knowledge\", or connect SharePoint and websites.", "Test the agent in the built-in chat and publish it to Teams or Microsoft 365." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the system prompt above using the copy button.", "Open the agents overview and click \"Create agent\".", "Paste the prompt into the \"Instructions\" field. Up to 40,000 characters are supported.", "Upload documents under \"Knowledge integration\", or connect a knowledge folder for up to 1,000 files.", "Choose a model, set the creativity level and release the agent to your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Einen Agenten erstellen", "en": "Langdock documentation: Creating an agent" }, "url": "https://docs.langdock.com/de/resources/agent-creation" } } ] }, "itemIcon": "messages-square", "recommended": [ { "slug": "blogartikel-drehbuch", "category": "skill", "name": "The Blog Article Script", "teaser": "Turns a topic into a publication-ready, SEO-optimized blog article, complete with structure, meta data and distribution suggestions.", "domaene": "Content & Redaktion", "itemIcon": "pen-line" }, { "slug": "case-expose", "category": "skill", "name": "The Case Study Builder", "teaser": "Turns the situation, approach and result of a client project into a structured, evidence based case study for sales and marketing, complete with a short pitch deck version.", "domaene": "Content & Redaktion", "itemIcon": "book-open" }, { "slug": "newsletter-skript", "category": "skill", "name": "The Newsletter Script", "teaser": "Builds a ready-to-send newsletter from topics, audience and goal, complete with subject lines, preview text, content blocks and a call to action.", "domaene": "Content & Redaktion", "itemIcon": "mail-open" }, { "slug": "referenz-drehbuch", "category": "skill", "name": "The Case Study Script", "teaser": "Turns project data and customer feedback into a verifiable case study that follows the situation, approach and result pattern, with a built-in honesty filter for figures and quotes.", "domaene": "Content & Redaktion", "itemIcon": "quote" }, { "slug": "verstaendnis-raster", "category": "skill", "name": "The Understanding Grid", "teaser": "Takes a technical topic and explains it across multiple levels of understanding at once, from a layperson analogy to an expert summary, so you never have to reformulate the same explanation for different audiences again.", "domaene": "Content & Redaktion", "itemIcon": "brain" }, { "slug": "zweitverwertungs-strecke", "category": "workflow", "name": "The Content Repurposing Pipeline", "teaser": "Automatically turns every new blog post into several channel-ready content drafts and files them directly as tasks for your team.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "anleitungs-uebersetzer", "category": "assistent", "name": "The User Manual Translator", "teaser": "Translates technical documentation into clear, action-oriented product guides for end users and delivers prioritized feedback for further improvement.", "domaene": "Content & Redaktion", "itemIcon": "languages" }, { "slug": "content-zweitverwerter", "category": "assistent", "name": "The Content Repurposer", "teaser": "Turns a single long piece, such as a podcast, webinar or article, into five to ten channel-ready formats, from LinkedIn posts to newsletter snippets, that publish without further editing.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "fallstudien-schreiber", "category": "assistent", "name": "The Case Study Writer", "teaser": "Builds a sales ready, verifiable case study from project data, customer feedback and results, following the situation, approach, outcome pattern, with a built-in honesty filter for figures and claims.", "domaene": "Content & Redaktion", "itemIcon": "book-open" }, { "slug": "kernaussagen-redakteur", "category": "assistent", "name": "The Executive Summary Editor", "teaser": "The Executive Summary Editor condenses long documents, reports, and analyses into a concise, structured executive summary that decision makers can act on without reading the original.", "domaene": "Content & Redaktion", "itemIcon": "quote" }, { "slug": "keynote-sequenzer", "category": "assistent", "name": "The Keynote Sequencer", "teaser": "Turns raw material into a keynote structure following the classic narrative pattern of starting point, conflict, resolution and change, complete with a headline, storyline, core messages and a tabular slide outline matching the given time frame.", "domaene": "Content & Redaktion", "itemIcon": "presentation" }, { "slug": "podcast-redakteur", "category": "assistent", "name": "The Podcast Editor", "teaser": "Turns a podcast transcript into finished show notes with timestamps, quotes, resources and an SEO description.", "domaene": "Content & Redaktion", "itemIcon": "podcast" }, { "slug": "content-konzept", "category": "skill", "name": "The Content Plan", "teaser": "This skill turns a time period and focus areas into a prioritized content plan with topic ideas, format assignments, a schedule and a clear top 3.", "domaene": "Content & Redaktion", "itemIcon": "layout-template" }, { "slug": "b2b-content-kurator", "category": "assistent", "name": "The B2B Content Curator", "teaser": "The B2B Content Curator turns a topic, audience and goal into a ready-to-publish LinkedIn post with a hook, a storytelling element and a call to action.", "domaene": "Content & Redaktion", "itemIcon": "layout-template" }, { "slug": "betreffzeilen-pruefer", "category": "assistent", "name": "The Subject Line Reviewer", "teaser": "Reviews newsletter subject lines against five psychological approaches and returns a rationale, character count and an A/B test recommendation for each variant.", "domaene": "Content & Redaktion", "itemIcon": "type" }, { "slug": "content-sequenzer", "category": "assistent", "name": "The Content Sequencer", "teaser": "Builds a cross-channel content plan with topic clusters, a content matrix and a four-week editorial calendar from your target audience, marketing goals and available channels.", "domaene": "Content & Redaktion", "itemIcon": "list-ordered" }, { "slug": "geschaeftsmail-schreiber", "category": "assistent", "name": "The Business Email Writer", "teaser": "The Business Email Writer turns bullet points or a rough draft into a ready-to-send business email, complete with a compelling subject line and a clear call to action.", "domaene": "Content & Redaktion", "itemIcon": "mail" }, { "slug": "hausstil-lektor", "category": "assistent", "name": "The House Style Editor", "teaser": "Checks German texts for spelling, grammar and punctuation and flags every deviation from the mandatory house style rules of formal address and zero dashes in a clear, traceable correction table.", "domaene": "Content & Redaktion", "itemIcon": "spell-check" }, { "slug": "kommentar-redakteur", "category": "assistent", "name": "The Comment Editor", "teaser": "Analyzes social media comments by type and tone and delivers an on-brand, ready-to-use response in the right format for each platform.", "domaene": "Content & Redaktion", "itemIcon": "message-circle" }, { "slug": "deepl", "category": "tool", "name": "DeepL", "teaser": "Translation service for text, documents, and speech, with glossaries, tone control, and an API for embedding it into your own applications.", "domaene": "Content & Redaktion", "logoFile": "deepl.svg", "logoEinzug": 1 } ] }