Skip to content
AskVault Docs
Try Free →

The FAQ Builder

Written by , Founder, AskVault · Reviewed by Aashiq
Last updated: · 4 min read

Why a public FAQ matters

Three reasons most teams ship one:

  1. SEO. FAQ pages rank for question-style queries. Google's AI Overview cites schema.org-marked FAQs.
  2. Self-service. Visitors who prefer reading over chatting find answers without engaging the widget.
  3. Trust signal. A populated FAQ tells visitors you've thought about the common questions.

About 20 to 40% of visitors prefer FAQ pages over chat for known-question lookups.

How AskVault's FAQ Builder differs

Two patterns most platforms get wrong:

  • Static FAQ in a CMS. Manually written, often outdated, not connected to support data.
  • AskVault's FAQ Builder. Sources from your indexed knowledge, suggests questions from real visitor conversations, schema.org-marked for SEO, updates as your knowledge changes.

Result: a FAQ that compounds value as your conversation data grows.

Three ways to add a FAQ entry

Method 1: manual.

  1. Open Dashboard > FAQ Builder > Add Q&A.
  2. Type the question as a visitor would ask.
  3. Type the answer (Markdown supported, up to 2,000 characters).
  4. Optionally pick a category (Pricing, Setup, Troubleshooting, etc.).
  5. Save.

Method 2: auto-suggest from conversations.

  1. Open FAQ Builder > Suggestions.
  2. AskVault lists frequently-asked questions from real visitor conversations.
  3. For each, the bot's typical answer is pre-filled.
  4. Review, edit, accept or dismiss.

Auto-suggestions surface about 80% of high-volume questions you should answer.

Method 3: import from knowledge sources.

  1. Open FAQ Builder > Import.
  2. Pick a Q&A pairs source from Knowledge Hub.
  3. AskVault imports them as draft FAQ entries.
  4. Review and publish.

Useful when you already have structured Q&A pairs.

Publishing the FAQ page

Once entries are ready:

  1. Open FAQ Builder > Publish Settings.
  2. Set the URL. Default /c/{slug}/faq; custom domain supported.
  3. Pick the theme. Inherits from your workspace branding.
  4. Optionally set audience scope. Public, paid_users, internal.
  5. Click Publish.

Page goes live within 30 seconds. SEO indexing typically within 24 hours of submission.

What the page looks like

Default layout:

  • Header with your logo and accent color.
  • Search bar at the top.
  • Categorized questions with expandable answers.
  • Footer with a "Still have questions? Chat with us" link.

Mobile-responsive. Loads in under 1 second on a typical connection.

SEO-friendly schema markup

Every published FAQ page carries FAQPage schema.org JSON-LD:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your refund policy?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer a 14-day refund window..."
      }
    }
  ]
}

Google parses this and may display the FAQ as rich snippets in search results. Estimated CTR lift: 10 to 25% over plain results.

Auto-suggestion from real conversations

The FAQ Builder analyzes the last 30 days of conversations and surfaces:

  • Most-asked questions that bot answered (high-frequency, high-resolution).
  • Most-asked unanswered questions that bot escalated (high-frequency, low-resolution; these are gaps to fill).
  • Patterns that vary across channels (questions hot on WhatsApp but not widget).

Click any suggestion to convert it to an FAQ entry.

Categories and organization

Group entries for browsability:

  • Pricing.
  • Setup and onboarding.
  • Features.
  • Account and billing.
  • Troubleshooting.
  • Integrations.
  • Security.

Categories show as expandable sections on the published page. Order is configurable.

Search behavior

Visitors can search the FAQ:

  • Full-text matching across questions and answers.
  • Fuzzy matching for typos.
  • "Did you mean..." suggestions.
  • No-result fallback: "We couldn't find an exact match. Want to ask our chat assistant?" with a deep-link to the widget.

About 60 to 75% of FAQ visitors find their answer via search.

Audience scoping

FAQ entries can be audience-restricted:

  • public. Default. Visible to everyone.
  • paid_users. Visible only to authenticated paying customers (via identity verification).
  • internal. Visible only to verified employees.

Useful when some FAQs are for staff only (e.g., HR policies on a workspace's internal FAQ).

See audience tags.

Embedding on your site

Beyond the standalone FAQ page, embed entries elsewhere:

Inline embed. Drop a snippet on your marketing site:

<div data-askvault-faq data-workspace="ws_xxxx" data-category="pricing"></div>
<script src="https://cdn.askvault.co/widget.js" async></script>

Renders the FAQ entries directly on your page.

Single Q&A. Embed one Q&A inline within a blog post or marketing copy:

<div data-askvault-faq-item data-id="faq_xxx"></div>

Useful for in-context answers within a longer page.

Analytics

Per FAQ entry:

  • Page views for the FAQ page total.
  • Per-question views.
  • Click-through to widget (visitor still wanted to chat after reading).
  • Search-no-result-rate. What visitors searched for but didn't find.

The search-no-result-rate is gold for finding knowledge gaps. Average around 5 to 15% across well-maintained FAQs.

Sync with knowledge base

FAQ entries pull from the same knowledge index:

  • Edit a knowledge source. FAQ entries built from it stay in sync.
  • Delete a knowledge source. Linked FAQ entries flag as "Orphaned" for review.
  • New knowledge added. Auto-suggestions surface new candidate FAQs.

Manual FAQ entries are independent and don't auto-sync.

API access

For programmatic FAQ management:

Terminal window
curl -X POST https://api.askvault.co/v1/faq \
  -H "Authorization: Bearer ak_xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "question": "What is your refund policy?",
    "answer": "We offer a 14-day refund window...",
    "category": "billing",
    "audience": "public"
  }'

Useful for syncing FAQs from external CMS or version-controlling in git.

Plan availability

  • Free. No FAQ Builder.
  • Starter. Up to 25 FAQ entries. Starter+
  • Growth. Up to 100 entries, schema.org markup, custom domain. Growth+
  • Business. Up to 500 entries, multi-language, audience scoping. Business+
  • Enterprise. Unlimited entries.

Sample workflow

End-to-end:

  1. Sign up; index your site.
  2. Bot answers visitor questions for 7 days.
  3. Open FAQ Builder > Suggestions. AskVault surfaces 20 high-frequency questions.
  4. Review, edit, publish 15.
  5. Set up custom domain faq.yoursite.co (optional).
  6. Publish.
  7. Submit sitemap to Google. FAQ entries index within 24 hours.
  8. Track analytics. Refine entries with no-result-search-rate as guide.

Most teams add 5 to 10 new FAQs per month as patterns emerge.

Planned features (on the roadmap)

Documented for accuracy:

  • Multi-language FAQ. Today, single-language per workspace. Native multi-language with auto-translation planned.
  • Visitor-suggested questions. Today, AskVault auto-suggests. Visitor-facing "Suggest a question" form planned.
  • A/B testing FAQ answers. Today, single version per question. A/B variant testing planned.
  • Voice-readable FAQ. Today, text. Voice-channel-compatible audio version planned.

Limits

  • Entries per workspace. Plan-dependent (25 to 500, unlimited Enterprise).
  • Answer length. 2,000 characters.
  • Categories per workspace. 30.
  • Schema.org rich snippet eligibility. Up to 10 entries shown by Google per query.

Common pitfalls

FAQ entries don't appear in Google. Page not crawled yet, or sitemap not submitted. Verify in Google Search Console.

Schema.org markup invalid. Markdown in answer breaking JSON-LD. Use plain text in answers; Markdown rendered separately for visitors.

Audience-restricted entries leaking. Audience routing not enabled. Check Workspace Settings > Audience Routing.

Suggestions don't surface. Not enough conversations yet (need 30 days of data). Or all common questions already answered.

FAQ

Can I have multiple FAQ pages per workspace?

Today, one per workspace. Multi-FAQ (per-product or per-region) planned.

Does the FAQ Builder count against my query quota?

Reading FAQ entries doesn't. Auto-suggestion runs in the background and doesn't impact your quota.

Can I export my FAQs?

Yes. FAQ Builder > Export for CSV or JSON.

Will the bot reference FAQ entries when answering chat questions?

Yes. FAQ entries are part of the same knowledge index. Bot retrieves them like any other source.

Can I disable schema.org markup?

Yes under Publish Settings > Advanced. Not recommended; you lose the SEO benefit.

Was this page helpful?