# Working in the assistant

{/* AUTO-SYNCED SOURCE: this page lives in apps/app/src/modules/db-leads/docs/ and is mirrored into the docs app by `bun sync:module-docs`. Edit it in the module, not in apps/docs. */}

<Lead>
You do not have to open the list to use it. The assistant under **/agent** knows DB-Leads as a plugin with nine skills: four read, five write. A question becomes a listing, and every change shows you a card first.
</Lead>

## What you can ask

<DefinitionList>
  <DefItem term="Filter the database">"Which owners have an inheritance or a divorce as a trigger and were contacted in the last two years?" The assistant uses the same filters as the list: signal, sale readiness, acquisition status, phase, owner, follow-up, city, period. On top of that come **keywords in the AI output**, meaning summary, briefing, plan and key facts. Every row carries customer number, name, phase, sale readiness and the AI summary.</DefItem>
  <DefItem term="Read findings">"What should I work on today?" The open findings, strongest first, with the same contact filters. On request also resolved ones, by band or from a minimum score.</DefItem>
  <DefItem term="Read a dossier">"What do we know about customer number 4711?" Everything the tool knows: contact details, briefing with evidence, plan and opener, detected properties, findings, follow-up, blocked channels and the history with notes. The history can be narrowed by type, period and keyword.</DefItem>
  <DefItem term="Numbers">"How many contacts are in which phase, how many findings are open?" Contacts per phase, open findings per band, sale readiness, due follow-ups, qualification progress.</DefItem>
</DefinitionList>

One example that shows what fits together: "Search the findings for sale-ready owners who will sell their house once they have found an accessible flat as a replacement, and list them with customer number, last name, first name and a short AI summary." The assistant filters the findings by sale readiness and keywords and builds the table from the summaries.

## What you can instruct

Each of these skills shows you a card with what is going to happen before it writes. Only your confirmation runs it.

<DefinitionList>
  <DefItem term="Set a follow-up">"Bring the Brandt family back up in three months." The follow-up is created as a real task, visible under Tasks and in onOffice, with a reminder on the due date. See [Follow-ups](/tools/db-leads/wiedervorlage).</DefItem>
  <DefItem term="Set a phase">"Move him to Hot Leads." The phase is named as on the board. Rules on the phase change run as they do on a click.</DefItem>
  <DefItem term="Assign an owner">"Assign me" or "give him to Maria Krause". If an onOffice field for the owner is configured, the value goes to the CRM, provided the member is mapped to an onOffice user.</DefItem>
  <DefItem term="Decide a finding">"Accept the finding", "dismiss it, not an owner", "snooze it for two weeks". Accepting sets the recommended phase, as in the inbox.</DefItem>
  <DefItem term="Set sale readiness">"Set sale readiness to Preparation, she asked for a valuation." The level must be one from your settings, the reason is mandatory and becomes a note. The next analysis reads it.</DefItem>
</DefinitionList>

Deliberately not a skill: archiving, deleting, advertising objection, data request and starting a scan. Those are decisions with external effect or data loss, and they stay in the interface.

## Permissions and visibility

The assistant works with the permissions of the person asking. Whoever only sees their own contacts also only gets those in chat. Follow-up, phase and sale readiness need **Edit contacts**, ownership needs **Assign owner**, the finding decision needs **Qualify**. See [Permissions](/tools/db-leads/berechtigungen).

Which skills are on in the workspace is decided by the administration under **Assistant, Plugins, DB-Leads**. That is also where you see what the plugin sends to the AI, and the changelog. See [Assistant plugins](/tools/agent/plugins).

## Where the answers come from

The skills read the same data as the interface and write through the same path as the buttons in the tool. An accepted finding promotes the contact to the recommended phase exactly like in the dialog. A note or a call result is not written through this plugin but through your personal [onOffice AI Connector](/tools/agent/plugins) into the activity log, under your name. The assistant does not assess anything itself: sale readiness, signals and summary come from the [database scan](/tools/db-leads/datenbank-scan) and the [acquisition agent](/tools/db-leads/akquise-agent).

<Callout type="tip" title="Numbers instead of paging">
For a question about the whole database the assistant first gets the numbers and then filters precisely. It does not page through the list. If every contact really has to be re-assessed, it says so and points to the database scan.
</Callout>