PromptlyPromptly
Sign inStart free trial
Features · FAQ

Your customers write your FAQ.
Every day.

Every question your bot receives is collected, grouped by meaning, and ranked by how often it comes up. The result is a living FAQ served over a simple REST API — one your website can render and never maintain. Try it below.

Public FAQ API · demo-shop
GET/api/public/faq/demo-shop?mode=general&sort=frequency
How do I return an item?47 asks
Do you ship internationally?38 asks
Where is my order?31 asks
What payment methods do you accept?24 asks
Do you offer discount codes?19 asks
Is the collagen powder vegan?14 asks
How long does delivery take?12 asks
Can I change my order after checkout?9 asks
Do products have a warranty?7 asks
How do I contact support?5 asks
01 · Mining

Where the questions
come from.

No forms, no surveys, no guessing. The FAQ is mined from conversations your bot is already having — automatically, every hour.

  1. 1
    Collect
    The opening question of every conversation is captured and cleaned. Greetings, typos-only messages, and noise are filtered out.
  2. 2
    Group
    Questions are embedded with a multilingual model and clustered by meaning. Paraphrases, typos, and different languages of the same question end up together.
  3. 3
    Split
    Groups the bot answers well become your public FAQ. Groups it couldn't answer become gaps — a ranked list of what your knowledge base is missing.
  4. 4
    Serve
    The finished FAQ is available the moment mining completes — in your dashboard and over the public API, ranked by how often each question is asked.
02 · Gaps

The bot tells you
what it doesn't know.

  • A ranked to-do list
    Gaps are sorted by frequency, so you always fix the answer customers hit most. No more guessing what to document next.
  • One click to fixed
    Add to Knowledge Base opens a pre-filled article draft. Write the answer, hit save — the next mining pass marks the group as answered.
  • Archive the noise
    Nonsense questions and one-offs can be archived so the list stays honest. Archived groups never reach your public FAQ.
03 · The API

One endpoint.
Your whole FAQ.

Every tenant gets a read-only, API-key protected endpoint that returns the mined FAQ as JSON — pull the top questions, search by term, or ask a whole question and get back the groups that match.

Request
GET https://api.promptly.chat/api/public/faq/your-slug?q=returns&mode=question
Response
{
  "success": true,
  "data": {
    "items": [
      { "question": "How do I return an item?", "frequency": 47, "relevance": 0.95 },
      { "question": "Can I return a used item?", "frequency": 12, "relevance": 0.88 }
    ],
    "page": 1,
    "totalCount": 2
  }
}
  • Three modes
    Pull the top questions, filter by a term, or pass a whole question — the API finds semantically matching groups, not just keyword hits.
  • Relevance-ranked
    Search results carry a relevance score and only groups that actually match are returned. A term you have no questions about returns empty, not nonsense.
  • Keyed and rate-limited
    Every request carries your API key. Per-IP rate limits are on by default, and the endpoint is read-only.
  • Privacy floor
    Only questions asked by multiple visitors surface publicly by default, so one customer's oddly specific question never becomes your FAQ.
Last thing

Ship a chatbot your customers will thank you for.

Try it free for 14 days. No credit card. Cancel any time you stop seeing your support queue shrink.

Start your 14-day trial