Property managers and small forwarders spend hours each week on the same chain: find a craftsman, wait for a quote, agree a date, get a tenant to let someone in, or find a free ramp slot at the customer's warehouse, then tell everybody what was agreed. An agent runs this chain: it writes the order, chases the answers, proposes dates, books where a portal allows it and keeps a visible status. Email and phone coordination works today; automated booking on third-party portals is still fragile.
Problem & value
- Today: a clerk in the property management (Hausverwaltung) reads the damage report, picks a trade firm, sends the order, calls to ask for a date, calls the tenant, repeats when the tenant is absent, and records everything by hand. In a forwarding company the dispatcher books customer ramp slots by phone, email or each customer's own portal. Every case is a thread of many small waiting steps.
- AI value: the work is mostly waiting and chasing, which an agent does without getting tired: sending the order from a template, reminding after a deadline, proposing alternative dates, writing clear notices to tenants and tracking what is still open. The human decides about money, owner consent and exceptions.
- Time at stake (internal estimate, not a measured benchmark): the gap analysis of this catalog puts about 10 h (commissioning and tracking contractors) plus 8 h (ordering a craftsman and arranging access) in the Hausverwaltung process and about 7 h (customer ramp slots) in the Spedition process into this step [4]. No independent time-saving study for such coordination agents was found.
- Ramp slots as proof of the pain: slot booking systems exist because waiting at the ramp is costly. A 2012 survey of 41 firms, commissioned by a slot-system vendor, reported shorter waiting times at the ramp; the same vendor states such systems support but cannot replace a good process [3].
Variants
- Hausverwaltung / WEG and rental management: damage report → trade firm → tenant access → report and invoice hand-over. Owner consent for costs above a limit is part of the flow.
- Facility management and housing companies: same chain at higher volume with framework contracts.
- Spedition and carriers: book and re-book unloading or loading slots at consignees, inform the driver, react to delays; see AGENT-024 for the shipment side.
- Handwerk and service companies: coordinate subcontractors and customer appointments.
- Private use: a household coordinating craftsmen for renovation; see AGENT-019.
How it works
- trigger (damage report, inspection finding, order, slot requirement)
- case creation + classification (trade, urgency, emergency?, owner consent needed?)
- contractor selection (framework contract, trade, region, availability; human confirms above limit)
- order or quote request by email/portal with photos and access information
- follow-up loop (reminder after deadline, escalation, alternative contractor)
- date proposal (contractor calendar + tenant/consignee availability + notice rules)
- access arrangement (written notice to tenant, key or caretaker, or slot booking on portal)
- confirmation to all parties + reminders before the date
- completion check (report, photos, invoice hand-over) + log in the property or transport system
- Core logic is a state machine. The case states (requested, quoted, ordered, date agreed, done) and deadlines are deterministic workflow code; the LLM reads replies, drafts messages and extracts dates and prices. It should not decide spending or legal steps by itself.
- Channels: email is the main channel; voice calls to craftsmen can use CONV-008 style outbound agents, but many tradespeople answer only the phone or WhatsApp, which limits automation.
- Portals: where a consignee offers a booking portal without API, a computer-use agent (AGENT-003) can fill the form, but layout changes, logins with two-factor codes and captchas break it.
- Human-in-the-loop: approval of orders above a spending limit, owner consent, emergencies, any access to a flat without the tenant present, and complaints from tenants.
Data preparation
Which data: contractor master data (trades, contacts, framework prices, response times), buildings and units, tenant and owner contact data, open orders, house rules, and for forwarders the list of consignees with their ramp rules and portals.
Where it lives: property management software (for example Aareon, Haufe, Lexware, immoware24 or smaller tools; vendor names are examples, not individually verified; at least some products list contractor and appointment management [2]), ERP or TMS for forwarders, Outlook or Google calendars, shared mailboxes, and a lot of knowledge only in the heads of clerks.
Typical gaps: outdated contractor lists, missing trade categories, tenant phone numbers and email addresses not maintained, no rule who may order up to which amount, no record of who has keys, and consignee booking rules that are not written down anywhere.
Preparation steps: 1. Clean the contractor master data and add trade, region, framework terms and a reliable contact (PREP-005). 2. Write the ordering rules: spending limits, owner consent, emergency cases, preferred firms (PREP-016). 3. Define the access rules per building (notice period, key holder, caretaker) and consignee rules per customer. 4. Collect 30-50 real past cases with the email threads as test set (PREP-018). 5. Give the agent only the mailbox and system access it needs (PREP-023, PREP-024).
Tools: export from the property or transport system, spreadsheet for rules, shared mailbox.
Rough share of effort: about 30 percent of the project; master data and written rules matter more than model choice. See GUIDE-003.
Implementation paths
Which path for whom
- SMB - Path B: the property manager or forwarder has a standard system but needs its own rules and mailbox workflow; a workflow tool plus a cloud LLM API is cheaper and more flexible than a niche product.
- Enterprise - Path B: large housing companies and logistics groups have ticketing and portals already; they add an agent layer with their own approval and logging rules.
Path A - Buy (off-the-shelf)
- Built into property management software: contractor management, order tracking and appointment functions exist in German products [2]; AI-based autonomous chasing is so far limited to add-ons.
- Damage-report and repair-portal tools for tenants and trades (QR-code damage reports, craftsman platforms) cover intake and ordering, but rarely the full chase and access loop.
- Slot-management systems for ramps (for example Cargoclix and similar) serve the consignee side; the carrier side usually still books manually [3].
- Choose A when: the existing software vendor already offers the workflow and you accept its channels.
Path B - Build on cloud APIs (recommended)
- LLM with tool calling from an EU provider or an EU region endpoint; orchestration in n8n, Power Automate or an agent SDK; case state in a database or the property/transport system via its API.
- Mail and calendar via Microsoft Graph or Google APIs with least-privilege scopes (see AGENT-001, AGENT-012).
- Portal booking via official APIs where they exist; otherwise AGENT-003 as fallback with a manual override queue.
- Choose B when: you need your own rules and several channels but no on-prem constraint.
Path C - Self-host (open source)
- n8n self-hosted, open-weight instruction models (Qwen, Mistral and similar) via Ollama or vLLM on HW2, mail via IMAP and calendars via CalDAV. Sensible for municipal housing companies or when tenant data must not leave the own data centre. Effort rises mainly for integration and monitoring.
Path D - Custom training
Rarely needed. A small ranking model for contractor choice (response time, cost, quality) can learn from own history; the language part works with prompts.
State of the art (2026)
- Works today: drafting orders and notices, extracting dates and prices from replies, reminders and escalation, status summaries, and rule-based selection from a contractor list. These are building blocks already proven in AGENT-001, AGENT-002 and AGENT-012.
- Partly works: phone coordination with tradespeople by voice agents (CONV-008) and booking on external portals through browser agents (AGENT-003); both depend on the counterpart and break often.
- Not solved: negotiating with another party's agent, judging quality of the finished work from photos without a human, and reliable handling of tenants who are unreachable or in conflict with the landlord.
- Limits and failure modes: wrong date or wrong flat, a notice that does not meet legal form, a contractor order placed without the owner's consent, double booking, prompt injection through incoming emails, and tone problems with tenants. Treat the maturity as early-adopter: pilots work, a fully autonomous end-to-end loop is not yet common.
Shared resources & combinations
- Same stack (llm-general + agent-framework + workflow-automation): AGENT-001 inbox triage (requests arrive by email), AGENT-002 workflow automation, AGENT-012 calendar agent for date search; one workflow engine and mail connection serves all.
- Voice and browser building blocks: CONV-008 (outbound calls), CONV-002 (inbound calls from tenants), AGENT-003 (portal booking).
- Upstream/downstream: AGENT-005 (quotes and supplier communication in procurement), DOC-006 (delivery and logistics documents), AGENT-024 (freight and carrier operations), AGENT-025 (governance and logging of the agent fleet).
- Biggest combined effect: inbox triage + this agent + calendar agent remove most of the waiting steps in one chain; do not start with the voice or portal parts.
Effort, cost & KPIs
- Path A: weeks, if the vendor offers it; priced per unit or per user.
- Path B: 2-4 months for a pilot with email and calendar for one process (for example repair orders), then more channels; low API cost per case compared with clerk time.
- Path C: 3-5 months including hardware and operations.
- KPIs: time from report to confirmed date, number of manual follow-ups per case, share of cases closed without clerk intervention, rate of missed appointments (tenant absent, contractor no-show), tenant and contractor satisfaction, waiting time at the ramp for the forwarder.
People & change
Involve early: management (spending and liability rules), the head of property management or dispatch as process owner, clerks and dispatchers as daily users, IT for mailbox and system access, and the DPO because tenant and consignee contact data is processed. Contractors and tenants are affected parties and should be told how the agent communicates (GUIDE-005, GUIDE-008).
Works council: depends. The agent logs who handled which case and how fast, which makes it objectively suited to monitor performance under §87(1) no. 6 BetrVG if a works council exists; inform under §90(1) no. 3. Agree that case logs are not used for individual performance control (GUIDE-004).
AI literacy: Art. 4 AI Act; train clerks on what the agent may send, how to read the log and when to take over (GUIDE-006).
Communication and pilot: start with one process and a few buildings or customers in suggestion mode (clerk approves each message), then let the agent send reminders alone, later date proposals. Name an owner for the contractor list. Typical concerns are tone toward tenants and liability for wrong orders; answer with templates, spending limits and a visible activity log (GUIDE-009, GUIDE-013).
Humans in control: orders above the limit, emergencies, access to flats and any dispute stay with people.
Risks, regulation & compliance
- EU AI Act: limited risk. The agent writes and may speak to natural persons (tenants, tradespeople, drivers). Art. 50 requires that people are informed they interact with an AI system unless it is obvious; the Commission applies this to AI agents, it applies from 2 August 2026 and the "obvious" exception is read narrowly [1]. Disclose it in the first message and in every voice call. No Annex III category as long as it is not used to rate employees.
- GDPR: tenant and contractor contact data, access and absence information (when nobody is at home) are personal data. Legal basis is mostly contract performance (Art. 6(1)(b)) and legitimate interest; sign an AVV (Art. 28) with the provider, keep data minimal in prompts and logs, define retention.
- Tenancy law: tenants must tolerate maintenance measures under §555a BGB, but the landlord must announce them in good time; notice is not needed for trivial or urgent measures [5]. Modernisation measures follow stricter notice rules (§555c BGB). Set the notice templates and periods with legal advice and keep a record of delivery. In WEG cases, owner resolutions and the manager's authority (WEG law) limit what may be ordered.
- Liability and commercial law: an order is a binding contract. Limits on amount and trade, owner consent and a four-eyes rule on exceptions are required; log every sent message for proof.
- Security: prompt injection through emails from outsiders, mailbox access with narrow scopes, no automatic change of contractor bank details, kill switch.
- Portal terms: automated use of third-party booking portals may violate their terms; prefer official APIs or ask the customer.
- Mitigations: tiered autonomy, templates for legal notices, human approval for money and access, audit log.
Getting started
- Pick one process with clear volume, for example repair orders for one portfolio or ramp slots for the five biggest customers, and measure the baseline (touches and days per case).
- Write down ordering, notice and escalation rules; clean the contractor list.
- Run suggestion mode on email only for four weeks; review every draft.
- Add reminders and date proposals; add voice or portal booking only after the email loop is stable.
- Review disclosure texts, privacy and works agreement before going live.
Sources
- European Commission - Transparency obligations under Article 50 AI Act (FAQ) - https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act
- Softguide - Hausverwaltung software listing (contractor, supplier and appointment management) - https://www.softguide.de/programm/hausverwaltung
- Verkehrsrundschau - Zeitfensterbuchung verkuerzt Wartezeit an der Rampe (vendor-commissioned survey) - https://www.verkehrsrundschau.de/nachrichten/transport-logistik/zeitfensterbuchung-verkuerzt-wartezeit-an-der-rampe-3007249
- Internal gap analysis of this catalog - research/gaps_2026-11_shadow.md, candidate AGENT-038
- Buzer - Text of section 555a BGB (Erhaltungsmassnahmen, duty to tolerate and announce) - https://www.buzer.de/555a_BGB.htm