Buildium shadow sync
Discover eligible work orders, reconcile the latest source state, and stop when records conflict.
PilotRelease 1 · founding pilot
System / Maintenance resolution
One resolution desk between “approved” and “actually closed.”
Korrd reads eligible Buildium work orders, coordinates the parties, preserves evidence, routes approvals, and verifies the PMS record after writeback.
The resolution kernel
Agents propose. Policy authorizes. Connectors execute.
No AI agent receives direct credentials or free-form authority. A deterministic gateway checks identity, case version, evidence, consent, policy, approval, expiration, and idempotency before an external action.
Systems of recordBuildium first
Current work order, property, resident, vendor, task history, and supported files.
Korrd resolution kernel
Case stateNext actionEvidence
AgentsPolicyApproval
Execution channelsSMS · email · voice route
Human-approved pilot actions plus verified PMS writeback.
Reference implementation uses synthetic data. Live provider connections require client onboarding, registration, sandbox acceptance, and an approved production pilot.
What Release 1 installs
A complete maintenance-resolution corridor.
The pilot is intentionally narrow: one Buildium account, one market, one timezone, one approved vendor policy, and human review for consequential actions.
Risk interruption
Emergency, habitability, legal, accommodation, insurance, and dispute signals leave the routine flow.
PilotTwo-way SMS and email
Typed drafts, approvals, delivery state, replies, opt-outs, quiet hours, and separate participant threads.
PilotStructured coordination
Vendor response, resident windows, confirmation, expiry, conflict recovery, and secure action links.
PilotCompletion packet
Photos, notes, invoice references, resident confirmation, missing requirements, and file controls.
PilotVerified writeback
Show the exact Buildium diff, require approval, fetch current state, write, then read back.
PilotBounded maintenance agents
Specialists with evidence—not a swarm with passwords.
Each agent reads a minimized case packet and returns a typed proposal. The system rejects stale, unsupported, expired, or out-of-policy proposals before they can become actions.
Intake + safety
Extract known facts, unknowns, and interrupt conditions.
Resolution planning
Select the next dependency, responsible party, and due time.
Vendor coordination
Prepare availability, decline, progress, evidence, and invoice follow-ups.
Resident access
Prepare scheduling, reminders, completion checks, and dispute routing.
Owner + manager approval
Package evidence, estimate context, policy basis, and the exact decision requested.
Completion + invoice
Compare required proof, invoice references, and completion claims.
Closeout
Prepare the exact PMS change and identify closure blockers.
Exception + recovery
Handle failed delivery, timeouts, ambiguity, provider outages, and reconciliation.
Reporting
Summarize verified events, waits, approvals, and outcomes.
Release 1 messaging target
The transport is automated. The authority is controlled.
After provider registration, technical certification, legal review, and UAT, a founding pilot is designed to use one registered Twilio customer-care setup per client. Every outbound pilot message remains human approved.
Human-control model
No consequential action hides behind “AI handled it.”
What should happen
Typed action, evidence, assumptions, risk flags, and confidence.
What may happen
Consent, limits, permissions, approvals, case version, and kill switches.
Who authorizes it
Exact message, schedule, invoice context, or PMS diff.
What actually happened
Provider result, source-system read-back, and immutable audit event.
Platform roadmap
Maintenance first. Property operations over time.
Later releases are architecture and product direction, not claims of current availability. Each capability has its own proof gate.
Available nowR0
Synthetic product
Resolution desk, calculator, implementation method, trust model, and pilot readiness using fictional records.
Inspect before accessPilot targetR1
Buildium Maintenance Resolution
Shadow sync, bounded agents, SMS/email, call routing, scheduling, evidence, approvals, and verified writeback after production activation gates pass.
Not currently activatedPlannedR2
Omnichannel resolution
Bounded inbound AI voice, English/Spanish, owner approval portal, PWA, and live takeover.
Requires three successful R1 pilotsPlannedR3
Routine autonomous classes
Proven message classes, scheduling, evidence follow-up, estimate context, policy-bounded decisions, and low-risk closeout.
Requires shadow evidencePlannedR4
Multi-PMS platform
AppFolio first, then connectors justified by customer demand and official partner access.
Connector conformance requiredPlannedR5
Vendor + financial operations
Client vendor directory, evidence-backed matching, invoice controls, regulated payment partner, and PMS reconciliation.
Korrd never holds client fundsPlannedR6
Additional workflow packs
Turns and inspections first; leasing and collections only with their own fair-housing, legal, and compliance boundaries.
No general CRM replacementPermanent boundaries
Autonomy stops where authority, safety, or evidence becomes uncertain.
- Emergency
- Detect and route; never present repair or emergency diagnosis as fact.
- Legal authority
- Never impersonate an owner or manager or fabricate approval.
- Spending
- No unrestricted spend. Later policy-bounded actions still require valid client authorization.
- Sensitive cases
- Fair-housing, accommodation, legal threats, insurance, habitability, and disputes enter human review.
- Accounting
- Integrate with the client’s system of record; do not recreate the general ledger or trust accounting.
- Closeout
- Missing evidence, consent, or a conflicting source record blocks closure.
Start with the actual workflow
Bring 20 deidentified work orders. Leave with a resolution map.
The audit maps wait states, chase events, evidence gaps, policy gates, and where a controlled pilot could fit. Do not send resident records or credentials through the public site.