> ## Documentation Index
> Fetch the complete documentation index at: https://help.mory.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows in mory: overview

> What a workflow type is, which types exist, and how checklists guide you through a case.

Every task in mory has a workflow type. The type decides which checklist the task gets, which fields are mandatory, and how the mory agent supports you. This page gives the overview; the individual guides are linked in the table below.

## What a workflow type is

A workflow type is a tag on the task, for example **Schadensbearbeitung** (Damage handling) or **Mietereinzug** (Tenant move-in). It defines:

* which steps appear in the **Checkliste** (checklist),
* which details are mandatory when creating the task (for example property and unit),
* whether and how the agent takes part (the **Mory AI** suggestion card),
* the default due date of the task.

## How the type is assigned

* **Automatically by the AI**: When a task is created from an email, a phone call, a WhatsApp message or a portal report, mory classifies the content and sets type, priority and language, plus property, unit, equipment and contact where they can be recognised.
* **Manually in the wizard**: Under **Aufgaben** (Tasks) › **Neue Aufgabe** (New task) you pick the type in the workflow type selector. The mandatory fields adapt to the chosen type.

You can change the type later in the task details. The checklist is replaced accordingly.

## All workflow types

| Tag in mory                       | Typical trigger                                             | Steps        | Guide                                                           |
| --------------------------------- | ----------------------------------------------------------- | ------------ | --------------------------------------------------------------- |
| Schadensbearbeitung               | Tenant reports a defect by email, phone, WhatsApp or portal | 5            | [Damage handling](/en/workflows/damage-basic)                   |
| Schadensbearbeitung (Multi-Offer) | Larger damage, several quotes needed                        | 7 phases     | [Damage with multiple quotes](/en/workflows/damage-multi-offer) |
| Allgemeine Anfrage                | Question or request without damage                          | 3            | [General request](/en/workflows/general-request)                |
| Versicherungsfall                 | Hail, water, glass, natural hazard                          | like damage  | [Insurance case](/en/workflows/insurance-case)                  |
| Mietereinzug                      | New tenant signs                                            | 14           | [Tenant move-in](/en/workflows/tenant-move-in)                  |
| Mieterauszug                      | Notice of termination arrives                               | 17           | [Tenant move-out](/en/workflows/tenant-move-out)                |
| Mieterwechsel                     | Termination with re-letting in one case                     | 26           | [Tenant change](/en/workflows/tenant-change)                    |
| Sanierung & Renovation            | Construction project on a property                          | 19           | [Renovation & refurbishment](/en/workflows/renovation)          |
| Objektvermarktung                 | Unit needs to be advertised                                 | 6            | [Property advertisement](/en/workflows/property-advertisement)  |
| STWEG Beschlüsse                  | Minutes of the owners' meeting are available                | 4            | [Condo community decisions](/en/workflows/condo-decisions)      |
| Notiz, Erinnerung                 | Personal notes and deadlines                                | no checklist | [Notes & reminders](/en/workflows/notes-reminders)              |

## How checklists work

You find the checklist in the right sidebar of the task and via **Checkliste öffnen** (Open checklist).

* **Required or optional**: Required steps must be completed before the task can be closed. Optional steps can be skipped.
* **Skipping**: **Skip** jumps to the next step, for example when a step does not apply to your case.
* **History**: Every change to a step is logged in the task's activities. Agent actions carry a robot icon.
* **Taking over manually**: You can complete any step yourself at any time, even if the agent has made a suggestion.

<Info>
  Administrators adjust steps, agent instructions and check criteria per organisation in the **Workflows** module. See [Configuring workflows](/en/admin/workflow-configuration). Step names in your checklist may therefore differ slightly from the guides here.
</Info>

## Third-party systems in steps

Some steps mention systems such as ELO, ImmoTop, the BeWi dashboard or ImmoMig. These steps are reminders of work to be done outside mory. They are not integrations: mory does not write to these systems. You complete the step there and tick it off in mory.

## Related pages

* [Damage handling](/en/workflows/damage-basic)
* [Tenant move-in](/en/workflows/tenant-move-in)
* [Notes & reminders](/en/workflows/notes-reminders)
* [Configuring workflows](/en/admin/workflow-configuration)