A WhatsApp bot for property managers
that logs maintenance tickets and move-in paperwork

Where the manual triage actually breaks

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. Someone on staff has to write it down, figure out which property and unit it belongs to, and decide how urgent it actually is. 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. Some arrives by email, some by text, and the rest gets forgotten. The move-in date is a day away and the file is still incomplete.

Visibility is the third gap. A tenant who wants to know whether their maintenance request has been seen usually has to call or message and wait for a reply. An owner asking the same question about a unit gets the same delay. Both read as the company being slow, even when the actual repair is already scheduled.

Where the information actually ends up is a fourth, easy to overlook. Photos of a leak, scanned documents, a tenant’s forwarded lease acknowledgment, all scatter across personal phones and inboxes. There is no single place a property manager can check what has and has not arrived for a given unit.

What the bot actually does

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. 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. A manager sees 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. This runs 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 is needed for routine updates that come with every new lease signed.

Typical integrations: WhatsApp Business API for the tenant flow, a lightweight database for ticket tracking, and a CRM or Google Sheets export.

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 covers most of the ticket-logistics work that eats an office’s week.

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 is worth a look. A vendor whose average response time keeps creeping up is worth a conversation. Neither is visible without the timestamps the bot captures as a byproduct of doing its one job well.

What stays with your team

The bot never decides whether a repair is covered under the lease. It 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, or a question about lease terms gets flagged to an admin rather than answered. A fixed-flow bot has no business guessing at any of those.

Price and timeline

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. How ticket logging holds up at scale is in the factory ERP recovery case study. Get a written plan with a fixed price for your portfolio.