Every tenant issue gets an owner and a clock.
Tenant requests for a real-estate portfolio arrived by phone and email with no owner and no deadline. I designed and built a ticketing system from scratch that routes, tracks and reports on every request.
Languages
Tools & platforms
AI & LLM
Skills
The thinking behind it
- 01 · What I noticed
Requests weren't ignored on purpose. They had no owner and no deadline, so they slipped.
- 02 · What I decided
Give every request an owner and a clock: route it by property and category, and remind people before deadlines.
- 03 · What I delivered
A ticketing system built from scratch, live at handover.
Old system vs new system
- Tenant calls or emails
- Staff forwards it
- Someone maybe follows up
- Reports built by hand
- Tenant submits a form
- Routed to the right team
- SLA reminders and status emails
- Reports generate automatically
Watch it run
Click through the four steps. In step 3, click any box to see what it does.
Every request needs an owner and a clock.
Tenant issues slipped because nobody clearly owned them. The system routes each ticket by property and category, reminds the team before deadlines, and keeps tenants updated by email, with reports for managers.
Why it's built this way
Route by property and category
Tickets go straight to the team that can fix them.
Deadline reminders
People are nudged before a deadline is missed, not after.
Tenants kept informed
Status emails cut down on "any update?" calls.
What made it work
- 01
Ownership fixes most delays
A ticket with an owner moves.
- 02
Remind before, not after
Early nudges prevent missed deadlines.
- 03
Updates reduce follow-ups
Telling tenants the status saves everyone time.
Have a similar mess? Tell me the step you hate.