Product · FAQ sections

Write every FAQ once. Show it everywhere.

Keep your FAQs in HelpCenter.io and put them on your pricing page, product pages, checkout, app and partner sites. When an answer changes, you edit it once, and every page that shows it has the new answer.

  • One edit updates every site, page and app that shows the answer
  • Translated, reviewed and measured with the rest of your help center
  • The same answers come up in your help center's search and in the widget
Start free trial Edit an answer yourself

FAQ sections are on every plan. Browse FAQ section templates. Send this to your developer

Pulse help center · FAQ
Published just now
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
Type: FAQ Released in English and Spanish
Marketing site pulserun.app/pricing Updated
Pricing questions
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
Online store shop.pulserun.app/band Updated
Orders and returns
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
In the app app.pulserun.app/billing Updated
Billing questions
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
Partner site striderunning.com/brands/pulse Updated
Pulse at Stride
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
One edit, every page updated
Edited once One FAQ article updates every page that shows it. Translated Each language shows the questions released in it. Reviewed Roles, reviews and version history, like every article. Measured See how many people your sections reach and what they read.
For every kind of business

Where your FAQs belong

Pick your kind of business to see where FAQ sections go, which questions people ask there, and what your developer pastes. It's the same feature on every plan, wherever you put it.

Marketing websites

Answer the questions that hold up a signup right where they come up: under your plans, beside your signup form, on each campaign page. Your marketing team changes an answer in HelpCenter.io instead of in every page of your CMS.

Every plan
Embed FAQ sections on your website Add the widget to your website
What your developer adds
HTML A Custom section 
<!-- Where the questions go -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- Once per page, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Online stores

Put delivery, returns and sizing answers on every product page from your product template, and the same answers in your cart and on your order-status page. Change your returns window once and the whole store agrees.

Every plan
Embed FAQ sections on your website Add the widget to your website
What your developer adds
HTML On every product page 
<!-- In your product page template, so every product shows it -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- In your theme's layout, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

SaaS apps

Show billing questions under your plan picker and setup questions beside each onboarding step, inside the app your customers are signed in to. With the launcher off, the snippet loads only your FAQs, and the same section can sit on your public pricing page too.

Every plan
Embed FAQ sections on your website Widget installation and options Want your whole help center in your app? See the AI Widget
What your developer adds
HTML FAQs without the widget 
<!-- Under your plan picker -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- No launcher: the snippet loads only your FAQ sections -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', widgetEnabled: false };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Mobile apps

If a help, account or checkout screen in your iOS or Android app is a web view, it shows a FAQ section like any web page. Change an answer and the screen is current the next time it opens, with no app release. Native screens can't run the snippet; link those to your help center instead.

Every plan
Embed FAQ sections on your website Widget installation and options
What your developer adds
HTML A page your app opens in a web view 
<!-- The page your app's Subscription screen loads -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', widgetEnabled: false };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Schools and universities

Deadlines, fees and rules change every term. Keep each answer in one place and show it on your admissions site, your student portal and your learning platform, in every language your students read.

Every plan

More than one language on Growth and Catalyst.

Embed FAQ sections on your website Translate an article
What your developer adds
HTML Another language 
<!-- On the Spanish version of the page -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', lang: 'es' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Banks and fintech

An old fee on one page is the kind of mistake customers remember. Keep fees and limits as FAQs, have every change reviewed like any article, and show them all on one page, grouped by category, with a Full section.

Every plan

On Catalyst, staged changes keep a new answer out of sight until you publish it on the day it takes effect.

Embed FAQ sections on your website Staged changes
What your developer adds
HTML Every FAQ, by category 
<!-- Every published FAQ that is in a category -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="full"></div>

<!-- Once per page, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Local services

Booking, membership and opening-hours questions come up all day. Put the answers on your booking and contact pages, and change your holiday hours or your cancellation policy in one place.

Every plan
Embed FAQ sections on your website Add the widget to your website
What your developer adds
HTML A Custom section 
<!-- Where the questions go -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- Once per page, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>

Partners and other brands

A section shows on any site whose host you list, so a reseller, a partner or your other brand shows your answers instead of a copy that goes stale. Agencies keep each client's FAQs in that client's own help center and switch between them from one login.

Every plan
Embed FAQ sections on your website How agencies run a help center per client
What your developer adds
HTML On a partner's site 
<!-- On striderunning.com, which Pulse lists under Display on URLs -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', widgetEnabled: false };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>
Why one source

FAQs are content, not page copy

Most FAQs start life pasted into one page. Then the same question gets pasted into the pricing template, the checkout, the app and a partner's site, and the copies drift apart: one says 30 days, another still says 14. Nobody translates them all, and nobody can tell which ones people read.

In HelpCenter.io each answer is one FAQ article. Every page that needs it shows that article, so there is only ever one answer to keep right.

Changing an answer

Pasted: Find every page, template and screen with a copy, and hope you found them all.

HelpCenter.io: Edit it once. Every section that shows it has the new answer the next time its page loads.

Languages

Pasted: Each copy is translated on its own, or never.

HelpCenter.io: Translated with your help center. Each language shows only the questions released in it.

Who can change it

Pasted: Whoever can edit that CMS page, template or code.

HelpCenter.io: Your roles, reviews and version history, the same as every article.

Knowing what works

Pasted: Nobody knows which questions people read.

HelpCenter.io: Statistics show how many visitors your sections reach and how often each question is viewed.

Everywhere else

Pasted: The answer lives on that one page.

HelpCenter.io: It also comes up in your help center's search, in the widget and in Ask AI (Catalyst, or $29/mo add-on).

Try it

Edit the answer. Every page catches up.

This is one FAQ article in Pulse's help center. Two of Pulse's sites show it in FAQ sections, and readers find it in the help center's search and in the widget. Change the answer and publish it.

Pulse help center · FAQ
FAQ
Question
Can I get a refund?
64 of 600 characters, the most an FAQ answer holds

Pricing page pulserun.app/pricing
Pricing questions
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
Can I pay yearly?
Yes, $79.99 a year, from Subscription in the app.
App screen app.pulserun.app/billing
Billing questions
Can I get a refund?
Yes. Ask within 60 days of your order and we refund you in full.
How do I cancel Premium?
From Subscription in the app. Premium stays on until your paid period ends.
Help center search help.pulserun.app
refund
2 results
Can I get a refund?FAQ
Yes. Ask within 60 days of your order and we refund you in full.
Returns and refunds
The widget, on any page pulserun.app
refund
Can I get a refund? Yes. Ask within 60 days of your order and we refund you in full.
Returns and refunds
  • On your own pages, the new answer shows the next time each page loads. There's nothing to republish.
  • Ask AI answers from the same article when someone asks in their own words. Catalyst, or $29/mo add-on.
How it works

From your help center to any page, in four steps

Owners and Admins build the sections. Anyone who can write articles can write the questions.

  1. 1

    Write FAQ articles

    A short answer of up to 600 characters, in the same editor as your articles, with its Type set to FAQ. Have a long article already? "Derive FAQs from this article" drafts up to three for you to check before they go live.

    FAQs: Every plan AI drafts: Catalyst, or $29/mo add-on
  2. 2

    Group them into a section

    A Custom section holds the questions you pick for one page, in your order. A Full section shows every FAQ that is in a category, grouped by category. One FAQ can be in as many sections as you like.

    Every plan, no cap on sections
  3. 3

    Paste one line where it goes

    Click Install next to the section and copy its div into your page, on a page that has the widget snippet. Don't want the floating widget there? One option turns the launcher off and keeps the FAQs.

    HTML The section 
    <div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>
    Every snippet and option
  4. 4

    Name the sites it may show on

    Under Display on URLs, list the host name of every site that shows the section, separated by commas. It loads only where the host matches exactly, so a copied snippet does nothing on anyone else's site.

    Host names only. A path such as /pricing is ignored: the snippet decides which pages show the section, and this list decides which sites may. www.example.com and example.com are two hosts. Your help center's own pages can always show its sections.

FAQ section templates

Your answers, in a design that fits your site

Choose from 27 FAQ section templates in HelpCenter.io. Set the accent colour, corners, font, and light or dark scheme, then embed your section wherever customers need it.

Need a free FAQ section?

faqs.me is our free alternative for a standalone FAQ section, with the same 27 designs. Create your FAQ and export the code. When you need answers managed in a help center, import your section into HelpCenter.io from the faqs.me editor.

Browse all FAQ templates ↗
Section types

Pick the questions, or show them all

Give a section one of 27 ready-made designs under Design, in your accent colour, corners and font. Or keep it Classic: part of your page, in your fonts and colours. These are the three ways a Classic section can look.

Custom

The questions you pick, in your order, with every answer showing. Show or hide its title and description.

Full: categories on the left, FAQs on the right

Every FAQ that is in a category. Readers pick a category and read its answers.

Full: stacked categories with expandable FAQs

Every category in a box of its own. Readers open the questions they care about.

Inside your help center, too

  • A FAQs block for your home, category and search pages, with your latest FAQs or one Custom section, each question opening in place
  • A FAQ section inside any article, its questions collapsed until opened
  • Each category page opens with its FAQs, and every FAQ has a page of its own

Three designs, Finder, Ledger and Bulletin, put a search box above the questions, and your help center and the widget find your FAQs too. In an article or a FAQs block a section takes your help center's look; its template and Custom CSS are for your own pages.

Languages

Every language you publish, from the same questions

Translate each FAQ in the editor, language by language, and turn on Released when a translation is ready. A section shown in Spanish lists the questions released in Spanish and leaves the rest out, so a half-finished translation never reaches your page.

  • Each section's title and description have a field per language
  • One option in the snippet picks the language each page shows
  • Auto-translate drafts a translation for you to check, on Catalyst
More than one language: Growth and Catalyst Translate an article
Reviewed like content

An FAQ is an article, with everything that comes with one

Roles

Owners and Admins build sections, Editors write FAQs, Translators translate them. Custom roles are on Catalyst. Team members: 1 on Bootstrap, 10 on Growth and no cap on Catalyst.

Reviews

Flag an FAQ for review, assign it, and mark it reviewed once it's checked. When the article an FAQ is attached to changes, the FAQ is marked as needing a look. On every plan.

Version history

See what changed, who changed it and when, and restore an earlier version. On every plan; how far back it goes depends on your plan.

Staged changes

Rework a live answer while readers keep seeing the current one, and publish it when it should take effect. On Catalyst.

Flag an article for review Article version history Staged changes Roles and permissions
Statistics

Know which questions people actually read

Every section counts its visitors and each question's views, wherever it's embedded. Filter Statistics to FAQ sections and you see them on their own, next to the rest of your help center.

  • Each FAQ's views in Content performance, beside your articles
  • A view means the answer was on screen; in the stacked layout and inside articles, that someone opened it
  • Visitor journeys show when a section loaded and which question was opened

Numbers cover all your sections together, not one section or one page. Embedded sections have no "Was this helpful?" vote; FAQs opened in the widget do. Statistics are on every plan, and how far back you can look depends on your plan.

For your developer

Two pieces of HTML, ready to paste

The widget snippet loads your sections, and one div per section says where each goes. No package to install, no build step, and the section key comes from Install in your dashboard.

HTML A Custom section 
<!-- Where the questions go -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- Once per page, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>
HTML Every FAQ, by category 
<!-- Every published FAQ that is in a category -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="full"></div>

<!-- Once per page, before </body> -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>
HTML FAQs without the widget 
<!-- Under your plan picker -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<!-- No launcher: the snippet loads only your FAQ sections -->
<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', widgetEnabled: false };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>
HTML Another language 
<!-- On the Spanish version of the page -->
<div class="hc-faq-section" data-id="YOUR_SECTION_KEY" data-type="custom"></div>

<script>
  window.hcOptions = { app_id: 'YOUR_WIDGET_ID', lang: 'es' };
</script>
<script src="https://helpcenter.io/js/init.js" async></script>
CSS Your own styles 
/* In your own stylesheet: the section is part of your page */
.hc-faq-section .hc-faqs-title { font-size: 28px; }
.hc-faq-section .hc-faqs-article-item-title strong { color: #0B2A46; }
.hc-faq-section .hc-faqs-article-item-content { color: #475569; }

Not the one writing the code?

Send your developer a short email with this page and the two docs they need. It opens in your own mail app; nothing is sent until you press send.

Email this to your developer

Docs

developers.helpcenter.io
  • Loads asynchronously, so it never holds up your page
  • Renders in your page, not in a frame, so your CSS reaches it
  • Looks for sections once, as it loads: put the div in the page's first HTML

Questions about FAQ sections

Which plans include FAQ sections?

Every plan, Bootstrap included, with no cap on sections or questions. Showing FAQs in more than one language needs Growth and Catalyst. Drafting FAQs with AI is included on Catalyst, or a $29 per month add-on on Bootstrap and Growth. Staged changes and custom roles are on Catalyst.

Do I need a developer?

Someone who can edit your site's HTML adds two things: the widget snippet, once per page, and a one-line div where the questions should appear. After that, writing, ordering and translating the questions all happens in your HelpCenter.io dashboard.

Can I show FAQs without the widget's launcher?

Yes. Add widgetEnabled: false to the snippet and it loads your FAQ sections with no floating button.

Our help center is private. Can we still show FAQs on our website?

Yes. A FAQ section shows only published, public FAQs, even when the rest of your help center is private, so your docs can stay behind a login while your website answers questions before people buy.

Will FAQ sections help our pages in search results?

We don't promise that for your own pages: a FAQ section is added to your page by JavaScript as it loads, and it adds no FAQ structured data. Inside your help center, each FAQ is a page of its own and is listed in your help center's sitemap.

Can a section match our site's design?

Yes. Under Design, pick one of 27 ready-made templates and set its accent colour, corners, font and light or dark scheme, previewed live with your own FAQs on a light or dark page, at desktop or phone width. Or keep it Classic: it takes your page's fonts and colours. Either way, Custom CSS fine-tunes it on your own pages.

Does it work in a single-page app?

The snippet looks for FAQ sections once, as it loads, so a section your app adds to the page later won't appear. Put the section's div in the HTML the page starts with.

Can visitors search inside a section?

Yes, in the designs with a search box: Finder, Ledger and Bulletin filter a section's questions and answers as visitors type. Your help center and the widget search your FAQs too.

Give every page the right answer

Start a trial, write your first FAQs, and put them on your own site with one line of HTML.

Start free trial Request a demo
14-day free trial · No credit card required
Help