Simply AskingDocs

Turning a Chat Answer into a Document

Save, derive, or combine chat answers into permanent knowledge base documents your whole team can search.

This guide is for everyone on the team. Whenever you get a useful answer from Lumen in a chat session, you can turn it into a permanent document that the rest of your organization can search and reference. If you have not yet used the Ask interface, complete the Your First Search and Your First Question guide first.

Save, derive, or combine chat answers into permanent knowledge base documents your whole team can search. By the end of this guide, you will know three different ways to turn conversations into lasting knowledge: saving an answer directly, deriving a new document from context, and combining multiple answers into a single comprehensive document.

1

Start a Chat Session

Click Ask in the center navigation bar and type your question. Ask something specific that your team would benefit from having documented, such as "What is our process for onboarding new clients?"

2

Get a Great Answer

Review the answer from Lumen. It will synthesize information from your uploaded documents, cite its sources, and present a grounded response. If the answer is comprehensive and accurate, it is a great candidate for saving.

3

Click "Save to KB"

Look below the answer for the Save to KB button. Click it to begin converting the answer into a permanent knowledge base document.

4

Edit Title, Tags, and Department

A dialog appears where you can customize the document. Give it a clear, descriptive title. Add relevant tags so your team can find it easily. Select the department that should own the document.

5

Save the Document

Click Save. The chat answer becomes a full knowledge base document. It enters the processing pipeline just like any uploaded file.

6

Find It in the Library

Once processing completes, your new document appears in the Library. It is now searchable by your entire team through both Search and Ask.

Deriving creates a new document that builds on the chat context but gives you full control to write original content. Use this when the chat gave you a starting point but you need to expand, restructure, or add your own expertise.

When to Use Derive: The chat answer covered the basics, but you want to add context, include examples, or reorganize the information into a more structured format for your team.
1

Click Derive

Click Derive below the chat answer to generate a new document pre-filled with context from the conversation.

2

Edit the Content

Edit the generated content. Rewrite sections, add your own analysis, and include details the chat did not cover.

3

Add Your Own Sections

Add your own sections. The derived document is fully editable, so you can structure it however works best for your team.

4

Save the Document

Save the document. It enters the processing pipeline and becomes searchable by your team.

Combining merges insights from multiple chat exchanges into one comprehensive document. Use this when you have asked several related questions and want to consolidate everything into a single reference.

When to Use Combine: You asked about onboarding steps, then about required paperwork, then about team introductions. Now you want one "Complete Onboarding Guide" that brings it all together.
1

Select Multiple Messages

Select multiple chat messages in your conversation that you want to merge into a single document.

2

Click Combine

Click Combine to generate a merged document that synthesizes content from all selected messages.

3

Review Merged Content

Review the merged content. The system organizes related information together and removes redundancy.

4

Edit and Save

Edit and save. Refine the structure, add any missing details, then save it to your knowledge base.

Pro Tip: The best knowledge base documents come from real questions. When you get a great answer from Lumen, save it. Over time, your team's actual questions become the foundation of your knowledge base.

Now that you know how to turn conversations into documents, learn how to synthesize your entire knowledge base into structured briefs. Briefs pull insights from dozens of documents into a single, shareable summary with citations.

Was this helpful?