What a maintenance request actually does in Rentbase
Most pages on the Rentbase site make claims. This page shows you the screens. We follow one request from the moment it lands to the moment it's closed out — the emergency check, the clarifying question, the drafted vendor outreach, your approval. One thing holds across all three moments: Rentbase drafts the vendor outreach and tenant updates for your approval — nothing reaches a vendor without you. A clarifying question and one reminder go out on their own so you're not chasing details, and emergencies are flagged to you the instant they're detected. The full feature set is covered on the Platform page. If you trust what you see, start the trial.
1. A request lands — and the emergency check runs first
The instant a request arrives, an always-on emergency check runs — independent of the AI toggle, so it's on even if you've turned drafting off. A suspected life-safety issue skips everything and pings you directly. Everything else gets triaged: category, urgency, and a vendor matched from your records, because Rentbase already knows the unit, the lease, and who you've used there before. The urgent one never sits buried under fifteen routine tickets.
2. When it's vague, it asks the right questions
Half of maintenance is getting enough detail to act. When a request is too vague to dispatch, Rentbase automatically asks the tenant the right clarifying question for you — never for emergencies, which go straight to you — then waits for the reply. You don't lift a finger. Once it has the full picture, it drafts the vendor outreach with the unit, access notes, and scope already filled in, plus the tenant reply, in a clear, professional tone. You read it, tweak if you want, and approve. You approve everything that reaches a vendor or updates a tenant; the clarifying question and reminders go on their own — nothing else does.
3. Ready for you, or still in motion
Every ticket shows whether it needs you now — a draft to approve, an emergency routed to you — or is still in motion, waiting on a tenant reply or a vendor visit. Rentbase chases the reply once when a thread goes quiet, and the moment you step in, it steps back. The back-and-forth keeps moving without you babysitting it, and nothing slips through the cracks because the board never lets a ticket go silent.
Common questions
Does the AI message my tenants and vendors on its own? The vendor outreach and tenant status updates sit as drafts until you say go — nothing reaches a vendor without you. Two things move on their own so you're not babysitting the inbox: a clarifying question when a request is too vague to act on, and one reminder if the tenant goes quiet. And a suspected emergency is flagged straight to you the instant it's detected.
How does it know which vendor to use, or what the draft should say? Because the request lands inside the system that already holds the unit, lease, tenant, and vendor history — so the drafts pull the address, access notes, the trade you've used at that property, and the scope. That context is why the drafts are usable, not generic.
What if the AI gets the triage wrong? You catch it before anything happens, because nothing is sent without your approval. Change the category, urgency, or vendor on the ticket and the draft updates. Emergency detection is deliberately cautious — it would rather flag something borderline than miss a real one.
What happens at the end of the 14-day trial? On day 15, your account becomes read-only until you subscribe. Your data stays where it is. We don't auto-charge.
One request, handled. Now do it for all of them.
14-day free trial of Starter. No credit card. Self-serve setup.