Instant Answers
Visitors search or browse your FAQ library and get answers in seconds — no queue, no wait, no agent needed.
The FAQ module surfaces searchable, categorised answers to common questions directly inside your chat widget. Visitors find what they need instantly — no agent required. Deflect up to 60% of routine enquiries and free your team to handle the conversations that truly need a human touch.
The FAQ module is a self-service workflow node that presents a searchable library of frequently asked questions directly inside the IMSupporting chat widget. Instead of waiting for a live agent to answer a question that has already been documented, visitors can browse categorised topics, type a keyword to search, and read the answer in seconds — all without leaving the chat window.
Support teams that deploy the FAQ module typically see a 30–60% reduction in repetitive ticket volume. That means fewer interruptions for agents, shorter queues during peak hours, and a better experience for visitors who prefer finding answers on their own. The module pulls content from your knowledge base, so every article you publish is immediately available inside the chat widget — no duplication required.
Because the FAQ module is a standard workflow node, you can place it anywhere in your conversation flow. Use it as the very first step so visitors can self-serve before speaking to anyone, or position it after an AI handoff as a secondary layer of support. Combined with a Button Group node, you can let visitors choose between browsing the FAQ or jumping straight to a live agent — giving them control over their own experience.
Visitors search or browse your FAQ library and get answers in seconds — no queue, no wait, no agent needed.
Resolve routine questions automatically and reduce your support ticket volume by 30–60%, freeing agents for complex issues.
Articles from your existing knowledge base appear inside the chat widget automatically — publish once, serve everywhere.
Empower visitors to help themselves 24/7, even outside business hours when no agents are online.
The FAQ module is most powerful when it sits at the front of your support workflow, acting as a first line of defence against repetitive questions. A typical pattern is: greet the visitor with a Message node, present a Button Group asking whether they'd like to check the FAQ or speak to someone, and then route the "Check FAQ" branch through the FAQ module. If the visitor finds their answer, the workflow ends with a satisfaction prompt. If they don't, it seamlessly escalates to a live agent — carrying the full conversation context.
This layered approach creates a natural support funnel. The easiest questions are resolved instantly by the FAQ. Slightly harder questions might be handled by an AI agent. Only the most complex or sensitive issues reach your human team. The result is a dramatically more efficient support operation without sacrificing the quality visitors expect.
A software company uses the FAQ module to let customers self-serve before escalating to live agents.
A well-maintained FAQ module can be the single highest-impact node in your entire workflow. Follow these guidelines to maximise deflection rates and visitor satisfaction.
Each article should answer one specific question in two to three short paragraphs. Visitors scanning inside a chat widget need quick, scannable answers — save the deep dives for your full help centre.
Group articles into clear categories like "Billing", "Getting Started", and "Troubleshooting". Logical grouping helps visitors browse without searching and reduces the cognitive load of finding the right answer.
Review your FAQ analytics monthly. Remove outdated articles, refresh answers that reference old features, and add new entries for questions that agents keep answering manually. Stale content erodes visitor trust.
No FAQ covers everything. Always provide a clear path to a live agent after the FAQ step. Visitors who feel trapped in a self-service loop will leave your site — a simple "Talk to a person" button prevents that.
There is no fixed limit on the number of articles you can add to the FAQ module. You can create as many categories and articles as your support content requires. That said, we recommend keeping the in-widget FAQ focused on the 30–50 most common questions. Larger knowledge bases work best when paired with a strong search function, which the module includes by default.
Yes. The FAQ module includes a built-in keyword search field at the top of the article list. Visitors can type a word or phrase and the module instantly filters matching articles. Search matches against both article titles and body content, so visitors find relevant results even if they don't know the exact title of the article they need.
Absolutely. The FAQ module and the AI handoff node complement each other perfectly. A common pattern is to offer the FAQ first for structured, documented answers, then fall back to the AI agent for open-ended questions that aren't covered by your articles. This creates a layered support strategy where each tier handles the questions it's best suited for.
Yes. The IMSupporting dashboard provides analytics for every FAQ article, including view counts, search queries that led to the article, and whether the visitor continued to a live agent afterwards. Use these insights to identify your highest-traffic articles, spot gaps in coverage where visitors frequently escalate, and prioritise content updates where they'll have the biggest impact.
The FAQ module works best alongside these workflow nodes to build a complete, layered support experience.
Build your FAQ module in minutes — drag it into your workflow, connect your knowledge base, and start resolving questions automatically. No code required.