What's New in Service Tickets
Service Tickets update: convert to task auto assign, vendor work order default, convert to board decision, removal reassignment, filters, and document previews.
Last updated
This update improves how your team works with service tickets in URBI Kore — specifically around converting tickets, assigning vendors, removing team members, filtering, and previewing documents. All changes apply to staff, board members, and property managers.
What changed
Area | What's new |
Convert to Task | Converting a ticket now auto-assigns it to you (or adds you as a collaborator) |
Assign vendor | Assigning a single vendor now defaults to a Work Order instead of a Request for Proposal |
Convert to Board Decision | Tickets can now be escalated directly into a board decision, carrying over the title, description, and attachments |
Remove team member | Removing a member who has open work now requires you to reassign that work first |
Sidebar filters | Label, category, and project filters in the left sidebar now correctly narrow the ticket list |
Documents tab | Images open in an inline lightbox; all files have Open and Download buttons |
Where to find service tickets
Go to Operations → Service Tickets in the left navigation. Board members see the same tickets under their board view.
Note: Service Tickets, Tasks, and the Operations area are available on KORE and PREMIUM plans only. BASIC-plan properties will be redirected to the dashboard.
September 2026
Tickets look like tickets while they load. The main list, the phone list, the ticket panel and the public entry-request page now show the shape of what is coming instead of a spinner, so the page stops jumping when the data lands.
Your building's word for the work. Emails and phone alerts now use your own vocabulary. A school reads maintenance request and classroom where a condominium reads service ticket and unit.
Clearer rules about who can do what. Changing who is working on a ticket now requires a connection to that building. Bringing in a colleague from another building still works exactly as before.
Repeating tickets record who really finished them. The history and the alerts name the person who pressed Complete, and someone whose ticket-creation permission has been switched off is told why the next occurrence was not created instead of it failing silently.
Closure reports tell you what actually happened to residents' money. Refunds are reported with the amount that went back and whether the booking was really cancelled, including refunds made outside the card system.