One resident-facing system
Sentus Home gives residents one place for the day-to-day interactions that should not require multiple portals, call-backs, and repeated explanations.
Sentus Home
Resident experience that stays connected to the operation.
Sentus Home gives residents one place for payments, maintenance requests, messages, documents, and service status without cutting them off from the real operating workflow.
How It Runs
Everything a resident needs, in one place.
- 01
Residents submit requests, review status, and access documents in one place.
- 02
Requests connect directly into Sentus Ops instead of becoming retyped tickets.
- 03
Messages and updates stay tied to the same operating event.
- 04
The resident sees progress without waiting on a manual callback.
- 05
Every step stays attached to Sentus Thread.
Why Buyers Care
Home proves Sentus can handle the resident-facing layer cleanly.
That matters because the market already expects resident portals. The differentiation comes from how well that portal connects back to the operating system.
Better service visibility
Residents should be able to see progress and context instead of sending follow-up messages into a black box whenever maintenance or billing questions surface.
A stronger bridge to operations
Home works because it is attached to Ops, Ledger, Thread, and Trust instead of acting like a disconnected resident front end.
Home Surfaces
The resident portal should not be a dead end.
Home keeps the resident experience role-specific while staying attached to the same operational truth the team is working from.
1 Payments, balances, and resident-facing financial context
2 Maintenance requests, updates, and service visibility
3 Messages, documents, and lease-related information
4 A role-specific resident experience tied back to the operating record
Inside Sentus Home
Residents feel heard on every channel. Operators never drop a ball.
A resident texts on Monday, calls on Tuesday, and emails on Wednesday about the same issue. Sentus Home unifies all of it — one chronological thread, one operating record, every participant in the same view.
Resident Portal (60 components)
Phone-first self-service portal: work order submission, lease documents, payment history, package tracking, community, and announcements.
Omnichannel inbox
Email + SMS + voice transcript + in-app message = one chronological thread per resident. All parties in the same view.
Multi-party threaded chat
Resident, PM, maintenance tech, vendor, and Sophia participate in a single thread. Sophia auto-joins every new thread.
SMS + push + in-app notifications
Residents control quiet-hours and digest preferences. TCPA consent captured at onboarding and enforced per-message.
Resident community (33 components)
Posts, discussions, events + RSVP, user badges, leaderboards, AI content moderation. Drives retention through belonging.
Amenities management
Amenity booking, availability calendar, and usage tracking from the Resident Portal.
Package tracking
Package arrival notifications and pickup logs from the Resident Portal.
Pets and parking
Pet profiles, parking permit requests, and vehicle registration managed in the portal.
Gate access
Digital access management and guest authorization from the Resident Portal.
Renters insurance tracking
Residents upload proof of renters insurance. Expiration tracking and re-upload requests are automated.
Resident credit builder
On-time rent payments reported to credit bureaus. Credit score tracking dashboard in the portal. Opt-in consent flow.
Auto-pay + payment streaks
Bank-linked or card auto-pay via Stripe. Payment streaks displayed as a retention gamification feature.
Referral program
Residents refer friends and neighbors. Referral tracking, reward configuration, and conversion reporting in the Management Portal.
Move-in welcome
Automated onboarding sequence: portal access, auto-pay setup, community introduction, and first-week checklist.
Resident billing plan enrollment
Utility billing, RUBS, and fee enrollment configured per property and managed through the portal.
TCPA consent management
SMS consent captured at registration and at each new communication type. Consent record is immutable and exportable.
Operator FAQ
Questions operators ask about the resident experience.
Straight answers to the questions that come up in every evaluation.
What channels does the Sentus resident inbox cover?
The omnichannel inbox unifies email, SMS, voice call transcripts, and in-app messages into a single chronological thread per resident. Management, maintenance, vendors, and Sophia all participate in the same thread — no separate inboxes for each channel.
How does the Sentus community feature work?
The resident community is a 33-component platform covering posts, discussions, events with RSVP tracking, user badges and reputation, leaderboards, and AI moderation. It is built into the Resident Portal and managed from the Management Portal. The community drives retention by making the property feel like a place, not just a unit.
What notifications does Sentus send to residents?
Sentus sends SMS, push notifications (via Firebase/APNs), and in-app alerts. Residents control quiet-hours preferences and digest frequency from their portal. TCPA consent is captured at onboarding and enforced on every outbound message.
What is the Sentus resident credit builder?
Residents can opt in to have their on-time rent payments reported to credit bureaus. The credit score tracking dashboard and reporting toggle are live in production. This is a concrete financial benefit that increases resident satisfaction and retention.
How does auto-pay work for residents?
Residents link their bank account via Plaid or enter a card in the Resident Portal. Rent is charged automatically on the due date via Stripe. Payment streaks are displayed as a gamified retention feature. Late fees apply according to the configured policy when payment is not received.
Connected Systems
Where Sentus Home fits in the stack.
Sentus systems are designed to connect, not compete.