Trigger Analysis on Conversation Completion
Trigger when a support ticket is resolved or a chatbot conversation closes. Capture the full transcript, resolution status, product area, source link, and relevant tags.
Keep a support knowledge base current by mining resolved conversations for reusable answers, checking for existing coverage, and publishing only approved, source-linked FAQ updates.
Download the skill for this workflow. Version 1.0.1.


with Claire Vo
Reid analyzes each resolved support conversation for its core question and solution, checks the existing knowledge base, routes a proposed FAQ through human review, and adds approved entries to the chatbot source.
An approved FAQ entry linked to its source conversation and available to the internal or customer-facing assistant.
Workflow automation platform
Follow the sequence once, then adapt the prompts, checks, and handoffs to your own setup.
5 steps
Trigger when a support ticket is resolved or a chatbot conversation closes. Capture the full transcript, resolution status, product area, source link, and relevant tags.
Extract the reusable user question and the solution actually confirmed in the conversation. Return unresolved when the transcript lacks a verified answer.
Analyze this resolved support conversation. Return JSON with reusable_question, verified_answer, product_area, prerequisites, source_evidence, resolution_status, and sensitive_details_to_remove. Do not infer a solution that was not confirmed in the transcript.
Search the current knowledge base semantically and by product area. Update a matching article when the answer adds useful detail; otherwise draft a concise new FAQ with source provenance.
Compare this verified question and answer with the retrieved knowledge entries. Return duplicate, update_existing, or new_entry with the matching article ID and reason. If an update or new entry is warranted, draft concise customer-safe copy without account-specific details.
Send the proposal to a named reviewer with the source conversation, duplicate analysis, and suggested destination. Allow edit, approve, reject, or route back for missing evidence.
Review is for accuracy and reuse, not a ceremonial approval. Give the reviewer the source and the proposed change together.
On approval, write the entry to the correct knowledge source, preserve owner and provenance, refresh the chatbot index, and record the published article ID in the review item.
Turn an idea into a PRD, user stories, and a plan.
How to recover when the loop fails and where human judgment helps.

Create a repository-based system to provide an AI assistant with durable context about your team, projects, and communication channels. This enables it to perform routine tasks like summarizing daily updates and identifying stakeholders, acting as a personalized chief of staff.

Use Meta's Muse to generate a printable, multi-page family newspaper that includes a weekly schedule, weather forecasts, and activity ideas. This workflow leverages Muse's strength in creating visually appealing, family-oriented artifacts.

Coordinate agents in Slack and Cursor to propose growth experiments for human review. Ezra’s Auto XP system was still being developed at the time of the episode.
Join 250,000+ product managers who use ChatPRD to write better docs, align teams faster, and build products users love.