The acquisition agent is the status engine of DB-Leads: it works through each contact's activities, understands in context where the person stands, and sorts the lead into the right pipeline phase on its own. It answers "where in the process is this contact?", while the database scan answers "how likely is a sales mandate here?". Together they make up owner mining.
What it does
Instead of just static contact fields, the agent reads the connected activity history from onOffice (emails, calls, appointments, portal inquiries, notes) and evaluates them in context:
Understand activities
How recent is the last contact? Who wrote last (inbound/outbound)? Is interest escalating or has it gone quiet?
Derive status
That yields a clear status: New, Engaged, Hot, Scheduled, Negotiating, Dormant, Lost, or Won, each with evidence from the activities.
Sort automatically
The agent assigns the lead to the matching phase of your pipeline: automatically, as a suggestion, or not at all, per your setting.
Reproducible & AGG-compliant
The status is derived deterministically from behaviour (never personal characteristics): same activities, same result.
How it flows
Import activities
The onOffice sync pulls each contact's activities alongside the addresses (see onOffice import). It is the same data foundation the database scan uses.
Qualify
On the AI briefing (single, inside the database scan, or automatically after a sync) the agent works through the activities and derives the status.
Sort
Based on the status the agent recommends a pipeline phase and applies it according to your automation setting. When you accept a finding from the scan, the lead moves into the recommended phase as well.
Automation setting (per workspace)
Under Settings → REOS AI you decide how the derived phase is applied:
Staying current automatically
A sync fetches data, it does not rate anyone. If you want new and changed contacts assessed without lifting a finger, set the auto-scan under Settings, Database scan to daily, weekly or monthly. Every automatic run syncs with onOffice first and then rates only the contacts where something happened since the last assessment. Data first, rating second, never the other way round. The scan analyses are included in the DB-Leads add-on.
Which activities count
Under Settings → Qualification → Context you define which activity types feed the assessment. Without rules all activities count; with rules only the matching ones.
Status at a glance
The derived status is visible everywhere: as a chip in the list and board, prominently on the customer view (with evidence and last activity), and as a dedicated status filter in the list, so you can work through, say, all "hot" leads at once.
Frequently asked questions
How status and seller score relate, who decides about a lead and what works without an AI provider: Questions and answers.