Skip to main content

​
Overview

The Tickets module provides a structured system for residents to report issues, request services, and submit complaints. Administrators can track, categorize, assign, and resolve tickets, ensuring accountability and timely response to resident needs.

​
Key Features

Issue Reporting

Residents submit tickets with descriptions, photos, and urgency indicators

Categorization

Organize tickets by category (Maintenance, Security, Noise, etc.)

Status Tracking

Monitor ticket progress through workflow stages from submission to resolution

Communication

Add comments and updates to keep residents informed

​
Ticket Structure

Each ticket contains:
  • Ticket ID: Unique identifier
  • Community: Associated community
  • Resident: Who submitted the ticket
  • Unit Number: Resident’s address
  • Category: Type of issue (Maintenance, Security, Complaint, etc.)
  • Status: Current stage (Open, In Progress, Resolved, Closed, etc.)
  • Content: Description of the issue or request
  • Images/Videos: Visual documentation (optional)
  • Report Date: When the ticket was submitted
  • Comments: Updates and communication thread

​
Submitting Tickets (Resident View)

​
How Residents Create Tickets

1

Access Ticket Portal

From the resident portal, navigate to “Tickets” or “Service Requests”
2

Create New Ticket

Click “New Ticket” or “Submit Request”
3

Select Category

Choose the issue category:
  • Maintenance: Repairs, broken equipment, facility issues
  • Security: Safety concerns, unauthorized access, suspicious activity
  • Noise Complaint: Loud neighbors, parties, construction noise
  • Parking Issue: Unauthorized parking, blocked spaces
  • Amenity Problem: Pool issues, gym equipment, clubhouse problems
  • Landscaping: Gardening issues, tree trimming, irrigation
  • Common Area: Cleanliness, lighting, signage
  • Other: General inquiries or uncategorized issues
4

Describe the Issue

Provide detailed information:
  • What: Clear description of the problem or request
  • Where: Specific location (unit number, common area, etc.)
  • When: When the issue occurred or was noticed
  • Impact: How it affects the resident or community
Encourage residents to be specific. Good example: “The pool gate lock is broken and won’t close properly. Noticed on March 15th around 3 PM. Safety concern as children could enter unsupervised.”
5

Add Photos or Videos

Upload visual documentation:
  • Photos of damage or issues
  • Videos showing the problem
  • Screenshots of relevant information
Visual evidence helps administrators and maintenance staff understand and address issues more effectively.
6

Submit Ticket

Click “Submit” to create the ticket. The system:
  • Assigns a unique ticket number
  • Sets initial status (typically “Open” or “Pending”)
  • Notifies administrators
  • Sends confirmation to the resident

​
Managing Tickets (Administrator View)

​
Viewing the Ticket List

Administrators see all tickets for their community: List Columns:
  • Report Date: When submitted (sortable)
  • Resident Name: Who submitted it
  • Unit Number: Resident’s address
  • Category: Issue type
  • Status: Current stage with color-coded badge
  • Content Preview: Brief description snippet
Filters:
  • Community: Select specific community or all communities
  • Status: Filter by status (Open, In Progress, Resolved, etc.)
  • Category: Show only specific issue types
  • Date Range: Tickets within a time period
Sorting:
  • By report date (newest or oldest first)
  • By resident name
  • By category
  • By status
Use the community filter at the top to switch between communities. The selection is remembered for convenience.

​
Reviewing Ticket Details

1

Open Ticket

Click on a ticket row to view full details
2

Review Information

Examine all ticket data:
  • Complete description
  • Submitted photos/videos
  • Resident contact information
  • Community and location details
  • Submission timestamp
3

Assess Priority

Determine urgency based on:
  • Safety implications
  • Number of residents affected
  • Potential for property damage
  • Community policies

​
Ticket Workflow

​
Status Progression

Tickets move through these typical stages:
1

Open / Pending

Initial Status
  • Ticket just submitted
  • Awaiting administrator review
  • Not yet assigned or actioned
Actions:
  • Review ticket details
  • Categorize correctly if needed
  • Assess priority
2

In Progress / Assigned

Work Started
  • Issue acknowledged
  • Assigned to staff or vendor
  • Action being taken
Actions:
  • Update ticket with action taken
  • Add comments on progress
  • Upload photos of work in progress
  • Update resident on timeline
3

Resolved

Issue Addressed
  • Problem fixed or request completed
  • Awaiting resident confirmation
  • May reopen if issue persists
Actions:
  • Document resolution
  • Add final photos
  • Notify resident of completion
  • Request feedback
4

Closed

Completed
  • Issue permanently resolved
  • Resident satisfied
  • No further action needed
Actions:
  • Archive for records
  • Update knowledge base if applicable
  • Review metrics and response time

​
Additional Status Options

  • Rejected: Ticket doesn’t warrant action (with explanation)
  • On Hold: Waiting for external factors (parts, weather, approvals)
  • Escalated: Requires management or board attention
  • Duplicate: Already reported in another ticket
Status codes may vary by implementation. Check your system configuration for available statuses and their meanings.

​
Updating Tickets

​
Changing Ticket Status

1

Open Ticket

Navigate to the ticket detail page
2

Update Status

Select new status from dropdown:
  • Choose appropriate next stage
  • Status badges show different colors for visibility
3

Add Update Comment

Provide context for the status change:
  • What action was taken
  • Who is assigned
  • Expected timeline
  • Next steps
4

Save Changes

Click “Save” or “Update”. The system:
  • Updates the ticket status
  • Records who made the change and when
  • Notifies the resident (if configured)

​
Adding Comments

Communicate within the ticket:
1

Navigate to Comments

Scroll to the comments section on the ticket detail page
2

Write Comment

Add information:
  • Status updates
  • Questions for the resident
  • Internal notes (if private comments are supported)
  • Resolution details
Optional:
  • Upload additional images
  • Reference related tickets
  • Tag other administrators or staff
3

Submit Comment

Click “Post” or “Add Comment”. The comment:
  • Appears in the ticket timeline
  • May notify the resident (based on settings)
  • Creates an audit trail
Comments create transparency and accountability. Residents can see progress and feel their concerns are being addressed.

​
Creating Tickets on Behalf of Residents

Administrators can submit tickets for residents:
1

Access Ticket Creation

Navigate to the ticket list and click “New Ticket”
2

Select Resident

Choose which resident the ticket is for:
  • Search by name or unit number
  • Select from dropdown
3

Select Community

Choose the associated community (required for multi-community admins)
4

Complete Ticket Details

Fill in category, description, and any images
5

Submit

The ticket is created on behalf of the resident with proper attribution
This is useful when residents report issues via phone, email, or in person at the office.

​
Ticket Categories

​
Common Issue Categories

Examples:
  • Plumbing issues (leaks, clogs, water pressure)
  • Electrical problems (outages, broken lights, outlets)
  • HVAC issues (heating, cooling, ventilation)
  • Structural damage (cracks, roof leaks, foundation)
  • Door and window repairs
  • Appliance malfunctions
Response Priority: Immediate for safety issues, scheduled for routine repairs
Examples:
  • Broken security gates or locks
  • Non-functioning cameras or lighting
  • Suspicious activity
  • Unauthorized access
  • Lost or stolen property reports
  • Safety hazards
Response Priority: High priority, immediate attention for active threats
Examples:
  • Loud music or parties
  • Construction noise outside allowed hours
  • Barking dogs
  • Excessive vehicle noise
  • Arguments or disturbances
Response Priority: Immediate for severe disturbances, logged for pattern tracking
Examples:
  • Unauthorized vehicles in resident spots
  • Blocked driveways or fire lanes
  • Abandoned vehicles
  • Guest parking violations
  • Parking permit disputes
Response Priority: Immediate for fire lane blocks, scheduled for other issues
Examples:
  • Pool equipment malfunctions
  • Gym equipment broken
  • Clubhouse cleanliness
  • Tennis court lights out
  • Playground safety issues
Response Priority: Based on safety impact and amenity usage patterns
Examples:
  • Landscaping needs attention
  • Trash or debris
  • Lighting outages
  • Signage damaged or missing
  • Pathway or sidewalk hazards
Response Priority: Immediate for safety hazards, routine for aesthetic issues

​
Best Practices

Establish response time standards:
  • Emergency (Safety): Within 1 hour
  • Urgent (Functionality): Same day
  • Standard: Within 48 hours
  • Low Priority: Within 1 week
Set clear expectations with residents and track your performance.
Keep residents informed:
  • Acknowledge ticket receipt immediately
  • Provide estimated resolution time
  • Update on progress at key milestones
  • Explain delays or complications
  • Confirm resolution and ask for feedback
Maintain complete records:
  • Take before and after photos
  • Document all actions taken
  • Record vendor information and costs
  • Note any complications or discoveries
  • Keep the ticket history detailed
Identify recurring issues:
  • Review tickets regularly for trends
  • Group related issues
  • Address root causes, not just symptoms
  • Use data to plan maintenance
  • Justify capital improvements with ticket history
Focus on service quality:
  • Follow up after resolution
  • Request feedback
  • Learn from complaints
  • Recognize when extra effort is needed
  • Build trust through transparency

​
Reporting and Analytics

​
Ticket Metrics

Track key performance indicators:
  • Response Time: Average time to first response
  • Resolution Time: Average time to resolve tickets
  • Open Tickets: Current unresolved count
  • Tickets by Category: Most common issue types
  • Tickets by Status: Distribution across workflow stages
  • Resident Satisfaction: Feedback ratings (if implemented)

​
Generating Reports

Use ticket data for:
  • Board Reports: Monthly ticket summaries for board meetings
  • Vendor Performance: Track response and quality by vendor
  • Budget Planning: Justify maintenance budgets with issue frequency
  • Trend Analysis: Identify seasonal or systemic problems
  • Resident Communication: Share community-wide issues and resolutions

​
Integration with Other Features

  • Resident Profiles: Link tickets to resident accounts for history
  • Documents: Reference community policies when responding
  • Payments: Generate charges for damage repairs or violations
  • Announcements: Notify community about widespread issues

​
Deleting Tickets

Deleting tickets removes important records. Instead of deleting:
  • Mark as “Rejected” or “Invalid” with a reason
  • Close resolved tickets rather than deleting
  • Preserve for audit and history purposes
If deletion is necessary:
  1. Ensure the ticket is truly invalid or duplicate
  2. Document the reason for deletion
  3. Consider archiving instead if the feature is available

Build docs developers (and LLMs) love

Get started for freeTalk to us