01 Overview
The work nobody budgets for
Leasing gets the attention because it is where revenue starts. Residency is where the hours actually go. A single tenancy generates a move in checklist, a deposit to register, utilities to transfer, a renewal to raise at the right moment, a rent cycle to watch twelve times a year, an amendment when a partner moves in, and perhaps forty small questions along the way.
None of it is difficult. All of it is time sensitive, and almost all of it depends on somebody remembering. Multiply by a few hundred units and the memory is the bottleneck.
Fashti turns that memory into workflows. Dates are tracked against the tenancy rather than in somebody's calendar, routine resident questions are answered the moment they are asked, and the things that genuinely need a person arrive with their full history attached rather than as a vague note to call someone back.
- Guided move in and move out with every step tracked to completion.
- Renewals raised on your notice schedule, with terms prepared in advance.
- Rent reminders, collection and reconciliation running quietly in the background.
- Resident support around the clock, with real escalation when it matters.
An illustrative resident thread
02 Tenancy lifecycle
Every date that matters, tracked against the tenancy
Not reminders in a calendar. Workflows that start themselves, progress, and report that they are done.
-
01
Move in
A checklist opens the moment an agreement is signed: deposit received and registered, first payment scheduled, utilities and account transfers explained, access and key collection arranged, inventory and condition report issued, and the welcome information sent in the resident's preferred channel. Each item is tracked, and anything incomplete three days out is flagged while there is still time to fix it.
-
02
Settling in
The period that produces the most questions and sets the tone for the whole tenancy. Fashti answers the practical ones immediately, logs the first maintenance request properly rather than as a text message somebody screenshots, and checks in once at the end of the first month so small problems surface early.
-
03
Mid tenancy changes
An occupant added, a pet requested, a parking space changed, a payment date moved. Each is a small amendment with a policy behind it. Fashti applies the policy, prepares the paperwork where the answer is yes, and escalates where the answer requires judgement rather than guessing on your behalf.
-
04
Renewal
Renewals are raised at the point your notice period requires, with the current terms, the proposed terms and the unit's history in one view. Fashti opens the conversation, handles the straightforward acceptances end to end, and brings you the negotiations. A renewal that starts on time is a void that never happens.
-
05
Move out
Notice acknowledged, final inspection booked, meter readings and forwarding details collected, deposit position prepared with the condition report attached, and the unit passed to leasing for marketing before it is empty rather than after. Deductions are proposed with evidence, and approved by a person.
03 Resident support
Answered at nine in the evening, properly
Residents do not have operational questions during office hours. They have them when they get home.
A resident should get a better answer at ten at night than they used to get at ten in the morning.
The standard we hold resident support to04 Rent and arrears
Chased early, firmly and with a record
Arrears are cheapest to solve in the first week and most expensive to solve in the third month. The difference is almost entirely about how quickly somebody noticed.
A reminder on the schedule you set, in the resident's channel, with the amount and the reference. Most short payments are oversights, and an oversight prevented is not an arrear.
Receipts are matched against expected amounts. Partial payments, duplicates and payments against the wrong reference are identified rather than quietly accumulating into a mismatch somebody finds at month end.
Follow up runs on your escalation ladder, at your intervals, in your wording, with every contact attempt logged against the tenancy. The tone stays professional and the record stays complete, which is what matters if the matter ever goes further.
Formal notices, payment plans, hardship cases and anything heading towards possession are escalated to your team with a full payment history prepared. Fashti does not issue notices and does not negotiate settlements.
An arrears position that is current rather than monthly, by property and by tenancy, with the age of each balance and the next scheduled action against it.
05 Care and escalation
Where automation should stop talking
Residents are people in their homes, not tickets in a queue. These are the cases Fashti is configured never to handle alone.
Always escalated to a person
- Anything affecting safety or the habitability of a home
- Formal complaints and disputes between residents
- Notices, possession proceedings and legal correspondence
- Signs of hardship, vulnerability or distress
- Any explicit request to speak with a person
How the handover works
- The conversation stops rather than stalling the resident
- The resident is told plainly that a colleague is taking over
- The full thread, tenancy and history reach the exception queue
- Urgency is assessed, and out of hours routing applies if set
- Nothing is closed automatically once a person is involved
06 Questions
About residential operations
Do residents have to use an app or a portal?
No. Residents keep using whatever they use today, which is usually text or email. Fashti meets them there. If you already run a resident portal, Fashti works alongside it rather than competing with it, and keeps the records in both places consistent.
Can it take payments?
Fashti handles the operational side of rent: reminders, references, matching receipts against expected amounts, identifying mismatches and running your follow up ladder. The money itself moves through your existing payment and banking arrangements, and the ledger stays in your property management system.
What stops it making a promise you cannot keep?
The policy engine. It holds what may and may not be offered to a resident: whether a payment date can move, whether a pet is permitted at a given property, what a deposit deduction can cover. Anything outside those bounds is escalated instead of answered, and every answer given is logged with the rule behind it.
How does it handle a resident who is clearly upset?
It stops and hands over. Detecting distress, frustration or vulnerability is one of the explicit escalation conditions, and in those cases the correct automated response is a short, human acknowledgement followed by a real person. It does not try to resolve the matter or manage the emotion.
Start the conversation
Hand over the remembering
Tell us how many tenancies your team carries and how renewals are tracked today. We will show you which dates Fashti would own and which would stay with you.
We read every message and reply within one business day