Dev manages 180 rental homes for a small property management company. Every morning brings a flood of messages: rent questions, repair reports, landlord queries, viewing requests and the occasional emergency. Dev is good at the job but spends the first two hours of every day just sorting messages.
This is a typical week before and after triage.
Before: Monday
Sixty messages from the weekend. Dev reads them in order. Message 41 is a tenant reporting no heating since Saturday evening. It gets attention at 11am. The tenant is cold and angry, and so is the landlord.
Before: Tuesday
Twelve tenants ask when rent is due or how to pay. Four ask about bin days. Dev answers them all individually. The general problem is described in tenant questions that swamp property managers.
Before: Wednesday
A landlord with five properties enquires about switching to Dev's company. The message sits among tenant emails and is answered on Friday. The landlord has already signed elsewhere. Landlord enquiries are covered in landlords looking for a manager and what they ask.
Before: Thursday
Three repair reports arrive without addresses or photos. Dev replies to each asking for details.
Counting the cost
Hours spent sorting and answering routine questions. An emergency handled late. A valuable landlord lost. Repairs delayed by missing details.
After: Monday
The company adds a website assistant. SpideyChat for property management companies answers routine tenant questions from the tenant handbook, captures repair requests with full details, flags landlord enquiries separately and shares emergency contact details immediately when a tenant describes something urgent.
On Monday, the heating tenant was given the emergency number on Saturday evening and the out-of-hours contractor attended that night. The routine questions have been answered. Dev starts the day with captured repairs, each with an address, description and photos.
After: Tuesday
Rent and bin questions have been answered from the handbook. Dev spends the morning on inspections.
After: Wednesday
A landlord enquiry arrives and is flagged. Dev replies the same afternoon and books a meeting.
After: Thursday
Repair requests arrive complete. Contractors are booked the same day. Overnight handling is described in how property managers handle tenant issues overnight.
After: Friday
For the first time in months, Dev spends Friday afternoon on planned inspections rather than chasing messages. The captured repair requests from the week are grouped by property, so Dev can see which buildings need attention and plan preventive work. Landlords receive their monthly updates on time, and one of them mentions the faster repair response in a positive review.
What does not change
Dev still makes every decision about repairs, still manages contractors and still speaks to tenants and landlords personally when it matters. The assistant handles first contact. Solo professionals experience a similar shift, as described in a solo coach's week before and after handling first contact.
What tenants noticed
Tenants noticed the change before anyone told them. Answers to simple questions arrived instantly, repairs were booked faster because the details were complete, and the one emergency that month was handled within the hour. Complaints about slow replies, which used to arrive every week, stopped almost entirely. Landlords heard about it from their tenants, which is the best marketing a property manager can have.
Where to start
Put your tenant handbook online, make the emergency route prominent and separate landlord enquiries from tenant messages. Try SpideyChat on your own site, or read about routing on the features page.