Product

Concierge FAQ

The fastest way to turn your existing documentation into a public Q&A surface customers actually use — every question its own indexable page, every unanswered one a tracked ticket.

Or build it custom →
Surfaces
Web · Mobile · Voice · Multi-channel
LLM
Provider-agnostic via gateway
Ownership
You own the infrastructure
help.yoursite.com — published FAQ pages
Search the help center…
How do I return an item?
Where is my order?
How do I change my address?
3 new unanswered questions → tickets created
Illustrative interface — every deployment is styled to your brand and connected to your systems.

What you get

Two surfaces from one setup. A set of public FAQ pages — one URL per question, server-rendered with structured data, indexed by Google, owned by you. And a chat widget on every page of your site that answers anything not in the FAQ list, with citations, and creates a ticket when it can't help.

What makes it different

Most companies write their FAQ by guessing what to write. Concierge FAQ reads your existing documentation, support history, and product content, then proposes the question list itself — clustered, named, ranked by how often customers actually ask. Your team approves the list before anything goes live. The result is an FAQ grounded in what customers actually ask, not what we guess they ask.

What it can do for you

Deflect the well-understood support volume so your team can spend its time on cases that need judgment. Improve SEO — every approved Q&A is a real page with structured FAQPage markup. Capture the questions you don't have answers for as tickets routed to the right team. Stay current — when your underlying documentation changes, the FAQ refreshes.

  • Auto-generated question list from your real content
  • One indexable page per question, with structured data
  • Embeddable chat widget for the long-tail questions
  • Tickets created automatically when nothing answers
  • Tone matches your brand, not a generic chatbot voice
  • Multi-language — same approach, native tone per language
  • Confidence thresholds you set; refusals you write
  • Connects to existing help-center platforms or stands alone

When it makes sense

You have a real documentation corpus (a help center, internal wiki, product docs) and customer support volume that mostly repeats. You want to reduce that volume without trading off brand voice. You don't want to write the FAQ from scratch, and you don't want a generic chatbot widget that hallucinates.

How we ship it

Typical first deployment is 2–3 weeks. We connect your content sources, run capability inference, your team reviews the proposed question list, we ship the public pages + the widget, you watch the deflection rate. The whole thing runs on the same platform as Concierge — graduate to the full Concierge when you want more than FAQ scope.

Behind the scenes

Concierge FAQ is a scoped configuration of the Embedded Agents service: Knowledge Base + Retrieval Pipelines + Capability Inference + a narrow Agent Runtime + Outcome Routing. Same Foundations, smaller surface, faster to ship.

Questions people actually ask

Do we have to write the FAQ ourselves?

No — that's the point. Concierge FAQ reads your existing documentation, support history, and product content, then proposes the question list itself, ranked by how often customers actually ask. Your team reviews and approves that list before a single page goes live.

What happens when a customer asks something that isn't in the FAQ?

The chat widget tries to answer it from your broader documentation, with citations. If it can't answer confidently, it doesn't improvise — it creates a ticket routed to the right team, and that unanswered question is tracked so you know what to document next.

What do we need to have in place before starting?

A real documentation corpus — a help center, wiki, or product docs — and repeating support volume. A typical first deployment is 2 to 3 weeks: we connect your content sources, your team reviews the proposed question list, we ship the public pages and the widget, and you watch the deflection rate. It connects to existing help-center platforms or stands alone.

The pages it generates — who owns them, and what if we want more than an FAQ?

The pages live on your domain, indexed by Google, and they're yours. Concierge FAQ runs on the same platform as the full Concierge, so when you want a wider scope — actions, account lookups, voice — you graduate to Concierge without rebuilding what's already live.

Frequently paired with

Related products