A property management office runs on interruption. The phone rings all day with tenants reporting problems, chasing problems, and asking questions the tenancy agreement already answers. In between, landlords ring about statements and contractors ring about access.
And the issues themselves don't respect the working day. Heating fails on Sunday. A leak starts at midnight. A lock breaks at eleven.
Maintenance logging is the core use case
The single biggest improvement a bot makes here is the quality of what gets logged.
Compare two records of the same problem.
Voicemail: "Hi, it's flat 4, the boiler's not working properly, can someone come out."
Bot-captured: Property: Flat 4, 12 Bridge Street. Issue: no hot water, heating works. Started: yesterday evening. Boiler shows an error code E133. Tenant available Tuesday and Thursday after 4pm, or can leave a key with the neighbour in flat 3. Contact: [number].
The second one gets fixed on the first visit. The first one generates two phone calls, an access failure, and a second appointment.
Configure the bot to gather, every time:
- Which property, and which unit
- What the problem is
- When it started, and whether it's getting worse
- Any error codes or specifics
- Access availability
- Whether there are pets or anything a contractor should know
- Contact number
That's a work order, not a message.
Emergencies need a script
Some things cannot wait for a logged ticket, and the bot needs an explicit list.
Gas smell. Carbon monoxide alarm. Water coming through a ceiling or an uncontrollable leak. Electrical burning smell or sparking. Total loss of heating in cold weather where there are children, elderly, or vulnerable occupants. Broken external door or window leaving a property insecure. Fire.
For any of those, the bot gives a scripted safety instruction and the emergency number, immediately. It does not log a ticket and say someone will be in touch. Write the list, write the response, put it first in the configuration.
Deflecting the repeat calls
A large share of a property manager's phone volume is less new information than chasing.
Tenants ring because nobody told them what happens next. Landlords ring because they don't know whether the repair was authorised. Both are anxiety produced by silence.
A bot helps in two ways. First, it confirms clearly what's been logged and what the process is, which resolves most of the immediate uncertainty. Second, it answers the standing process questions: how long do repairs usually take, who authorises them, what counts as an emergency, what am I responsible for versus the landlord.
That last one is worth putting real content behind. Tenant-versus-landlord responsibility is the source of a huge amount of friction, and a clear, consistent answer available at any hour prevents a lot of arguments.
Tenancy admin
The other steady load is process:
- How do I give notice, and how much?
- When is rent due and how do I change the payment date?
- How do I request a pet?
- Can I redecorate?
- How do I get a reference?
- What happens at check-out, and how does the deposit work?
All documented in your tenancy agreement and your published policies. All currently answered individually, repeatedly, by someone who could be doing something else.
Deposit and check-out questions cluster heavily in the final month of a tenancy. Predictable, seasonal, and entirely automatable, which makes them an odd thing to still be answering by hand.
Landlord acquisition
The commercially interesting side. Landlords compare managing agents in the evening, and they ask a consistent set of questions: what do you charge, what's included in full management versus let-only, how do you handle arrears, are you accredited, how do you vet tenants.
Answer those from published content and capture the enquiry properly. How many properties, where, currently self-managing or with another agent, and when they're free to move. Route it to whoever handles new instructions, flagged.
These leads are worth far more than anything else on the website and they routinely sit in a shared inbox for days.
What to keep away from it
Don't let it authorise repairs or commit to a timescale. Authorisation limits and contractor availability are yours to manage.
Don't let it give legal advice on tenancy law. Eviction, rent increases, and disputes are legally sensitive and need a person, often a qualified one.
Don't let it discuss arrears, or any other tenant's affairs. Anything account-specific routes to a human.
Putting it in place
Point it at your website. Services, fees, tenant information, and process pages. Upload your tenancy agreement template and your repairs policy; that's where the responsibility answers live.
Split routing three ways at the first question: tenant, landlord, or new landlord enquiry. Add the emergency script. Set the maintenance capture fields.
What to watch afterwards
Two numbers. Maintenance requests logged with complete information, because that's what determines first-visit fix rates and contractor cost. And new landlord enquiries responded to within an hour rather than a day.
The first saves money every week. The second grows the portfolio, which is the only thing that grows the business.