---
title: Request to the Talemo team
summary: When the assistant cannot do what a person asks because Talemo does not have it, it says so and passes the request to the Talemo team in the person's own words. It does not promise a date. It fixes its own mistakes itself and does not write to the team about them.
tools: [talemo_send_feedback, talemo_add_feedback_wish]
related: [staff-assistant, assistant-mode, chat-topics, confirmation-cards]
search: [support, feature request, request to the team]
---

# Request to the Talemo team

## When the assistant cannot

Talemo does not do everything yet. When a person asks for something it cannot do,
the assistant says so in its own words and does not work around it with other tools:
that it is not there yet, what the person can do by hand, and then it asks once how
they would like it to work. Talemo puts no words of its own into the assistant's answer,
and the assistant does not say that it passed the request on.

That the request reached the team shows right under the answer, and Talemo itself puts it
there, only when the request really went out. It is a grey card "Talemo can’t do this yet":
under the title "The Talemo team has this request. We can’t say when it will be ready.",
and below it in grey the request as the team got it. It is the assistant's retelling, so
there are no quotation marks. A long request shows three lines, and a tap opens all of it.
No card means the request did not go out.

## What goes to the team

The request is passed on at once, when the assistant says it cannot, even if the
person does not answer or says "not now". It carries the person's request in their
own words, and the business and the place the person wrote from. The person's
answer to "how would you like it?" is added to the same request, and a line appears
under the answer: "The Talemo team got the addition to your request."
If the person asks for the same thing again right after, the team still gets one request:
the repeat is added to it, and the card under the answer is shown again.
Asked later, it is a new request with a card of its own. A wish is added once to a
request. The steps above the answer are named for what they did: "Passed to the team",
"Wish added". If the tool refused, the step says "Didn't work" and there is no card or line
under the answer.

## When the assistant made a mistake

The team gets only what Talemo does not have. If the assistant made a mistake, did not
do what it said, or did something else, and the person writes about it ("you did nothing",
"that's not it", "wrong again"), that is not a request to the team: the assistant fixes it
itself, in the same answer, and if it did not understand what was wrong, it asks once. What
it really did shows under its answer (see [The assistant](staff-assistant.md)): the
names of the steps and a line "… · Done" for every change that went through.

## What it does not promise

The assistant does not name a date. It also does not promise to tell the person when
the feature appears, because Talemo does not send such a message.

## Mailings

Talemo has no mass mailings. The assistant writes to clients one chat at a time and
refuses to write to many different chats in one go. A request for "a card to everyone"
is something it cannot do yet, and it is passed on as described above.

## Who reads it

The Talemo team reads these requests in its own admin tool, together with the
business, in the person's words. Nobody is asked for approval: the request goes out
quietly, in either mode of the assistant, and there is no decision card for it.

Only the assistant for the team passes requests on. The online admin does not talk
about the system with clients. A program connected over MCP has no such tools
either. The assistant's own tools for this are `talemo_send_feedback` and
`talemo_add_feedback_wish`.

## Tools and refusals

- Only the assistant of the team passes requests on. `talemo_send_feedback` and `talemo_add_feedback_wish` are not listed to a business key, to Claude or to ChatGPT, and the online admin does not talk about the system with clients.
- `talemo_send_feedback` passes one thing: what the person asked for is not in Talemo and no tool does exactly that. `request` is the person's request in their words. Do not piece a missing feature together from other tools: pass the signal at once, when you tell the person that Talemo cannot do it yet.
- This is not a signal: your own mistake ("you did nothing", "that's not it", "wrong again") — fix it in this same answer and pass nothing; something a tool does — find that tool; a rule of the business — it belongs to the knowledge; an error with a code — Talemo already sees it.
- When the signal succeeds, the person sees under your answer that it reached the team (a card "Talemo can’t do this yet"), so do not say it yourself: say in your own words that Talemo cannot do it yet, offer what they can do by hand, and ask once how they would like it to work. Call `talemo_send_feedback` once per request: when the person then thanks you or agrees, do not call it again, the request is already with the team. Their answer about how it should work goes to `talemo_add_feedback_wish`; when there is nothing to add it to, it is refused with `feedback.wish_closed`: do not say you added it, and do not ask again. A refused call did not reach the team, and you must not say it did.
- Promise no date, and do not promise to tell the person when it is ready.
