AI analyses: dig into a conversation

An AI analysis evaluates a meeting based on your question — for example "Summarise the decisions", "What are the open points?" or "How was the mood?". Unlike the AI summary, which gives a fixed overview, an analysis answers exactly what you need right now.

You can create new analyses once AI and the assistant are available in your organisation and the meeting has notes or a transcript. Saved analyses remain accessible according to your meeting read permission even when AI is temporarily unavailable.

Analyse in the assistant

1. Open a meeting and choose Create analysis beside the saved analyses. The assistant opens and adopts exactly this meeting as a reference. No AI request starts yet.
2. Write your instruction in the normal message field. Analyse meeting · Examples & templates offers decisions, open points, risks and Choose template. The searchable picker uses the existing organisation-wide templates.
3. Examples and templates fill that same field. If it already contains a draft, the instruction is appended and a notice appears. Edit the text and send it yourself.
4. Click Revise on the selected answer and enter your changes in the same message field, for example “Shorter.”, “Only binding decisions.” or “Add the unresolved responsibilities.” Answers and follow-up questions do not create meeting analyses yet.
5. On a completed result associated with a meeting, choose Save as analysis …. Check the meeting and title, then confirm Save privately. If several meetings qualify, select the target explicitly.
6. Saved privately to the meeting · Open analysis opens the saved result at the correct meeting. Only this answer, its sources and instruction are saved. Saving does not run the AI again.

The association belongs to the individual answer. Navigation and later reference changes do not move its target. If saving fails, the title and selection remain available for retry. Later replies never change a saved analysis. You can save a revised answer as another analysis. Reloading preserves the link to the saved result. Cancel beside the revision notice removes the answer association without deleting your draft.

Navigation preserves both your draft and the selected revision. If the selected answer has changed, been deleted or become inaccessible, a notice appears instead of a new AI answer; this also applies when regenerating. If your instruction is too long, shorten it or ask a new question.

Save as template copies the current message text to the organisation's existing library after you enter a title. Using, saving and managing templates requires meeting write access and access to the assistant. Manage templates opens management directly beside the same message field.

New results are private and excluded from search. Publication and separate search release still happen at the meeting. If the conversation used additional sources outside the target meeting, the result remains private so differing source permissions cannot be bypassed. Source access is checked again when saving. The personal conversation and its other messages are not published. Titles of adopted references also count as sources. Replies using activity, time-report, ticket-list or code tools without a complete source list also cannot be saved as analyses. Saving is unavailable when older or interrupted replies in the conversation context lack complete provenance; start a new conversation with the meeting reference in that case.

The fixed AI summary in the meeting header keeps its own create and refresh button. It remains separate from free-form analyses in the assistant.

Where to find analyses

Finished analyses appear as a list directly below the meeting — they are part of the meeting record and visible without a detour. Expand each one via Show result.

Create analysis sits beside that list. On desktop it opens the existing assistant interface; on mobile it opens that same assistant as a bottom sheet. Examples, templates, follow-up questions and revisions always use its single message field. A private meeting result is created only when you choose Save as analysis … on a completed answer.

Derive tasks as tickets

The Ticket suggestions section offers Derive tasks, or Derive again when results already exist. The entry opens the same assistant, adopts the correct meeting and target project, and prepares the visible task mode. It does not submit anything yet. Unlike a free-text analysis, which returns text, this flow turns the meeting into concrete tasks as ticket suggestions — each one can be turned into a real ticket individually or dismissed. The shared list remains visible at the meeting.

That way "What needs doing?" no longer gives you a hard-to-read wall of text but an actionable list.

Private, publish, release for search & chat

A new analysis is private at first — only you can see it. Publish makes it visible to all project members with meetings read access; Retract makes it private again.

Only after publishing can you also release it for search & chat — its content then becomes findable in search and in the AI assistant, independent of whether the meeting itself is released.

Ticket suggestions in the assistant

Use Derive tasks or Derive again in the meeting's ticket-suggestions section. The entry adopts exactly that meeting as reference and target; other existing references remain in place. It does not overwrite a draft. Review the instruction, meeting and target project, then send it yourself. Leave task mode cancels special processing without deleting your text. Create analysis leaves a previously active task mode so an analysis cannot accidentally start a suggestion run.

Suggestions are visible to people with access to this meeting. Tickets are created only when you accept a suggestion. Only the selected meeting’s notes and transcript and your explicit instruction are used. Personal chat history, other references and saved analyses are excluded. The per-source limit is shown beside the message field before submission; shortened sources are identified. If sources change before the run finishes, no result is published. You can try again using the current sources.

The instruction, meeting, target project and status remain in the conversation across navigation and reopening. Errors offer Try again; a successful run without tasks says so explicitly. Expand any suggestion, then choose Create as ticket or Dismiss. A ticket is created in the meeting’s project and linked to the original meeting. Open ticket leads to the created ticket. Acceptance additionally requires ticket write access; generation and dismissal require meeting write access.

A successful new run replaces all open suggestions for this meeting, including those used by other people. The assistant explains this before submission. Older conversation entries keep their original suggestions marked as superseded, with acceptance disabled. Accepted and dismissed suggestions remain in history. A failed run leaves open suggestions unchanged. Relevant truncation of the list, titles or descriptions is shown with the applicable limits.

Use Refresh status to update completed results; automatic checks when returning to the visible result area occur at most once per minute. Try again creates at most one new attempt per failed task. Deleting the conversation deletes its run and instruction; meeting-wide suggestions remain available at the meeting.