Present the property's published times unchanged from enquirer to enquirer, log the set that went out, and hold confirmation and access for the licensee who holds the written authorisation.
2Property status assembledOccupancy flag, written authorisation on file, tour modality and the published slot table
3Slot set presentedThe published times, the modality, the send record and confidence
4Controls appliedOccupancy and authorisation checks, parity against the published table, and the confidence threshold
No human action required
Stages 1 to 4 run unaided, and none of them is authorised to confirm a tour or issue a credential — the licensee's lane opens at the authorisation gate.
5DecisionSplits at the confidence threshold
High confidence
Goes to the named licensee to authorise.
Low confidence
Adds a property-manager read first.
Licensee authorisation
The request is held with the offered set, the occupancy flag and the authorisation on file.
Authorise · Decline · Send to property manager
Authorised — tour confirmed▼
6Showing systems updatedOnly where write access and authorisation policy allow it
7Outcome evaluatedSlot-offer parity, escalation outcomes, access events and post-tour incidents
Overrides
What the licensee changes at that gate is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Granting property access or issuing a lockbox or smart-lock credential.
Deciding that an enquirer may take a self-guided tour.
Adjudicating an identity-verification result from the vendor.
Confirming a tour on a tenant-occupied unit.
Automation boundaryAgent acts unaided
✓Present the uniform published slot inventory.
✓Send reminders for a tour already authorised.
✓Escalate occupied-unit and accommodation requests to the licensee.
✓Log the offered slot set and each access event to the audit store.
Any write happens inside the boundaries agreed at implementation, never ahead of the licensee's authorisation.
Varying the slot inventory offered to an individual enquirer.
Approving unaccompanied access in any jurisdiction.
Extending, reissuing or overriding a code expiry.
Answering substantive questions about the property during booking.
Example output
One enquiry, annotated
Everything the agent offers is attached to the inventory it was taken from.
Scheduling output · single enquiryIllustrative example
Enquiry
Offered slot set
Earliest slot
Authorisation
Confidence
Tour modality
Two-bed rental
The published set, sent whole and in the published order
Sat 10:00
Written authorisation on file
93%
Accompanied — licensee present
As receivedTaken from the published inventory and the authorisation record — nothing on this side is chosen by the agent.
Record checks usedOccupancy flagWritten authorisationPublished slot table
Why this slot setIt is the published set, unchanged for this enquirer — the parity the licensee owns.
ActionAuthoriseDeclineSend to property manager
What the score decidesBelow the threshold the request picks up a manager read before it reaches the licensee.
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
Every enquiryFrom the enquiry channel
03Scheduling
Offer the published set
Draw on the published slot table, the occupancy flag and the authorisation on file.
01Approved path
Offer the same slots to everyone
Routine requests on authorised properties come back with times attached.
02Human review
Send the licensee the risky ones
Occupied units, accommodation requests and failed verification are escalated, so the licensee's attention lands there.
04Build an evidence trail
Log the offered slot set, the modality and every access event, on both paths.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Showing schedulingShowingTime+ Aligned Showings
Rental self-tourRently Tenant Turner
Access and key controlSmartRent · PointCentral SentriLock · Supra eKEY
Agent
Showing & tour scheduling
Reads availability Presents the slots Holds for authorisation
Two cohorts sit above the review threshold while the aggregate still reads acceptable, which is why Nestack reports the slot-offer parity-failure rate by slice and by cohort, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Voucher-holder enquiries
3.9%
3.5×
Review
Accessible-tour requests
3.0%
2.7×
Review
Benign verification failures
2.0%
1.8×
Watch
Enquirers with an assigned agent
1.0%
0.9×
Normal
Bar: slot-offer parity-failure-rate lift vs. the all-enquiry baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
No cycle closes without a new test
A failure leaves behind a paired-slot regression case the next release has to pass. That suite is what the following detection is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Slot-offer parity drops in an enquirer cohort.
02Diagnose
When the gap widens past the configured threshold, the paired outbound logs are read side by side until the cause is one.
03Improve
A version stamp and the paired logs travel with the correction.
04Verify
The paired-slot cases are re-run before anything ships.
05Learn
Both the regression suite and the scheduling policy carry it from then on.
Learn → DetectThe return edge. The next detection runs against a suite one case larger.
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, scheduling workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Showing workflow discovery and boundary definition.
02Showing, tour and access-system assessment.
03Authorisation, occupancy and entry-notice rule mapping.
04Slot-inventory ingestion and normalisation.
05Uniform-offer logic and parity checks.
06Confidence scoring and escalation routing.
07Licensee authorisation workflow.
08Showing and access-system integration.
09Paired-slot regression cases.
10Credential and authorisation guardrails.
11Observability and trace instrumentation.
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 market, one officeProductionProduction showing systemsAdvancedMulti-market inventory
Introduced at Pilot
Uniform slot presentation✓✓✓
Licensee authorisation✓✓✓
Parity baseline✓✓✓
Introduced at Production
Paired-slot reporting—✓✓
Escalation workflow in your systems—✓✓
Approved calendar write-back—✓✓
Access-event logging—✓✓
Introduced at Advanced
Multi-state and MLS rules——✓
Multi-stage brokerage approvals——✓
High enquiry volume——✓
Enterprise user and role 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 published slot inventory and calendar rules→Slot-inventory ingestion and channel mappingWeek 1
02Representative enquiry threads→Offer baseline, parity checks and cohort definitionsWeek 2
03Your lockbox authorisations and access policy→Access-policy mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Showing, tour and access-system assessment, then integration setupWeek 2
05Bookings you had to undo→Paired-slot regression cases and failure-mode testingWeek 4
06What must reach a person before a slot is confirmed→Confidence scoring, escalation routing, guardrails and approval controlsWeek 3
07Named licensees and property managers to authorise→Authorisation workflow, then pilot properties and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases sit on the weeks they occupy. Week 5 carries two bars because evaluation and pilot overlap.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Showing workflow discovery, access-policy mapping and the automation boundaryW2Source integration and the uniform-offer baselineW3How a slot is offered, when it escalates, and who authorisesW4Paired-slot testing, credential-expiry checks and the evaluation suiteW5Access systems connected, pilot properties and the corrections they surfaceW6A week of live bookings under authorisation, then Agent Care takes over
Reading the bandWeek 5 shows two bars because two phases actually run in it, not to fill the row.
At the end of W6Once validation closes, Agent Care owns the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a showing agent around your access-authorisation chain.
Show us your slot inventory, your written authorisations and who holds them. A tour that happened cannot be un-happened, so we map the scheduling workflow, set the automation boundary and name what stays with the licensee.
