# Turn repeat Crisp questions into drafted help center articles

> Every Monday, the questions customers asked more than once become drafted help center pages in Notion, but only where you have no article yet.

- Workflow type: agent
- Services: Crisp, Notion
- Categories: Customer Support, Product
- Published: 2026-08-14

## What it does

- Every Monday morning, reviews the past week of live chats on your website and groups them into the questions that keep coming back
- Only treats a topic as a real pattern when at least three separate conversations raise it, so one-off questions never turn into busywork
- Checks your existing help center first and skips anything you have already written, so you only ever see genuine gaps
- Creates one clearly labelled draft page per gap, covering the customer question, a suggested answer, how many chats it came from, and two example chats as evidence

## What you'll need

- A Crisp account with live chat running on your website
- A Notion workspace, with your help center section shared with the connection so new pages can be created there
- Enough weekly chat volume for patterns to show up, roughly a few dozen conversations a week works well
- Someone on the team who reviews and publishes the drafts, since nothing goes live on its own

## Prompt

Every Monday at 8am, review last week's Crisp conversations and turn the questions customers keep asking into drafted help center articles in Notion.

Start with the Crisp List Conversations operation to pull every conversation for my website from the past seven days. For each conversation, read the subject, the last message preview, and the segments, and use those fields to group conversations into recurring themes. Work from what the conversation list gives you rather than assuming you have the full chat transcript.

Only keep a theme when at least three separate conversations hit it. Three is the threshold I want to start with, and it should be easy for me to change that number later. Drop anything that came up only once or twice, since a single question is not a documentation gap.

For each surviving theme, use the Notion Search by Title operation to check whether my help center space already has a page covering it. If a matching page already exists, skip that theme entirely. The point of this step is that I only ever see genuine gaps, never topics I have already documented.

For each remaining gap, create one Notion page with Create a Page, then fill the body using Update Page Content as Markdown. The body should cover the customer question phrased in their own words, a suggested answer, how many conversations the theme came from, and two example conversation subjects as supporting evidence.

Title every page so it is unmistakably a draft awaiting human review, for example "[Draft] How do I reset my password?". Nothing should ever be published automatically. A person reviews each draft, edits it, and decides whether it goes live.

Strip customer names and email addresses out of everything you write. The drafts should describe the question and the answer, never the individual who asked it.

If no theme clears the threshold, or every theme already has a page in the help center, finish the run without creating anything.

## How to customize

- Change how many conversations a topic needs before it counts as a pattern. Three is the starting point, raise it if you get a lot of chat
- Move the run to a different day or time, or switch to fortnightly if your chat volume is lower
- Point the drafts at a different Notion section, or have the agent read full chat transcripts instead of just the opening subject and latest reply

## FAQ

### Will it publish anything to my help center automatically?

No. Every page lands clearly titled as a draft, and a person decides whether to edit, publish, or throw it away. The workflow only ever writes drafts.

### What if we already have an article covering the question?

It searches your existing help center by title before writing anything, and skips any topic that already has a page. You only see the questions your documentation does not answer yet.

### Do customer names or email addresses end up in the drafts?

No. Personal details are stripped out before anything is written. The drafts describe the question and the suggested answer, not the individual who asked.

### How much chat volume do I need for this to be worth running?

Enough that the same question genuinely comes up three times in a week. A few dozen conversations a week is a comfortable starting point. Below that, run it fortnightly or lower the threshold.

### What happens on a quiet week with no clear patterns?

Nothing is created. If no topic reaches the threshold, or every topic already has an article, the run finishes without adding pages so your workspace stays clean.

Use this prompt in General Input: https://www.generalinput.com/prompts/turn-repeat-crisp-questions-into-drafted-help-center-articles