Build apps · Your App Cloud
Build an AI knowledge base
Let people ask questions of your handbook, policies and FAQs and get answers that link to the passage they came from. You choose the sources and who can ask.
Built around a purpose
From your handbook to answers people can check.
For people who answer the same questions from the same documents. That might be an operations lead with the staff handbook or a support team with a returns FAQ.
For illustration: an employee handbook, a travel and expenses policy, an approvals guide only managers should see, and a returns FAQ for the support team. Add 25 questions taken from recent messages to HR and support, in the words people used.
A question box that answers from those four documents and links each answer to the section it used. It points to a contact when the documents are silent, and it collects flagged answers for each owner.
This app needs Pro: a language model answering inside the app, saved flags and sign-in for private documents are backend capabilities. Free publishes frontend-only static apps. Model and service usage is metered separately.
Sort the sources by audience
Give each document an audience, such as all staff, managers or support, and a status of current or superseded. Leave out drafts and anything you would not hand that audience on paper.
Write the question list first
Keep each question in the asker's words, such as whether unused vacation days carry over. Include a few the documents can't answer, such as next year's office closures. They show you how the app handles a gap.
Describe the shape of an answer
Tell Studio what every answer needs: a short reply and a link to the document and section it relies on. Questions the sources don't cover get a set response naming who to ask.
Run the list in the preview
Check each answer against its linked section, not against what you remember the policy says. Then repeat a few questions signed in as a staff member and as a manager, and compare what each one sees.
Route flags to the document owner
Add a flag button that saves the question, the answer and the reader's note. The owner reviews that list, corrects the document, and re-imports it when the policy changes.
Scope the first version
What a first version includes.
Source library
One record per document with its title, audience, status and a review date.
Answers with a source link
People type questions in their own words. Each answer names the document and section it relies on and links there, so readers can compare the wording.
A reply for gaps
A set message for questions the sources don't cover, naming the person or team who can answer.
Flagged answers
Answers readers marked as wrong or unclear, saved with the question and their note and grouped by document owner.
Unanswered questions
Every question that got the gap reply, so you can see which topics the documents are missing.
Test questions
Your question list with the section you expect each answer to use, kept so you can rerun it after an update.
Test it in the preview
Before you share it.
- Open five answers at random and read the linked section. The answer should match it, including conditions such as a spending limit or a notice period.
- Ask something the documents don't cover. You should get the gap reply, not a plausible guess. If you get a guess, tighten the instructions in Studio and ask again.
- Signed out, confirm the private sources can't be reached at all. Signed in as a staff member, ask about manager approvals and confirm the answer doesn't draw on the approvals guide.
- Replace one policy with an edited copy and ask the question it changes. The answer should follow the new wording and stop quoting the old version.
- Flag an answer and confirm it reaches the owner's list with the question and your note attached.
Together in your app cloud
The pieces behind the possibility.
Choose the models and services that support the experience you want to create.
Language models
Reason, write, and understand
File storage
A home for your documents and media
Database
Keep data and context for apps and agents
Authentication
Give the right people access
Shape the details
Make it work for your world.
- Keep one version of each policy live. If last year's expenses policy sits beside this year's, answers can quote either, so mark the old one superseded or remove it.
- Name an owner for every document before launch, because a flag helps only if someone can fix the source. On Pro you can invite that person to your workspace as a team member.
- Say in the app that answers come from the listed documents and can miss context. Point people to a person for decisions about pay, leave or a customer's refund.
A little more context
Good questions.
How can people evaluate an answer?
Give every answer a link to the section it used, so a reader can compare the two. Test with questions the documents answer and questions they don't, and let readers flag an answer that looks wrong. People should rely on the linked source, not the answer alone.
Is this for staff or for customers?
Either, with different sources and access. A staff version sits behind sign-in and can draw on internal documents. A customer version should use only material you would publish anyway. If you also want requests handed to a person, see the support agent and internal helpdesk agent guides below.
How do I keep answers current when a policy changes?
An uploaded file is a snapshot, not a live link. Edit the text in the app or re-import the new version, mark the old one superseded, and rerun the test questions it touches. On Pro, a scheduled task can list the week's flagged answers and documents due for review; a person still decides what changes.
Which files can I start from?
Start from the handbook, policy or FAQ people already ask about. The PDF, Word and PowerPoint guides below cover preparing each format. Whichever you bring, compare a few imported sections with the original in the preview, tables included, before anyone relies on the answers.
Explore Pricing for plans, included capabilities, and usage details.
Start from what you have
Bring the file you already use.
Keep exploring.
Your ideas, up and running
Your next idea has a home.
Build an app. Run an agent. Make it yours.
Start building