FAQ widget, built into your website
Add common questions directly inside the Flidu visitor-facing widget. Show a clean FAQ button, let visitors open questions, manage answers from the dashboard, and place FAQ beside Contact Form, WhatsApp, Resources, Business Hours, Offers, Book Appointment, and Ask AI.
What is Flidu’s FAQ website widget?
FAQ is a Website Widgets channel, included from Starter. It appears inside the visitor-facing widget as a row, and opens a list of common questions and answers without leaving the page. Owners manage the questions from the dashboard. FAQ can run on its own, in a Contact-only widget, or beside Ask AI in a Contact + Ask AI widget experience — useful when visitors need quick, predictable answers before choosing a next action.
How the FAQ button appears on your website
Visitors open FAQ from the channel list, scroll the question list, and tap a question to open its answer in place — all without leaving the page. Long lists stay scrollable inside the widget, and the layout stays comfortable on mobile.
Manage FAQ questions from the dashboard
Every question and answer lives in the dashboard. Add, edit, reorder, and enable or hide questions, then preview exactly how the FAQ appears in the widget.
Add question-and-answer content without rebuilding the page
FAQ answers are controlled in the dashboard. Plain, concise answers work best — keep them page-relevant and practical. It’s a focused question-and-answer editor, not a rich document tool.
Place FAQ beside your other widget channels
FAQ is part of Website Widgets, so you control where it sits in the channel order. Put it before Contact Form to answer common questions first, near Business Hours for availability questions, or beside Ask AI in a Contact + Ask AI widget.
Use more than one FAQ in the same widget
A basic FAQ button points to one generic list. On Website Widgets Business and above, one Flidu widget can offer different FAQ groups for different visitor intents — each with its own title, question list, and answers.
Use different FAQ experiences on different pages
One website doesn’t need one generic FAQ everywhere. Each widget has its own FAQ questions and surrounding actions, so each page can answer what its visitors actually ask. Page Targeting starts on Website Widgets Pro.
Example URLs: example.com/pricing · courses.example/course-name · clinic.example/service-name · property.example/listing-204
FAQ beside Contact Form, WhatsApp, Resources, and Ask AI
FAQ works best as part of the visitor journey, not buried in the footer. Visitors can open FAQ for quick answers, use Ask AI for source-aware answers, send a structured request with Contact Form, message on WhatsApp, check Business Hours, or open Resources and Offers — in the channel order you set.
Ask AI can answer first, while FAQ stays close by
Ask AI belongs to AI Chatbot and FAQ belongs to Website Widgets, but both can appear inside one visitor-facing widget experience. Ask AI answers open-ended questions from configured sources; FAQ gives visitors a predictable list of owner-approved answers to browse.
FAQ content is configured by the owner. Ask AI does not write, edit, or import FAQ answers, and it answers only from the sources it has indexed. The two sit on separate tabs of the same widget and simply work side by side.
FAQ settings owners can configure
See how often visitors open your FAQ
From Website Widgets Starter, Analytics counts how often visitors open the FAQ channel. Pro adds a Top Pages list, and Business adds a filter for a single channel. Analytics and Data Hub stay product-line specific.
Figures shown here are illustrative. Flidu reports aggregate counts, does not show visitor identity, and does not record which individual question was opened.
More than a basic FAQ section for your website
A page-based FAQ sits in one place and waits to be found. The FAQ channel lives inside the widget, right where visitors are deciding what to do next.
Practical FAQ widget setups
Each setup pairs an FAQ instance with example questions, neighboring channels, and what the owner can see in Analytics.