A WhatsApp bot for property managers
that logs maintenance tickets and move-in paperwork
Not every portfolio needs a full AI agent on day one. A WhatsApp bot that logs a maintenance ticket, collects move-in paperwork against a checklist and reminds tenants before rent is due is often enough to stop the manual chasing, built and live in one to two weeks.
Why property management companies lose money today
Maintenance requests for a managed portfolio arrive the same way at almost every company: a tenant calls, texts a personal number, or emails whichever address they remember, and someone on staff has to write it down, figure out which property and unit it belongs to, and decide how urgent it actually is before anything moves forward. That manual triage step is where tickets get lost, especially during a week when three other things are also on fire.
Move-in and move-out paperwork suffers the same scatter. A new tenant is asked for an ID, proof of income, a signed lease acknowledgment, and sends some of it by email, some by text, and forgets the rest until a move-in date is a day away and the file is still incomplete, with nobody having checked until it was almost too late to fix.
The third gap is visibility. A tenant who wants to know whether their maintenance request has been seen usually has to call or message and wait for a reply, and an owner asking the same question about a unit gets the same delay, both of which read as the company being slow even when the actual repair is already scheduled.
A fourth, easy to overlook, is where the information actually ends up. Photos of a leak, scanned documents, a tenant’s forwarded lease acknowledgment, all scatter across personal phones and inboxes with no single place a property manager can check to confirm what has and has not arrived for a given unit.
What we build for property management companies
A WhatsApp bot with one job done well: log a maintenance ticket with photos and property tagging, collect move-in or move-out documents against a checklist matched to the lease type, and let a tenant check their own ticket’s status without waiting for a reply. Every ticket is logged with a timestamp and the unit it belongs to, so a manager can see at a glance what is open, what is scheduled, and what has been sitting too long.
Admins get notified the moment a ticket is logged or a rent deadline passes without the expected payment confirmation, through a separate admin channel, so nothing depends on someone remembering to check a shared inbox. Checklists and reminder schedules are editable by your own staff through simple bot commands, no developer needed for the routine updates that come with every new lease signed.
Typical integrations: WhatsApp Business API for the tenant-facing flow and the admin alert channel, a lightweight database for ticket and document tracking, and a CRM or Google Sheets export where your company wants the data to live alongside other property records.
The bot deliberately does not try to hold a conversation. It runs a fixed sequence: here is what we need, here is what is still missing, here is your current status. That narrower scope keeps the build fast and the running cost close to zero, and it covers most of the ticket-logistics work that eats an office’s week without the extra build time a free-form conversational layer would add.
The bot also keeps a simple audit trail that a manual process rarely produces on its own: every ticket’s open and close timestamps, which vendor was assigned, and how long each stage actually took. That record turns into useful information on its own, a property with three times the ticket volume of comparable units in the portfolio is worth a look, and a vendor whose average response time keeps creeping up is worth a conversation, neither of which is visible without the timestamps the bot already captures as a byproduct of doing its one job well.
What stays with humans
The bot never decides whether a repair is covered under the lease, never negotiates a move-out deduction, and never promises a vendor visit time it has not actually confirmed. A tenant message that reads as a dispute, a safety concern beyond a standard maintenance ticket, or a question about lease terms gets flagged to an admin rather than answered, since a fixed-flow bot has no business guessing at any of those.
Price and timeline
| Model | Price | What it covers | Timeline |
|---|---|---|---|
| Agency runs it | from $900 | We build, host and maintain the bot; checklist and schedule updates included for the first month | 1 to 2 weeks |
| Full control, handover-ready | from $1,530 | Same build, plus full source, hosting handover and a written runbook for your own team | 2 to 3 weeks |
Running cost is close to zero beyond hosting, since the bot runs fixed logic rather than a language model on every message.
Related
Pair this bot with a website for property management companies for the owner- and tenant-facing side, or step up to the full AI agent for property management companies once FAQ and owner updates outgrow a fixed flow. The property management AI agent and the document OCR extraction automation cover adjacent pieces of the same paperwork problem. See the full package breakdown on the development service page, read how ticket logging holds up at scale in the factory ERP recovery case study, or get a written plan with a fixed price for your portfolio.
FAQ
What does a WhatsApp bot for a property management company cost?
A bot with ticket intake, move-in documents and rent reminders is about $900 to $1,500. Adding an admin panel with CRM export typically moves it toward $1,500 to $4,000. We give the exact number in a written plan after a short brief.
How is this different from the full AI agent package?
This bot runs a fixed flow: log a ticket, collect a document, send a reminder, check a status. It does not hold an open conversation or answer FAQ. The [AI agent for property management companies](/solutions/ai-agent-for-property-management-companies/) adds owner updates and judgment calls handled by a language model, for portfolios that need more than ticket logistics.
Can tenants use it without installing anything new?
Yes, it runs inside WhatsApp, which almost every tenant already has open. There is no separate app to download and no login to remember.
Who updates the checklists and reminder schedule?
You, through admin commands or a simple panel we build in, no developer needed for routine updates. We only get involved again if the ticket logic or lease structure itself changes.
Can admins get notified the moment a ticket comes in?
Yes. The admin alert flow flags a new ticket, a missed rent deadline, or an incomplete move-in document set as soon as the schedule says it should have arrived, not at the next manual check of a shared inbox.