Customer Support Knowledge Base Build
Budget: $30 – $250 USD
I need a clean, well-structured knowledge base that my support team – and eventually customers through our chatbot – can rely on for quick, authoritative answers. Everything must be distilled from three existing sources: our company manuals, the public-facing product FAQs, and a sizeable archive of past support tickets.
Here’s what I’m after:
• A single, master document (Google Docs or Markdown) that pulls the most relevant information out of those sources, updates any outdated wording, and removes duplicates.
• The content should be discoverable three ways at once: grouped by topic for browsability, re-framed as concise FAQs for self-service search, and laid out as step-by-step troubleshooting flows for agents who need scripts.
• Please weave in short, consistent summaries and tags so I can later import the file directly into our help-center wiki and feed it into the AI chatbot for intent matching.
I’ll consider the job complete when:
1. Every major product area is covered with at least one topic section, an FAQ set, and a clear problem-solving sequence.
2. Internal links and anchors work, and search in the draft returns logical results.
3. A quick demo import into our test chatbot returns relevant answers without hallucinations.
If you already work with tools like Notion, Confluence, Zendesk Guide, or Trainual, feel free to suggest the best export format.
Here’s what I’m after:
• A single, master document (Google Docs or Markdown) that pulls the most relevant information out of those sources, updates any outdated wording, and removes duplicates.
• The content should be discoverable three ways at once: grouped by topic for browsability, re-framed as concise FAQs for self-service search, and laid out as step-by-step troubleshooting flows for agents who need scripts.
• Please weave in short, consistent summaries and tags so I can later import the file directly into our help-center wiki and feed it into the AI chatbot for intent matching.
I’ll consider the job complete when:
1. Every major product area is covered with at least one topic section, an FAQ set, and a clear problem-solving sequence.
2. Internal links and anchors work, and search in the draft returns logical results.
3. A quick demo import into our test chatbot returns relevant answers without hallucinations.
If you already work with tools like Notion, Confluence, Zendesk Guide, or Trainual, feel free to suggest the best export format.