Skip to main content

FAQ

Menu path: Admin -> FAQ

This section manages the frequently asked questions shown on the website.

Main pages​

  • FAQ List
  • FAQ Create
  • FAQ Update
  • FAQ Details

What you can do​

  • publish common answers for customers
  • keep draft entries hidden
  • improve support efficiency by answering repeated questions once

FAQ List page​

The list page helps admins manage FAQ items quickly.

From this page, admins can normally:

  • see the question text
  • change publish status
  • open the details page
  • open the edit page
  • delete an FAQ item

FAQ form field guide​

FieldWhat it meansValidation or good input
QuestionThe question users will see on the public FAQ pageRequired. Keep it under 255 characters
StatusWhether the FAQ is public or hiddenPublished shows it on the site. Draft keeps it hidden
AnswerThe answer content shown under the questionRequired

What Published and Draft mean​

  • Published: the FAQ can appear on the public FAQ page
  • Draft: the FAQ stays hidden until you are ready

Use Draft while you are still reviewing the text.

FAQ Details page​

The details page is useful when you want to read one FAQ item in full without opening the edit form.

It helps admins review:

  • the full question
  • the full answer
  • whether the content looks correct before updating it

How FAQ appears on the website​

Published FAQ items are shown in the public FAQ page as accordion-style questions and answers.

That means:

  • the question should be short and clear
  • the answer should be easy to scan
  • very long answers should be broken into readable paragraphs

Good FAQ question examples​

  • How long does exchange processing take?
  • How do I track my order?
  • What documents are required for verification?
  • What should I do if my payment is delayed?

Good FAQ answer style​

Try to write answers that are:

  • short
  • direct
  • easy for new users
  • consistent with your actual business rules

Common mistakes​

  • writing the question too long
  • writing an answer that does not really solve the user problem
  • publishing an FAQ before checking the wording
  • keeping outdated answers after business rules changed
  • using FAQ for information that belongs in Page Settings or Blog

If save fails​

Check these points first:

  • Question is filled
  • Question is under 255 characters
  • Answer is not empty
  • Status is selected correctly

Best practice​

  • write one clear question per item
  • keep the answer simple and direct
  • update old answers when business rules change
  • use FAQ before customers need to open a support ticket
  • keep high-volume support questions in FAQ first
  • review Support Tickets regularly and turn repeated questions into FAQ items