Where the integration is set up to do so, an issue a resident reports in the Chainels resident portal creates a ticket in Lavanda, and the work your team does on that ticket can be shown back to the resident.
Chainels is a third-party application and every setup is configured separately, so what is available to your organisation may differ from what is described here. Confirm the detail with your Lavanda contact.
Before you begin
Issue reporting is part of what your organisation has set up with Chainels.
You have access to Operations in the Lavanda PMS.
Your residents know to report issues in Chainels rather than by contacting the site team.
What you need to know
A resident reports an issue in Chainels, choosing a category and describing the problem.
A ticket is created in Lavanda carrying the description and the resident details.
Your team works the ticket in Lavanda: assigning it, setting priority, adding comments and changing status.
Comments and status changes can be shown back to the resident on their original issue.
Because each issue becomes a normal Lavanda ticket, it can be filtered, assigned and reported on alongside every other ticket your team handles.
When would you use it
A resident has reported a repair and you need to find it in the PMS.
You need to reply to a resident about work in progress.
You are reporting to a client or an owner on how quickly requests are resolved.
Things to note
Which details carry across, and how quickly, depends on your configuration. Category and priority mapping in particular varies.
A category chosen in Chainels is matched to the nearest Lavanda ticket category, so it may not land in the one the resident expected.
Priority set by a resident is their own assessment. Check it against your own standards rather than treating it as agreed.
Photographs a resident attaches may arrive as links in the ticket description rather than in the Media section.
A ticket created directly in Lavanda is not normally shown in Chainels.