Take maintenance intake verbatim, triage it against the repair clock configured for that jurisdiction, and hold dispatch, closure and lead-regulated scope for the licensed property manager, who decides.
Collect the report verbatim, with photos, access notes and pets on site, from the portal, phone and SMS channels.
02
Collect the unit's construction-year and vendor records from the systems of record, each carried with its source.
Reason
03
Classify urgency against the repair clock and heating-season rules configured for that property's jurisdiction.
04
Classify any life-safety trigger straight to the on-call supervisor, without waiting for a second signal.
05
Classify a pre-1978 or unsourced-year unit as lead-regulated scope, which only a certified firm may narrow.
Decide
06
Dispatch against a vendor record re-checked for licence, insurance and scope class at dispatch time.
07
Dispatch nothing a human has not approved, and leave the order open until that human closes it.
Out
08
Retain the verbatim text, the photos, the notice sent, the vendor checks and the approving human.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent triages and prepares the order; the licensed property manager decides what dispatches, and the repair duty stays the owner's.
Example workflow
One ticket, intake to dispatch
AgentHuman
1Report receivedPortal, phone, SMS or on-site report from the tenant
2Record assembledVerbatim text, photos, unit history, construction-year source and vendor status
3Urgency proposedCategory, proposed route, the clock that applies and confidence
4Controls appliedLife-safety trigger list, lead screening, vendor re-checks, entry-notice rules and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is dispatched at any of them — the agent is preparing the order, and the manager's lane opens at the confidence gate.
5DecisionSplits at the confidence threshold
High confidence
Goes to the property manager to approve.
Low confidence
Adds an on-call supervisor read first.
Manager approval
The order is held with its verbatim text, its triggers and the confidence.
Approve dispatch · Reprioritise · Send to on-call
Approved — released to dispatch▼
6Work-order system updatedOnly where write access and approval policy allow it
7Outcome evaluatedReclassification rate, clock adherence, vendor checks and repeat reports
Reclassifications
Reclassifications made in review are counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Determining whether the RRP rule applies to a scope.
Dispatching paint-disturbing work in pre-1978 housing.
Classifying or reclassifying a life-safety condition.
Approving a vendor whose licence or insurance is unverified.
Automation boundaryAgent acts unaided
✓Collect structured intake — unit, access, pets, verbatim text, photos.
✓Confirm a window a human approved with a verified vendor.
✓Send status updates from the system of record.
✓Prompt the tenant to confirm the work once it is marked complete.
Every dispatch waits for the approval boundaries agreed at implementation to allow it.
Closing, deferring or cancelling a habitability work order.
Authorising entry, or invoking the emergency exception.
Deciding an accommodation inside a repair request.
Advising on repair-and-deduct or rent withholding.
Example output
One ticket in the queue, annotated
Everything the agent proposes is attached to the report it was drawn from.
Triage output · single work orderIllustrative example
Unit
Reported condition
Year built
Proposed route
Confidence
Approval held for
Garden duplex, unit B
Ceiling stain spreading in the back bedroom, paint now flaking
1962
Certified-firm queue
88%
Licensed property manager
As receivedTaken from the tenant's report and the property record — nothing on this side is written by the agent.
Signals usedVerbatim tenant reportPhotos attached at intakeUnsourced year record
Why this routeThe year-built source is unsourced, so the scope routes as lead-regulated.
ActionApprove dispatchReprioritiseSend to on-call
What the score decidesBelow the threshold the ticket picks up an on-call read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
All ticketsFrom the intake channels
03Triage
Triage against the record
Draw on the unit's history, the construction-year source and the jurisdiction's clock.
01Approved path
Get emergencies to a person faster
Routine repairs arrive scoped, with the intake already structured.
02Human review
Send the urgent ones to a human first
Life-safety triggers and low-confidence tickets are marked, so the on-call read starts where harm concentrates.
04Build an evidence trail
The intake text, the photos, the triage class and the dispatch record stay with the ticket.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Pre-1978 units with a child under six absorb most of the mis-triage long before the aggregate rate moves. Nestack reports the emergency mis-triage rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Pre-1978 units, child under 6
5.4%
2.7×
Review
Accommodation-adjacent
4.2%
2.1×
Review
After-hours heating season
2.4%
1.2×
Watch
Scattered-site single-family
1.0%
0.5×
Normal
Bar: emergency mis-triage-rate lift vs. the all-ticket baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle is not closed until a test exists
Nothing closes until the failure is a regression case the next release has to clear. The suite it joins is what the next detection is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Emergency mis-triage rate rises in a property cohort.
02Diagnose
The ticket, its photos and the record behind it are read together until one cause remains.
03Improve
The fix lands against a version, with the reclassifications that prompted it attached.
04Verify
Nothing releases until the affected regression cases pass again.
05Learn
The case joins the permanent suite and the firm's triage rules.
Learn → DetectThe return edge. The next detection runs against a suite that is one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, triage workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Maintenance intake discovery and boundary definition.
02Work-order and vendor source assessment.
03Jurisdiction clock, lead-screening and trigger-list mapping.
04Ticket ingestion and verbatim-record capture.
05Triage logic and property-record binding.
06Confidence scoring and escalation routing.
07Manager approval workflow.
08Work-order and vendor-system integration.
09Regression cases and the evaluation suite.
10Guardrails and dispatch controls.
11Trace instrumentation and observability.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne portfolio, one marketProductionProduction work-order systemsAdvancedScattered-site portfolios
Introduced at Pilot
Triage to your clocks and rules✓✓✓
Manager approval✓✓✓
Triage-accuracy baseline✓✓✓
Introduced at Production
Triage reporting by property type—✓✓
Dispatch approval in your systems—✓✓
Approved write-back—✓✓
Dispatch and vendor logging—✓✓
Introduced at Advanced
Multi-state clock and lead rules——✓
Multi-stage dispatch approvals——✓
High ticket volume——✓
Enterprise vendor controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your intake channels and ticket fields→Ticket ingestion and verbatim-record captureWeek 1
02Representative closed work orders→Triage baseline, trigger-list extraction and record bindingWeek 2
03Your emergency list and jurisdiction clocks→Clock, lead-screening and trigger-list mappingWeek 1
04Access to relevant APIs, feeds or exports→Work-order, vendor and inspection assessment, then integration setupWeek 2
05Tickets that were reclassified after closure→Regression cases, evaluation suite and failure-mode testingWeek 4
06Your dispatch thresholds and write-back limits→Confidence scoring, escalation routing, guardrails and dispatch controlsWeek 3
07Named managers and on-call supervisors→Manager approval workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they occupy. Week 5 carries evaluation and pilot together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Intake discovery, clock mapping and the automation boundaryW2Source integration and the triage baselineW3Triage workflow, confidence logic and dispatch controlsW4Evaluation suite, lead-screening checks and failure-mode testingW5Vendor-system integration, pilot tickets and targeted correctionsW6Production validation on live tickets, then Agent Care handover
Reading the bandA bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6Everything verified in production, with Agent Care carrying it forward.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a maintenance-triage agent around your on-call chain.
Show us your intake channels, your vendor bench and who is on call. If your after-hours tickets wait for a human until the morning, that is where we set the automation boundary.
