• Solutions for Every Building, Every Stakeholder

    URBI is the first Building OS powered by HERO AI. Whether you manage properties, own them, or operate them day to day, URBI transforms complex, disconnected workflows into a single, intelligent platform that drives efficiency and builds stronger communities.

    Role Benefits

    • For Property ManagersStreamline operations and enhance tenant satisfaction with centralized management tools.
    • For Building OperatorsSimplify daily tasks and maintenance with intelligent automation and workflow management.
    • For OwnersMaximize ROI and property value with comprehensive oversight and analytics.
    • For Finance TeamsClose faster with double entry books, trust accounting, and reconciliation that runs nightly.
    • For BusinessesConnect with building communities and expand your service offerings.

    Building Benefits

    • Residential BuildingsSimplify living with one app for bookings, packages, payments, and community updates.
    • Commercial BuildingsStreamline operations, vendors, and compliance while giving tenants a frictionless experience.
    • Education BuildingsManage facilities, visitors, and compliance for safer, smarter, more connected campuses.
    • Senior LivingAnswer families around the clock, publish life enrichment once, and see every community on one screen.
  • One Platform. Smarter Buildings.

    URBI centralizes daily operations and adds AI intelligence to transform complexity into clarity.

    Products

    • URBI KoreThe central hub where managers, owners, and staff run building operations in one place.
    • URBI KonnectA marketplace that connects buildings with trusted vendors, services, and community events.
    • URBI AccountingAI consolidation, invoices and receipts processed by AI, books pre reconciled before month end. In Beta.
    • URBI AIOne intelligence across URBI. HERO answers your team's questions, Arthur answers your community's calls, texts, and emails 24/7.

    Features

    • Operations & Workflow
    • Amenities & Booking
    • Events & Ticketing
    • Communication & Community
    • Payments & Transactions
    • Data & Compliance
    • HERO AI Intelligence
    • IoT & Hardware Integration
    • Community Experience
    • Accounting (In Beta)
    View All
  • Customers
    • All ResourcesGuides, support, and customer stories in one place
    • Help CenterGuides and answers for every part of URBI
    • BlogWhy URBI works the way it does
    • ReleasesEvery update we ship, in plain language
    • System StatusHow every part of URBI is running right now
    • About UsLearn about our story and mission
    • MilestonesHow URBI got here and where it is going
    • CareersWe're HiringJoin our growing team
    • FAQStraight answers about URBI, HERO and Arthur
    • ContactGet in touch with us

Schedule a Demo

  1. Help Center
  2. /Operations
  3. /Service Tickets
  4. /What Residents See When They Create a Ticket

What Residents See When They Create a Ticket

Use this article to walk a resident through creating a service ticket in the URBI mobile app, whether they're on the phone with you or you're just confirming what they should be seeing on their...

Last updated September 14, 2026

Operations
  • Approvals: decide expenses, board votes and RFPs in one place
  • Board Decisions: overview
  • Confirming packages, and what a refused package means
  • Document sharing
  • Finding the packages for one home
  • How to approve expenses and RFPs in Approvals
  • How to create a decision
  • How to create a time limited public link
  • How to generate the PDF report
  • How to run a vendor RFP through Board Decisions
  • How to share a file or folder
  • How to upload with drag and drop
  • How to vote and finalize a decision
  • How to vote on board decisions in Approvals
  • Operations
  • Troubleshooting
  • Troubleshooting document sharing
  • When a scanned package needs a look
    • Add Assignees to a Service Ticket
    • Attach a Vendor to a Service Ticket
    • Convert a Service Ticket to a Task (and make sure it stays visible)
    • Create a Service Ticket
    • Documents on a Service Ticket
    • Finding a Ticket: Search and Filters
    • How the Emergency Number Is Chosen
    • How to Convert a Service Ticket into a Board Decision
    • How to Reassign Work When Removing a Team Member
    • How to Set the Emergency Line
    • Notes on a Ticket, and What the Resident Can See
    • Service Ticket Statuses Explained
    • Service Tickets: Glossary
    • Service Tickets: Overview
    • Service Tickets: Troubleshooting
    • Set Up Recurring Service Tickets
    • The History on a Ticket: What It Records
    • The Tabs on a Service Ticket, Explained
    • Troubleshooting
    • What Residents See When They Create a Ticket
    • What's New in Service Tickets
    • Who Can Do What on a Service Ticket
    • Add Assignees to a Task
    • Create a Task
    • Organize Tasks with Categories, Projects, and Labels
    • Set Up Recurring Tasks
    • Access Request Statuses Explained
    • Choosing Who Receives a Request for Access
    • How to Send a Request for Access
    • Mandatory vs Request: Which One to Send
    • Recording an Answer on Someone's Behalf
    • Requests for Access: Glossary
    • Requests for Access: Overview
    • Requests for Access: Troubleshooting
    • Reschedule Requests: How They Work
    • Sending a Reminder for a Request That Has Not Been Answered
    • What the Recipient Sees and How They Answer
    • Awarding the Work
    • Comparing Proposals
    • How to Invite Vendors to an RFP
    • Putting an RFP to a Board Vote
    • Requests for Proposal: Glossary
    • Requests for Proposal: Overview
    • Requests for Proposal: Troubleshooting
    • RFP Statuses Explained
    • What a Vendor Sees and How They Submit a Proposal
    • Asset Impact: Overview
    • Asset Impact: Troubleshooting
    • Cancel Bookings or Block New Ones
    • Closure Statuses Explained
    • Confirming a Closure, and Why Scheduling Is Not Enough
    • How to Close an Amenity for Scheduled Work
    • What Happens to Bookings and Money When You Close an Amenity
    • How to view and add a vendor's expenses
    • Requesting Completion, and Technician Notes
    • Vendor Billing Tab: FAQ
    • Vendor Billing Tab: Overview
    • What a Contractor Sees on a Work Order
    • Set Maintenance Schedules for Assets
    • Track Equipment and Warranties
All collections

On this page

  • Before you start
  • Steps
  • Things worth knowing when supporting a resident

Use this article to walk a resident through creating a service ticket in the URBI mobile app, whether they're on the phone with you or you're just confirming what they should be seeing on their screen. This is the resident-facing flow; residents do not have access to Kore.

Before you start

Service ticket creation is only available to residents whose property is on a plan that includes service tickets. If a resident's property is on the entry-level plan, they will not see a way to create a ticket at all (see Steps, step 1).

Steps

  1. From their home screen, the resident opens Service Tickets. At the top of the list they see a + button in the header.
    • If their property's plan doesn't include service tickets, there is no + button. Instead, if they have no tickets yet, they see a message telling them service tickets aren't available on their building's current plan and to contact their management team.
  1. Above the ticket list, the resident sees a short notice: "Tickets are reviewed during business hours." If a phone number is available for their property, a second line appears: "If this is an emergency, call [number] now." with the number as a tappable link. This notice can be dismissed from the list view by tapping the X on it. See How the Emergency Number Is Chosen for where that number comes from.
  1. Tapping + opens the New Service Ticket form as a sheet. The same notice from step 2 appears again at the top of the form (this instance cannot be dismissed).
  1. The resident fills in Title (required, up to 100 characters), a brief description of the issue, for example "Leaking kitchen faucet."

  2. The resident fills in Description (required, up to 500 characters), the fuller details of what's wrong.

  1. Optionally, the resident fills in Access Instructions (up to 300 characters), anything staff or a vendor should know about getting into the unit, for example a door code or a request to call ahead.

  2. Optionally, the resident adds attachments under Attachments:

    • Add Photo lets them take a new photo with the camera or choose one from their photo library.
    • Add Document lets them attach a PDF, a text file, or a Word document.
    • Each attached file shows a thumbnail (or a document icon) and its file name, with an X to remove it before submitting.
  1. The Submit button in the top right stays disabled (greyed out) until both Title and Description have something in them. Once both are filled in, the resident taps Submit. While the ticket is being created, the button shows a loading spinner in place of the label.

  2. On success, the resident sees a confirmation alert ("Service ticket created successfully!"), the form closes, and the new ticket appears at the top of their ticket list. If anything goes wrong creating the ticket or uploading an attachment, the resident sees an error alert asking them to try again, and the sheet stays open with what they entered still in place.

Things worth knowing when supporting a resident

  • The notice never blocks submission. Even in an active emergency, a resident can still fill out and submit a ticket, the banner is informational, not a gate.
  • Title and Description are the only required fields. Access Instructions and attachments are optional.
  • If a resident says they don't see an emergency number, that's expected in some configurations, see How the Emergency Number Is Chosen and Troubleshooting.
  • Attachments upload after the ticket is created, not before. If the ticket itself is created but an attachment fails to upload, the resident sees the shared error alert, ask them to try attaching the file again from the ticket rather than resubmitting the whole form.

Was this article helpful?

Related articles

Operations

Create a Service Ticket

Learn how to create service tickets in URBI Kore to track maintenance, repairs, and operational work for your properties.

Read
Operations

Notes on a Ticket, and What the Resident Can See

Notes are internal by default. How sharing works, and why it is per note.

Read
Operations

Add Assignees to a Service Ticket

Learn how to assign team members and collaborators to service tickets in URBI Kore.

Read
Operations

Attach a Vendor to a Service Ticket

Learn how to attach vendors to service tickets in URBI Kore for RFP workflows or direct assignments.

Read
All Operations articlesAsk the URBI team
URBI

URBI is the Building OS, founded in Calgary in 2023. One platform with HERO AI built in, running thousands of units for property managers, condo boards and owners.

Solutions

  • All Solutions
  • For Property Managers
  • For Building Operators
  • For Owners
  • For Finance Teams
  • For Businesses

Building Benefits

  • Residential Buildings
  • Commercial Buildings
  • Education Buildings
  • Senior Living

Products

  • All Products
  • URBI Kore
  • URBI Konnect
  • URBI AI
  • URBI Accounting (Beta)

Company

  • About URBI
  • About Us
  • Milestones
  • Reviews
  • FAQ
  • CareersWe're Hiring
  • Contact

Resources

  • All Resources
  • Help Center
  • Blog
  • Releases
  • System Status
  • FAQ
  • For AI assistants

Compare

  • Compare Us to Residential
  • Compare Us to Commercial
  • Compare Us to K-12

Legal

  • Security & Privacy
  • Terms & Conditions
  • Terms of Service for Konnect

© 2026 URBI. All rights reserved.

Privacy PolicyTerms of Service

Schedule a Demo