What initiated the work?
Category, priority, approval, PMS status, assigned vendor, and known exceptions.
Method / From operating truth to controlled resolution
Map the chase before automating the message.
Korrd begins with the work as it actually happens: who waits, who decides, what evidence matters, where consent applies, and what must never proceed unattended.
Five gated stages
No live action until the preceding proof exists.
- 01AuditOutput: resolution map + baseline
Trace 20 deidentified work orders.
Map elapsed time, chase events, participant handoffs, evidence gaps, closeout defects, and manager intervention.
- 02ConfigureOutput: versioned policy pack
Turn operating judgment into policy.
Document eligible categories, interrupt conditions, vendors, contact windows, approvals, spending boundaries, evidence, and escalation.
- 03ShadowOutput: UAT evidence + corrections
Read the work without touching it.
Reconcile Buildium, build case state, draft next actions, and compare Korrd’s proposal with the team’s real decision.
- 04ApproveTarget output: activated L2 pilot
Coordinate through a human gate.
After all activation gates pass, enable registered channels. A person reviews every outbound message, schedule commitment, approval request, and source-system write.
- 05ProveOutput: keep, change, or stop decision
Promote only exact, stable classes.
Measure edits, safety, identity, consent, delivery, cycle time, and operator effort before one routine template class earns automation.
The 20-work-order audit
Small input. Operationally complete view.
Korrd does not need a data dump to establish fit. The first pass uses deidentified timeline facts and aggregates supplied through an agreed secure process.
Who owed the next response?
Manager, vendor, resident, owner, or another team—and for how long.
What did the team have to chase?
Calls, texts, emails, reschedules, status checks, repeated explanations, and corrections.
What proved completion?
Photos, notes, invoice, resident confirmation, inspection, or an alternate policy-defined proof.
Which decision needed authority?
Vendor choice, access, estimate, owner approval, spending, dispute, cancellation, or closure.
Did the PMS reflect reality?
Close date, status, evidence, invoice reference, reopen, and what remained unresolved.
Policy before prompts
The client’s operating rules become versioned system inputs.
- Eligibility
- Which approved routine categories may enter Korrd, in which market and property types.
- Interruptions
- Emergency, habitability, accommodation, legal, insurance, access, or dispute signals that pause automation.
- Participants
- Authorized vendors, client staff, owner approval routes, resident contact rules, and identity boundaries.
- Communication
- Consent evidence, quiet hours, message classes, reminder limits, language, channel preference, and opt-out handling.
- Decisions
- Vendor assignment, estimate, spend, access, approval, schedule, cancellation, reopen, and escalation authority.
- Closeout
- Required photos, notes, invoice references, confirmation, approvals, status mapping, and read-back verification.
Autonomy ladder
Capability advances by evidence, not enthusiasm.
A tenant can pause agents, SMS, email, voice, scheduling, PMS writes, estimates, financial actions, auto-close, or an entire workflow pack independently.
Synthetic
Fictional cases and simulated integrations.
Available nowShadow
Read current records and compare proposals with real decisions.
Pilot stageHuman approved
Target state after certification: real channels and writes with every consequential action reviewed.
Pilot targetClass limited
Only exact routine actions that satisfy promotion thresholds.
PlannedRoutine resolution
Policy-bounded coordination with sampling and kill switches.
FutureClient inputs
Operational facts—not credentials in a form.
Production onboarding happens only after agreement, through scoped secure channels. The public application collects company-level fit information only.
Before the auditDoor count, PMS plan, work-order volume, markets, team structure
Before shadow modeDeidentified examples, policy owners, categories, vendors, evidence standards
Before live messagingConsent basis, approved disclosures, Twilio registration facts, quiet hours, templates
Before writebackRestricted Buildium access, field allowlist, approvers, UAT evidence, rollback owner
Start with operating truth
The first deliverable is clarity, not a login.
Request a deidentified 20-work-order audit to see where resolution time is actually accumulating and whether the founding pilot fits.