Street
How a visitor reaches the property and the first controlled entrance.
Security at Botway
Security isn't a feature. It's infrastructure.
Botway is rebuilding how a brokerage runs around software, AI, and connected properties. Owners need to trust the system protecting their homes, so tested routes, clear permissions, and human accountability come first.
A modern brokerage needs a new access layer.
Traditional brokerage relied on someone carrying keys. Online scheduling, remote owners, and connected buildings change what is possible. Access has to become more controlled as the brokerage becomes more connected.
01
Know the property before the showing.
- Street, building, interior barriers, and unit are assessed separately
- Occupancy, authority, and building permission are part of the plan
- A changed configuration needs a new staff test
02
Keep people accountable.
- Staff test the complete route before remote access is enabled
- Owners can disable access at any time
- Tenant-occupied homes stay outside the self-guided path
03
Make the software enforce the rules.
- Native vacant instant bookings require a live access plan
- Confirmation also requires verification for that appointment
- A booking or doorbell event never grants entry on its own
04
Let AI assist, never authorize.
- AI can gather answers in chat and on calls
- Staff resolve permissions and attest to the test
- No AI model can enable access or open a door
Every property has its own security architecture.
A Brooklyn apartment with a buzzer is different from a Connecticut house with a doorbell. A vacant listing is different from someone's home. Botway maps the entire route before deciding whether remote access is appropriate.
Building
Doorman, virtual doorman, intercom, buzzer, fob, or another approved method.
Inside
Vestibules, elevators, floor restrictions, and any second barrier.
Unit
The unit door has its own method and authorization requirements.
Secure again
The staff test covers securing the unit again, and the plan says what happens if the route fails.
Plan it. Test it. Then trust it.
Owner onboarding asks how people enter, who can authorize them, what the building permits, and whether anyone lives there. Botway turns those answers into a property-specific Access Plan in the Console, with open issues and a backup route.
Configured does not mean ready. Staff must attest to a test of the exact route before remote access can be switched on. A changed answer clears that test and switches access off again. Owners can switch it off themselves.
Botway Console
14 Orchard Row · Unit 3B
Access plan built from the owner’s onboarding answers
Street to unit
- Occupancy
- Vacant
- Street to building
- Virtual doormanTested
- Interior barriers
- Elevator pass for visitorsTested
- Unit entry
- Controlled lockboxTested
- Building permission
- Confirmed by management
- Unit authority
- Owner confirmed
Controls
Remote self-showingsOn after a passed test. The owner can switch it off.
- Prospect verificationRequired
- Open permissionsNone
- Ring doorbellReported, not connected
Activity
- Staff enabled remote self-showings
- Staff recorded a passed street-to-unit test
- Owner changed building entry; earlier test cleared
- Owner answered the access questions by email
Try the switch. Fictional property and data.
Access belongs to a person, a property, and a time.
A scheduled appointment is not permission to enter. Native vacant instant showings require a live Access Plan and a verified prospect tied to the exact appointment before confirmation.
What works today. Booking rules check the property plan and the appointment's verification record. If either condition is missing, confirmation does not proceed. There is no native prospect-verification provider yet, so these bookings remain pending verification in the current workflow.
What we are building. Arrival confirmation, supported identity checks, and short-lived credentials could make permission more precise. A photo ID check, payment card check, doorbell event, or credential alone will never be treated as complete authorization.
If Botway isn't sure, the door stays closed.
A change to the Access Plan switches remote access off. If a route fails or permission is uncertain, the plan calls for an assisted showing or a new time. Uncertainty does not become permission.
Tenant-occupied homes never enter the self-guided path. Showing access requires the tenant's approval or authorized onsite staff. Technology does not override someone's control of their home.
AI can understand the plan. AI doesn't get the keys.
AI can collect an owner's answers in chat or on a call. Fixed rules turn those answers into the Access Plan and list what is still missing for staff. AI cannot decide that someone should enter a property, enable remote access, or open a door.
Access decisions depend on explicit rules, the property's current state, permissions, and an attested staff test. AI assists. Authorization governs.
Security also protects information.
No codes or passwords in onboarding. We ask how access works, not for a door code, alarm code, key, or password. Access secrets should not be entered into the plan.
Private links, stored as fingerprints. An owner’s onboarding link is private to their property. We keep only a one-way fingerprint of it, never the link itself.
Nothing sensitive in verification. Prospect verification records never hold Social Security numbers or ID images.
Role-based access, with a record. Owners and staff see only what their role allows. Access changes are logged; a private onboarding link is recorded as a link action rather than attributed to a signed-in owner. Read our privacy policy for the rest.
Work with the building you have.
Botway is building a brokerage layer around the property's existing access systems and the people responsible for them. A doorman, intercom, or staff escort can be the right controlled route. A published API is an option to evaluate, not proof that a connection is ready.
Ring
Brivo
DOOR / Latch
Kisi
ButterflyMXRing, Brivo, DOOR / Latch, Kisi, and ButterflyMX publish APIs or partner platforms. Botway has not connected their devices or enabled remote entry through them. Each future connection requires provider access, owner and building permission, and a full-path staff test.
Provider connections
Direct integrations with access and intercom systems are in development. A logo or available API does not authorize a showing or make the property ready.
People and existing systems
A doorman, building staff member, intercom, visitor pass, staff escort, or controlled lockbox can be part of a documented route. Staff test the full path before the plan is marked ready.
Ring is a signal, not a key
A future Ring connection may provide authorized activity signals. Seeing someone at a door cannot decide whether that person may enter. Ring events never serve as an unlock command.
What works today. What comes next.
Every new capability has to earn its place in the access system through permission, authorization, and real-world testing.
Live today
- Access plans built from owner onboarding
- Staff full-path tests and the remote-access switch
- Owner switch-off from their private onboarding link
- Booking and verification checks for native vacant instant showings
- Occupied homes routed to tenant-approved or staff-led showings
- Owner onboarding listings held inactive on our showing partner until access is ready
In development
- Prospect arrival confirmation at the door
- Short-lived access credentials
- Direct lock and buzzer commands
- Ring, Brivo, DOOR, Kisi, and ButterflyMX connections
- Direct photo ID and payment card checks through supported providers
Availability will depend on each property and its providers.
Security is in the DNA.
Because real estate is becoming software. And homes are not ordinary software endpoints.
The next generation of brokerage needs trust, identity, and physical access infrastructure that respects the people who live in and own these spaces. Tell us about your property and we'll start with the access questions.