(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-T4WQLRB');
Real estate · Property managers · Developers

Ticketing system for property managers.

A burst pipe, a request for a certificate, noise after ten at night — all of it lands in one queue with a case number. The resident can see the status, and the board gets a monthly report.

Built for housing communities and co-operatives, for developers handling post-sale defects, and for firms managing commercial property.

Book a demo · 15 min See use cases →
debesis.app/property
Water leak — Mickiewicza 4/12
Urgent · Plumber called
!
Certificate request — flat 12B
Bank request · SLA 5d
5d
Noise after 10pm — flat 8/3
Third complaint · escalated
3x
Meter replacement — Słowackiego 8
Done · handover signed
Response time
95%
Three use cases

How Debesis works in property management?

Three situations where a ticketing system replaces scattered phone calls, emails and notes left at the front desk.

Use case 01

Housing community or co-operative

Several hundred residents report faults, requests and complaints, and a board of three to five people has to keep all of it in mind, along with inspection dates and escalations to contractors.

What Debesis does about it:

  • Resident portal — the resident reports through the website or app with their flat number, a category, a description and photos, and the case number is issued automatically.
  • Automatic routing — a technical fault goes to maintenance, an administrative matter to accounts, a noise complaint to the board. Nothing has to be "passed on".
  • Escalation of repeat complaints — a third noise complaint about the same flat escalates to the board automatically, with a formal warning proposed.
Use case 02

Developer — post-sale customer care

The buyer has taken possession. Through the warranty period — five years under Polish law — they report defects: a cracked wall, a window that won't close, a ventilation problem. The developer has to track each one, fix it on time and keep the evidence.

What Debesis does about it:

  • One ticket per defect, with its location — flat 87 on a named development, with every defect for that unit in a single view and the full warranty history behind it.
  • A workflow for contractors — a joinery defect becomes a ticket for the joinery firm with a deadline attached, the conversation stays in the thread and the dates are watched.
  • Complete warranty documentation — when the warranty period ends, the archived history of every report, repair and photograph is there for audits and for any dispute.
Use case 03

Commercial property — offices and retail

A manager looks after five to fifteen commercial tenants in an office block or shopping centre. Tenants report technical problems, ask for changes and raise administrative matters — and each of them has an SLA written into the lease.

What Debesis does about it:

  • An SLA per tenant — a premium tenant at two hours, a standard tenant at eight. The system tracks it and alerts the manager before a breach.
  • Technical workflow with maintenance firms — an air conditioning failure raises a ticket for the service company, the tenant is told when to expect them, and the invoice is linked to the ticket.
  • A report for the building's owners — how many reports came in, in which categories, what share met the SLA and what repairs cost per tenant: the numbers you take into a lease negotiation.

What is a ticketing system for a property manager?

A ticketing system for property management organises the stream of reports coming from residents in a housing community, buyers in a development or tenants in a commercial building. Each one becomes a ticket with a case number, a category, a location down to the flat or building, a status and a named owner.

In housing community management it replaces notes pinned by the entrance, a manager's phone buried in text messages and a spreadsheet of things to do. Residents report through a portal or app, the system routes each case to maintenance, accounts or the board, and the owner can see where their case stands.

For developers it is protection as much as organisation. Every defect is recorded with a date, a description, a photograph and the state of the repair, so at the end of the warranty period there is a full record of what was done and when. In a dispute that record is evidence, rather than one manager's recollection.

Related pages

Ticketing system for property management — frequently asked questions

Questions from community managers, developers and customer service leads at property management firms.

Do residents need an account to report something?

No. There are two routes. A public form takes a flat number and a description, creates the ticket and confirms by email. Or residents can log into a portal and see the history of their cases, the status of each and their invoices. Communities often start with the form and open the portal later.

How does Debesis handle anonymous reports, such as a complaint about a neighbour?

Anonymous complaints often still have to be logged, even without knowing who made them. Debesis has a separate ticket type for them: recorded with no reporter details, but with the building or entrance, the date and the description. The board then decides how to respond — a warning, mediation or legal escalation.

Can contractors be given access?

Yes, with a restricted account. A contractor sees only their own tickets, can update the status and attach completion reports, and cannot see other firms' work or residents' personal data. When the ticket closes, the before-and-after photos and the signed handover stay in the archive.

Does the system support the statutory register of reports?

Yes. Every report carries an immutable number, a date and a status, and a monthly or annual PDF export gives you the register with its full history for the community's files. There is an audit log of every change behind it.

How does Debesis help with a developer's warranty obligations?

Each defect reported during the warranty becomes a ticket with its location, its category — services, joinery, finishing — the date it was raised, the state of the repair, before-and-after photos and a signed handover. At the end of the period you have a documented record of what was repaired, when and at what cost.

Can SLAs be tracked per tenant in a commercial building?

Yes. SLA policies follow the lease: a premium tenant at two hours, a standard tenant at eight, weekends handled separately. The system watches the clock and raises tickets at risk to the top of the queue, and the monthly report shows SLA performance per tenant.

What does a ticketing system cost for a community of 200 flats?

Debesis is priced per user, starting at 119 PLN per user / month on the Basic plan, and for a housing community the cost depends on how many people on the board need an account. We quote larger commercial properties individually, and a free trial period is available so you can see whether it fits before committing.

Start with a demo

We'll show you this on your own property.

We'll walk through how Debesis would have handled last month's reports. Fifteen minutes, no slide deck.

Book a demo · 15 min