Skip to main content

How requests come into resvu

Updated today

Goal

This article explains the three different ways a request can be raised in Resvu: by a resident, by an admin, or by an unknown person through a public form. All requests are derived from workflow templates and appear in the dashboard once submitted.

Before You Get Started

You will need to have the correct permissions set in order to manage requests and workflow templates. To check this, navigate to: Settings ➡️ Admins ➡️ Edit your chosen admin ➡️ Select Roles & Permissions ➡️ Scroll down to Workflows ➡️ Expand Requests and ensure that Requests has full access selected.

Overview

All requests are derived from workflow templates. The templates you see in the system represent the types of requests residents or admin staff can raise. Once a request is submitted through any of the methods below, it appears in the Dashboard where it can be managed.

Workflow templates can be tailored to specific communities, which is why a resident in one community may see a different list of request types to a resident in another community.

There are three ways a request can enter the system:

  • A resident raises it through the resident portal or app

  • An admin raises it through the Dashboard or the Outlook add-in

  • An unknown person submits it through a public form link

Training Video

This video goes through the three ways a request can enter the system

Method 1 - Resident submissions

Residents can raise requests through either the Resvu mobile app or the web portal. The experience is the same on both.

Step 1 - Open Requests in the resident portal

The resident navigates to the Requests section in the resident portal or app.

Step 2 - Select a request type

The resident chooses from the list of workflow templates available to them. The list shown depends on which templates have been assigned to their community — they will only see the templates that apply to their specific community.

Step 3 - Fill out and submit the request

The resident fills in the fields (mandatory fields are marked with a star), then presses Submit Request.

Once submitted, the request appears in the Dashboard with the resident listed as the requester.

Method 2 - Admin submissions

Admins can raise requests on behalf of a resident, or internally, using either the Dashboard or the Outlook add-in.

Option 1 - Raising a request from the Dashboard

Step 1 - Open the Dashboard

Navigate to the Dashboard from the admin console.

Step 2 - Select New Request

Press the New button and choose New Request.

Step 3 - Choose the community and workflow template

Select the community the request relates to, then choose the workflow template.

Step 4 - Choose the requester

You can select either a resident (if you are raising the request on their behalf) or an admin (if the request is internal or you want to assign it to yourself).

This choice controls whether the request is visible to the resident or treated as internal only.

Step 5 - Fill out the request fields

Complete the form fields — these are the same fields the resident would see. Mandatory fields are marked with a star. Optional fields can be left blank.

Step 6 - Submit

Press Submit. The request will now appear in the Dashboard. The requester can be changed later if needed by clicking into the field and selecting a different resident or admin.

Option 2 - Raising a request from the Outlook add-in

The Outlook add-in allows admins to convert incoming emails directly into Resvu requests, including any attachments.

Step 1 - Open an email and launch the add-in

With the email open in Outlook, click the Resvu add-in. Your sign-in details will auto-populate if you're already logged in.

NOTE: your workspace is the admin URL before au.resvu.io

For the Resvu Demo environment the admin URL is https://demo.au.resvu.io/

the Workspace is demo.

if you require assistance reach out to [email protected] and they will be able to assist you.

Step 2 - Select New Request

Click New Request.

Step 3 - Configure the request

Select the community, choose the workflow template, and choose the requester (resident or admin). You can also choose to include the email contents in the activity log and attach any email attachments.

Step 4 - Fill out the form and submit

Complete the fields as you would from the Dashboard and press Submit. You can then click View in Admin Console to open the new request in a new tab.

The email contents will appear in the activity log as an internal comment, and any attached images or files will be added to the request automatically, removing the need to upload them separately.

Method 3 - Public submissions

Public submissions allow anyone with the form link to submit a request, even if they don't have a Resvu account. This is useful for property managers, family members raising issues on behalf of residents, or anyone external who needs to log an issue.

Step 1 - Enable external access on the workflow template

Go to Workflows ➡️ Options ➡️ View ➡️ Advanced, and toggle on Allow external access.

Step 2 - Copy the public form link

Once enabled, a public link is generated. Copy it and share it where needed — for example, as a form embedded on your strata management company's website.

Step 3 - External user submits the request

When the link is opened, the public form displays. Because the person submitting is unknown to the system, three additional fields are added automatically:

  • Name

  • Email

  • Community address and scheme

The remaining fields match the workflow template as usual. Once submitted, the person can click View Submission to see their request reference number, and can also Download a PDF copy of the submission for their records.

What happens in the Dashboard after a public submission

Public submissions appear in the Dashboard alongside all other requests. There are two important details to know:

Community matching: If the submitter entered a valid community scheme number, Resvu will automatically associate the request with the correct community. You can confirm this by adding the Scheme / CTS number column to the dashboard view.

Note: once you associate a Community to the public submission, it cannot be changed.

Requester matching: The requester will initially be shown as a Guest (using the name and email from the public form). If the request actually relates to an existing resident, an admin can update the requester by opening the request and changing it to the correct resident. This links the request to that resident's profile going forward.

Summary

Requests can enter Resvu through three paths:

  • Residents submitting via the resident portal or app

  • Admins submitting via the Dashboard or the Outlook add-in (on behalf of a resident, or internally)

  • External people submitting via a public form link, with community and requester details able to be matched after submission

All submissions land in the same Dashboard, ready to be managed from there.

Did this answer your question?