# Frequently asked questions

{/* 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>
The questions we get asked most often about DB-Leads. If a scan will not start, or you are looking at an error message, the answer is under [Troubleshooting](/tools/db-leads/troubleshooting).
</Lead>

<Faq>
  <FaqItem q="Is DB-Leads the tool for new portal enquiries?">
    No. DB-Leads mines your **existing** database for seller leads. A separate tool is planned for new enquiries from new contacts arriving through portals and web forms.
  </FaqItem>
  <FaqItem q="Does DB-Leads replace my CRM?">
    No. Your database stays authoritative in onOffice. DB-Leads reads it, analyses it and writes results back. A complement, not a replacement.
  </FaqItem>
  <FaqItem q="Do I strictly need onOffice?">
    For the full benefit, yes: the scan lives on the activity history of your contacts, and that comes from your CRM. To try things out you can load sample contacts in the setup assistant. They are labelled as samples everywhere and disappear with the first sync against your real database.
  </FaqItem>
  <FaqItem q="What does a database scan cost?">
    Nothing extra. The AI analyses of a scan are included in the add-on, and a scan that has started always runs to completion. The add-on carries a fixed quota of full scans per month; incremental scans only analyse what is new and are possible at any time. All figures: [Cost and add-on](/tools/db-leads/kosten).
  </FaqItem>
  <FaqItem q="Does the AI decide about a lead?">
    No. The AI presents findings with evidence. Accepting, rejecting or postponing is your decision. The phase assignment of the acquisition agent is logged and correctable at any time as well, and in **suggest** mode you confirm it yourself.
  </FaqItem>
  <FaqItem q="How do I know a finding is correct?">
    Every finding points to the activity it came from. You read the evidence before you accept. There is no statement without evidence, and that is also how you spot an assessment that is off.
  </FaqItem>
  <FaqItem q="What is the difference between status and seller score?">
    The status says **where in the process** a contact stands, from new to won. The seller score of the database scan says **how likely** a listing is. A contact can be dormant and still carry a hot finding, and those are exactly the cases the scan surfaces.
  </FaqItem>
  <FaqItem q="Does the tool work without an AI provider?">
    Partly. The status derivation of the acquisition agent is deterministic and runs without a configured model. A provider improves the briefing texts and is what makes the database scan possible in the first place.
  </FaqItem>
  <FaqItem q="Do age, origin or marital status feed into the assessment?">
    No. Seller signals come exclusively from statements the person made in the activity history, such as a mentioned intention to sell or a follow-up mandate. Personal characteristics such as age, gender, origin, religion or marital status are not scored. That is not a setting, it is a boundary of the tool.
  </FaqItem>
  <FaqItem q="Which data goes to the AI provider?">
    For the analysis, the details and activities of the respective contact go to the model your workspace uses. Only your own client database is analysed. Where the computation happens, and with which provider, is controlled in the workspace privacy settings and in the tool [settings](/tools/db-leads/einstellungen).
  </FaqItem>
  <FaqItem q="How often should I scan?">
    After every larger sync a scan pays off. The freshness check makes sure only contacts with new activities are analysed, which keeps follow-up scans fast. If you would rather not start anything by hand, switch on the automatic scan in the settings.
  </FaqItem>
  <FaqItem q="Why did my rule do nothing?">
    Four common reasons: the rule is still paused, which is how every new rule starts. It only applies to new events after activation; the past never fires afterwards, and you reach existing contacts via "Apply to existing contacts". The action is waiting in the approvals list because your action approval is set to approval. Or the field change in onOffice has not been synced yet: it is detected at the next sync, and the first sync after activation only learns the starting value. The rule's log tells you which case it is. Details under [Rules](/tools/db-leads/regeln).
  </FaqItem>
  <FaqItem q="Why does almost every contact say “No properties found”?">
    Because that is the normal case in this phase. DB-Leads hunts for listing mandates, so it works the period **before** the mandate, and before the mandate the property is recorded nowhere. The section fills from two sources: what the analysis finds in the correspondence, and what you record yourself after a call. See [Ownership](/tools/db-leads/objekte).
  </FaqItem>
  <FaqItem q="Ownership used to show properties from my own inventory. Why not any more?">
    Because the match was wrong. When onOffice holds no owner relation, it fell back to matching the **address**, and then a buyer would be shown their neighbour's property. Building a call on that means offering to sell a stranger's flat. If onOffice explicitly lists the contact as owner or buyer, the property is still shown, under the heading **On file**.
  </FaqItem>
  <FaqItem q="Does a new scan overwrite the properties I entered?">
    No. Only entries **from the analysis** are replaced. Anything you entered yourself or confirmed with the check mark survives every further scan. That is why editing an AI entry automatically turns it into your own.
  </FaqItem>
  <FaqItem q="Can I turn a property lead into a real listing?">
    Deliberately not. Your property inventory is the list of what you hold a mandate for, and it feeds the exposé generator, the website and reporting. A placeholder built on a guess would be counted there as a mandate. Once the mandate exists you create the listing in onOffice, and it arrives through the sync.
  </FaqItem>
  <FaqItem q="Why does a run-through not skip contacts I just disqualified?">
    Because the queue is frozen at start. If it followed the list, the order would shift on every outcome and you would skip contacts without noticing. The stack therefore stays as it was. See [Durcharbeiten](/tools/db-leads/durchgang).
  </FaqItem>
  <FaqItem q="What happens to my leads when I uninstall?">
    They are kept, including findings and scan history. Actually deleting the data is a separate, explicit step.
  </FaqItem>
</Faq>

## Related

How a scan works: [Database scan](/tools/db-leads/datenbank-scan). What the tool costs: [Cost and add-on](/tools/db-leads/kosten). Back to the [overview](/tools/db-leads).