Customer support · Website

Build your own wiki and knowledge base website

A public wiki for your product or community: pages arranged in a tree, linked to each other, searchable, and edited by your team with every change kept, on your own address.

What it does

Made for help desks, call centres and customer success teams

Sidebar page tree

Sections and sub-pages in a sidebar, such as getting started, guides and reference, so readers always know where they are.

Cross-links between pages

Link one page to another by its title; renamed pages keep their links working, so the wiki does not fill with dead ends.

Team editing

Your team signs in to write and edit pages in the browser, with headings, tables, code blocks and images.

Page history

Every edit is kept with who made it and when; open an old version and restore it if a change went wrong.

Search

A search box on every page that looks through titles and text, with the matching section highlighted.

Own domain

The wiki runs on your own address, such as docs.yourcompany.com, with HTTPS, and pages are readable on phones.

Screens you get

Every person sees what they need

Reader

  • Home
  • Page
  • Search results

Editor

  • Edit page
  • New page
  • Page history
  • Move page

The data it keeps

Everything in one place

  • Pages
  • Sections
  • Page versions
  • Links
  • Editors
  • Images

Deployflix writes this into a one-page plan with the screens and the cost before anything is built. Change anything in the plan, then approve it.

More for customer support

Other apps for help desks, call centres and customer success teams

Call centre agent scheduling app

Build agent scheduling software for your call center: shift templates, half-hour staffing needs, staggered breaks, leave and shift swaps, by skill and language.

Help desk and ticketing SaaS

Build a ticketing SaaS other companies sign up for: a workspace per customer, agent seats, ticket queues, SLA policies and plans paid online.

Call center SaaS

Build a call center SaaS for client companies: calling campaigns, contact lists, agent call screens with scripts, dispositions, callbacks and per-seat plans.

Customer success CRM

Build a customer success and retention CRM: account health, onboarding checklists, renewal dates, check-in notes and churn risks, for every customer account.

Help desk CRM

Build a customer support CRM: one timeline per customer with tickets, calls, notes, orders and products owned, so every agent sees the full story.

Customer support dashboard

Build a support or help desk dashboard: open tickets by age, first reply and resolution times, SLA breaches, backlog and agent workload, for customer service.

Questions

About building a wiki and knowledge base website

Can anyone edit the wiki, or only my team?

You choose. Describe who may edit, such as only signed-in maintainers, or readers who suggest edits for approval, and the spec shows it before anything is built.

Can it be private for our staff only?

Yes. Ask for sign-in to read and the wiki becomes an internal one for your team, with the same page tree, history and search.

Can the pages be kept in GitHub?

The wiki’s code goes to your GitHub account. If you want the pages themselves stored as files there, describe it and the spec will say how it is done.

Build your wiki and knowledge base website

Describe it in your words. You’ll see the plan before anything is built.