> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchski-attract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Keep your FAQ in step with what your team tells customers

> Every day Fetchski Engage notes what your team answered customers; each week it finds the questions people keep asking, and drafts the FAQ entries and corrections your site needs.

> [!NOTE]
>
> **Available on request, with Fetchski Engage.** Fetchski sets this workflow up inside Fetchski Engage
> for each organization that wants it. It needs a Fetchski Engage subscription (separate from your
> Attract site). You don't install any code. To have it enabled, contact your Fetchski representative.

## The situation

Your team answers the same questions every week, by text, WhatsApp, web chat, email and phone, and the
website's FAQ falls behind. It's missing the questions people actually ask, and some answers say what
your team stopped saying months ago: an old cancellation window, last year's hours.

## What it does

**1. Notes what your team answered, every day**

Each conversation your team resolved in Fetchski Engage the day before: the customer's question
and the answer a person on your team gave, written down short. Engage's AI agent is never a
source: its replies, and anything it answered before handing over to your team, are left out.
Email addresses and phone numbers are masked before anything reaches the model.

**2. Finds the questions people keep asking**

Once a week, it looks across those notes for the questions asked in two or more conversations,
with your team's latest answer to each.

**3. Reads your FAQ**

Your Attract site's FAQ, drafts included, so nothing already answered or already drafted is
drafted again.

**4. Drafts the new questions**

A repeated question the FAQ doesn't answer becomes a new FAQ entry, worded the way a visitor
would ask it and answered with your team's own words.

**5. Drafts the corrections**

An FAQ answer your team no longer gives (a new price, policy, time or step) is rewritten with what
they say today.

**6. Emails you the report**

Each week, when something was drafted, the people you choose get one email listing each draft,
how often it was asked and why, plus what was left alone. If a week's check fails, they get an
email saying why and what to do.

## What it never does

> [card] Publish
>
> Every new question and correction is a draft in your CMS's **Submitted Drafts**. Your editor
> publishes it, or doesn't.

> [card] Copy a customer's details
>
> No names, emails, phone numbers or order details go into your FAQ.

> [card] Invent an answer
>
> Prices, times and promises come only from what your team actually said.

> [card] Flood your review queue
>
> At most five new questions and five corrections a week.

## What you need

* A **Fetchski Engage** subscription, where your team answers customers.
* An **Attract site** for the same organization.
* Your Fetchski representative to enable the workflow. They connect Engage to your site with an API
  key that can write FAQ drafts but never publish, and agree with you who receives the report and
  which day it comes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.