---
title: Knowledge entry
summary: An entry is an article or an answer to a frequent question that the online admin tells clients in words. One entry is the voice of the business.
tools: [talemo_find_knowledge, talemo_get_knowledge, talemo_create_knowledge, talemo_update_knowledge, talemo_archive_knowledge, talemo_restore_knowledge]
related: [versions-and-removed, suggestions, knowledge-search, online-admin-and-knowledge]
search: [FAQ, article, answers for clients, tone of voice]
---

# Knowledge entry

Knowledge is what the business says about itself in words: how to get there,
the rules, how a service goes. The online admin answers clients from it, and
the assistant reads it when it helps the team. In the web version the section
is called **Knowledge**.

## Two kinds of entry

- **Article:** a title and a text.
- **Answer to a frequent question:** a title, a text and the other ways clients
  ask it, one per line (**Also asked as**). A search finds the answer by any of
  them. Only an answer has these variants.

## Topic

Every entry has a topic: About us; Services and how they go; How to get here;
Rules: booking, being late, cancelling; Payment; Frequent questions. The topic
**How we talk to clients** is kept for the voice and holds nothing else.

## The voice

The voice is a single entry about how the business talks to clients: formal or
casual, how it greets, emoji, the words it uses and never uses. It has no
title and no branches, and a business has one. Writing a second one is refused
until the first is edited or removed. General politeness does not need to be
written down: the online admin knows it already.

## Where an entry applies

An entry can be about chosen branches and chosen services of a branch. With
nothing ticked it is about the whole business. An entry about a service also
shows on the service's page in settings, under **Knowledge about this service**.
Knowledge belongs to the business as a whole.

## Prices and times

Prices, durations, schedules and discounts are not knowledge. The online admin
takes them from the price list and the schedules, and the text of an entry is
for the words around them.

## Who can do what

A role can be given three rights separately:

- see the knowledge and its history;
- suggest changes, which wait for approval (see [Knowledge suggestions](suggestions.md));
- write, change, remove and bring back. Each save is the approval.

The ready-made Accountant role does not see the knowledge at all. A program
connected over MCP reads entries and suggests changes, and cannot change them.
The assistant changes entries at a person's request and always asks first (see
[Versions, history and removed entries](versions-and-removed.md)).

## Tools and refusals

- Knowledge is what the assistant and the replies to clients say in words: articles, answers to frequent questions and the voice of the business, the one article with place `voice` on how it talks to clients. Prices, durations, schedules and discounts are not knowledge: they live in the price list and the schedules (`talemo_list_services`, `talemo_get_schedule`).
- `talemo_find_knowledge` lists the entries: the voice first, then by topic and title, without the text. `topic` (`about`, `directions`, `services`, `rules`, `payment`, `faq`, `communication`), `service` and `archived` narrow it, and the counts of live entries by topic come along. Pass `next` as `after` for more. With `q` it searches instead (see [Searching the knowledge](knowledge-search.md)).
- `talemo_get_knowledge` shows one entry by `document_id`: the text, the other wordings of the question, the branches and services it is about (none means the whole business), its `version`, who wrote it and who approved it. `talemo_get_knowledge_history` shows each version whole, newest first; pass `next` as `before` for older ones.
- Look before you write: an entry that exists is changed, not written a second time.
- Over a business key or a connection of Claude or ChatGPT knowledge is only read and proposed (see [Knowledge suggestions](suggestions.md)). A direct change from a program is refused with status 401, code `auth.required`, which here means that the person does it in Talemo, not that the connection is broken. `talemo_create_knowledge`, `talemo_update_knowledge`, `talemo_archive_knowledge` and `talemo_restore_knowledge` exist only for the assistant of the team, and each change waits for the person's approval on a card in the conversation: do not ask them to type yes, and when the tool returns the entry, the person has allowed it and it is saved.
- `talemo_create_knowledge` takes `kind` (`article` or `answer`), `topic` and `body`; the voice is `place` `voice`, one per business, and a second one is refused with status 409, code `knowledge.voice_taken`. The topic `communication` holds only the voice: anything else there is refused with `request.body_invalid` and `params.field` `topic`. Keep the meaning of the person in their words and add no fact they did not say.
- `talemo_update_knowledge` takes the `version` from `talemo_get_knowledge`: if the entry was saved since, it is refused with `knowledge.version_conflict` and `params.version`. Read the entry again and redo the change. The text, the wordings, the branches and the services are given whole, as they will be; what is left out stays. A removed entry is brought back first (`knowledge.archived`).
- `talemo_archive_knowledge` removes an entry from what the assistant says; nothing is lost, and `talemo_restore_knowledge` brings it back with the text it had. The voice cannot come back while another voice is live: status 409, code `knowledge.voice_taken`.