See Flidu Answer,
Guide, And Learn.
Explore how visitors ask questions, get source-aware answers, open Contact actions, and create useful insight for your website — all inside one lightweight Flidu widget shell.
Five parts of the widget experience.
Switch between the four modes in the console above, then read on for each part of the experience.
What a visitor actually experiences.
Visitors ask a website question and see a source-aware answer.
Ask AI answers from your website sources so visitors can ask natural questions about your pages. Suggested Questions help visitors start quickly, and Source Cards make answers easier to understand.
Give visitors a useful contact path beside the answer.
Some visitors want a quick action, not a long search. Website Widgets can show familiar Contact paths inside the same shell.
One widget shell. Two product lines. One visitor experience.
Visitors do not need to understand product-line mechanics. They simply see the experience you configure. Behind the scenes, Contact follows Website Widgets access and Ask AI follows AI Chatbot access.
A Guided Example With Sample Website Data.
This example shows what a setup built on a few public pages looks like: Suggested Questions you write, a source-aware answer, and a Contact action. Create a free account to build the same thing from your own website.
The visitor experience also creates better website insight.
The same questions visitors ask in the widget can become useful website improvement signals — what visitors ask, which questions go unanswered, which source pages are used, and which Contact actions follow Ask AI where included.
See how different websites use the same shell.
From demo to your own widget.
A free account lets you build your own setup: add your website sources for Ask AI, configure Contact actions, and install Flidu on your website.
A demo built from fixed examples, not a live scan.
The demo helps you understand Flidu quickly with fixed example content. It does not read your website or your account, and nothing is created or saved.
Visitors see the widget, not your internal setup.
Public visitors see the widget experience you configure. They do not see billing, plan, workspace, targeting rules, usage limits, source IDs, raw crawl details, or internal setup information.