Quick answer
Create maintenance ticket: Open a complete maintenance ticket with priority, owner, evidence, and follow-up so incidents keep context until resolution. In Renteric, follow these key steps: Select the property or unit, Describe the incident and priority, and Attach evidence and assign owners. Finish by validating that the incident is logged, prioritized, and traceable for the team, tenant, and owner.
Before you start
- Know which property or unit has the issue.
- Have an initial description and, if possible, photos or video.
- Decide whether the tenant, owner, or only internal staff should see the ticket.
Step by step
- 1
Select the property or unit
Choose where the issue happens so the ticket is linked to the correct asset and appears in history.
- 2
Describe the incident and priority
Write what happened, since when, what it affects, and mark the urgency as low, medium, or critical.
- 3
Attach evidence and assign owners
Add photos, videos, notes, and assign an internal owner or vendor so no one has to guess the context.
- 4
Define visibility and communications
Choose whether the ticket is shared with the tenant or owner and which update message will be used.
- 5
Save and monitor
Create the ticket and track status changes, timelines, and comments from the maintenance inbox.
Common errors
The ticket does not appear in the expected inbox
It was created without a valid property or unit, or with overly strict visibility.
Edit the ticket, correct the asset, and review the configured audience.
The vendor receives too little context
Evidence, priority, or an actionable description is missing.
Attach photos and complete a resolution-oriented description.
FAQ
Can the ticket be created from the tenant portal?
Yes, if that flow is enabled. Staff can still edit priority and assignment later.
Can I assign more than one owner?
You can keep one primary owner and add collaborators or vendors depending on the team's process.
Does the owner see every comment?
Not necessarily. They only see what the visibility flow publishes for that ticket.
Video guide
What this solves
Open a complete maintenance ticket with priority, owner, evidence, and follow-up so incidents keep context until resolution.
Select the property or unit
What to prepare first
Know which property or unit has the issue. Have an initial description and, if possible, photos or video. Decide whether the tenant, owner, or only internal staff should see the ticket.
Describe the incident and priority
Guided walkthrough
Select the property or unit: Choose where the issue happens so the ticket is linked to the correct asset and appears in history. Describe the incident and priority: Write what happened, since when, what it affects, and mark the urgency as low, medium, or critical. Attach evidence and assign owners: Add photos, videos, notes, and assign an internal owner or vendor so no one has to guess the context.
Attach evidence and assign owners
How to validate the result
Define visibility and communications: Choose whether the ticket is shared with the tenant or owner and which update message will be used. Save and monitor: Create the ticket and track status changes, timelines, and comments from the maintenance inbox. the incident is logged, prioritized, and traceable for the team, tenant, and owner
Save and monitor