work / internal app / tenant service ticketing system

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.

role
Solo full-stack developer
client
Facility management company
status
Live at handover

Languages

PythonJavaScriptHTML5CSS

Tools & platforms

DjangoReact

AI & LLM

to build it
ChatGPT

Skills

Full-stack developmentRouting logicSLA timersEmail notificationsReporting
01// how I approached it

The thinking behind it

  1. 01 · What I noticed

    Requests weren't ignored on purpose. They had no owner and no deadline, so they slipped.

  2. 02 · What I decided

    Give every request an owner and a clock: route it by property and category, and remind people before deadlines.

  3. 03 · What I delivered

    A ticketing system built from scratch, live at handover.

02// old vs new

Old system vs new system

Old systempeople as the glue
  1. Tenant calls or emails
  2. Staff forwards it
  3. Someone maybe follows up
  4. Reports built by hand
New systemthe system does the work
  1. Tenant submits a form
  2. Routed to the right team
  3. SLA reminders and status emails
  4. Reports generate automatically
03// how it works

Watch it run

Click through the four steps. In step 3, click any box to see what it does.

synthetic data · no client screens
Reconstruction with synthetic data · no client screens
04// the hard part

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.

05// key decisions

Why it's built this way

decision 1

Route by property and category

Tickets go straight to the team that can fix them.

Trade-off: routing rules must be kept current.
decision 2

Deadline reminders

People are nudged before a deadline is missed, not after.

Trade-off: more notifications to tune.
decision 3

Tenants kept informed

Status emails cut down on "any update?" calls.

Trade-off: emails must be clear and timely.
06// lessons

What made it work

  1. 01

    Ownership fixes most delays

    A ticket with an owner moves.

  2. 02

    Remind before, not after

    Early nudges prevent missed deadlines.

  3. 03

    Updates reduce follow-ups

    Telling tenants the status saves everyone time.