It knows how you work.
Your principles, policies, prices, catalogue and documents, kept as knowledge you name, used only where you say, seen only by who you allow.
Named, placed, protected.
Knowledge you name.
Prices, Policies, Team notes. Each knowledge base has its own name and a description of what it holds and who it is for.
Used where you say.
Set once per knowledge base whether it answers your customers, supports your team, or both.
Seen by who you allow.
Make a knowledge base private and choose which roles can read it. Left empty, only you can.
Files or your website.
Add PDF, TXT, MD or JSON files, or bring in a page, a list of pages, a sitemap or a whole site.
From a document to an answer.
Five steps, in this order.
- 1 Name
Name it, say what it's for.
Give the knowledge base a name and a description of what it holds and who it is for.
- 2 Add
Add files or your website.
Drop in files, or point it at a page, a list of pages, a sitemap or a crawl of your site.
- 3 Audience
Say where it's used.
Customers, your team, or both. Visibility decides which of your team can read it.
- 4 Test
Ask what it would find.
Ask Felesh what it would find for a question, before a customer ever asks it.
- 5 Manage
Change it by saying so.
Tell Felesh to add a page. The change is queued and waits for your yes.
Where this does the most.
Noah asks on Instagram whether you open on Saturdays. Your opening hours live in a Policies knowledge base set to Customers, so Felesh can answer him.
Audience · CustomersSee the playbook →Maple Studio's rate card is for your team, not your clients. You keep it in a private knowledge base set to Team, with only the roles you choose allowed to read it.
Private · TeamMrs Keller's question isn't covered yet. You ask Felesh what it would find, see the gap, and add the missing page. It is queued until you say yes.
Queued · waits for your yesWhat a knowledge base does not do.
And what happens instead.
- It does notIt does not make up answers.InsteadWhen nothing in your knowledge bases fits, the conversation comes to you, with the reason.
- It does notPublic does not mean on the internet.InsteadPublic here means every operator on your team can use it. Private limits it to the roles you allow.
- It does notAudience and visibility are not the same setting.InsteadAudience is who it answers. Visibility is which of your team can read it.
- It does notChat cannot set who may read a private knowledge base.InsteadAllowed roles are set where you edit the knowledge base. Everything else you can ask for in chat, and it waits for your yes.
Can I keep more than one knowledge base?
Yes. Give each its own name and description, for example Prices, Policies and Team notes, and choose where each one is used.
Can I keep some knowledge away from customers?
Yes. Set its audience to Team and Felesh uses it to support your team, not to answer customers. Make it private as well and only the roles you allow can read it.
What can I add?
Files in PDF, TXT, MD or JSON, up to 50 MB each. From your website you can add a single page, a list of pages, a sitemap, or a crawl that follows links within the same site.
Can I check what it knows before a customer asks?
Yes. Ask Felesh what it would find for a question and it looks across your knowledge bases and tells you where it found it.
Can I manage it by talking?
Yes. Create, rename, describe, add or remove documents and change the audience by saying so. Each change waits for your yes, and an addition shows as queued until it is done.
Hand it the work. Keep the decisions.
Hand Felesh the work you've been carrying?14 days free, no card. Everything that needs your call still waits for your yes.