Services

All services, one coordinated platform

INSSNAPP is a real-time leasing coordination layer for occupied residential units. These are the services being built for the pilot — management remains the system of record for property and unit eligibility throughout.

Showing Engine coordination

The authoritative state machine behind every showing: AVAILABLE → REQUESTED → RESIDENT_ACCEPTED → BROKER_GATE → CONFIRMED → IN_PROGRESS → COMPLETED → OUTCOME.

Unit-level locking prevents double-booking
Idempotent transitions — safe retries
Role policy enforced on every transition
Immutable audit event for every material step

Management web portal

The desktop operations surface for property management teams.

Dashboard and live showings monitor
Properties, units, and eligibility
Resident enrollment and participation
Basic reports and PMS connection status

Resident mobile experience

One-screen workflow for the current tenant.

Available NOW toggle
Incoming request inbox
Accept / decline with one tap
Live status, completion, and rating

Prospect mobile experience

One-screen workflow for the prospective tenant.

Eligible unit discovery and details
Request showing without resident contact details
Live request and tour status
Apply / Watch / Decline outcomes

Broker mobile experience

One-screen workflow for broker participation.

Assignment queue
Accept / decline assignments
Check-in support for the showing
Completion and rating

Control Center

The INSSNAPP super-admin surface for platform operations.

Organization overview
Workflow monitor and engine health
Integration status
Audit log and security events

Mobile

One Expo codebase, three experiences

One Expo codebase powers the resident, prospect, and broker experiences — role-based views on iOS and Android, designed as one-screen workflows.

Resident

Available NOW toggle, accept/decline, live status.

Prospect

Discovery, request showing, Apply / Watch / Decline.

Broker

Assignment queue, check-in, completion, rating.

Design principles

Built for trust in occupied units

Resident stays in control

Showings only move forward when the resident accepts. Private resident contact information is never shared with prospects.

Engine is the authority

The Showing Engine is the sole authority for state changes — portals and mobile apps request transitions; they don't make workflow rules.

No double-booking

Confirmation locks the unit so conflicting active showings can't overlap; completion releases the lock.

Auditable by design

Every material transition emits an immutable event with actor, organization, timestamp, and state change.