When a resident moves in, renews their lease or has a service request closed in Yardi Voyager, Reviewflowz asks that resident for a review of their property. Each moment has its own request.
How it works
A resident moves in, renews their lease or has a service request closed in Voyager.
Within about two hours, Reviewflowz reads the resident and the property.
The request for that moment goes out after your delay.
The resident's review is matched to the resident and the property.
What triggers a request
Trigger | When it fires | Who is asked |
A resident moves in | The move-in date has arrived | The resident |
A resident renews their lease | The new lease term starts | The resident |
A resident's service request is closed | The service request is closed in Voyager | The resident the request is for, if they still live there |
The three triggers are off when you connect. Switch on the ones you want, and each sends to its own request: Yardi move-in, Yardi lease renewal and Yardi service request closed. A service request closed within 14 days after a resident's move-in isn't asked about separately.
When the business or the resident is in the EU, the UK or Switzerland, residents aren't asked.
When you link a property, its last 90 days are imported, so reviews you already have are matched to their residents. Nobody is messaged for those.
Connect Yardi Voyager
Reviewflowz reads your residents and service requests through Yardi's Service Requests interface. You fill in six fields, and get them like this:
Interface entity and Interface license. Your Yardi account rep licenses the Service Requests interface for your portfolio and sends you both. Ask your rep, or open a case in Client Central, and paste this:
Please license the Service Requests interface (itfServiceRequests) for our portfolio database and send us the interface entity and interface license. We'll use it, with an interface user we create, to connect Reviewflowz.
Interface user name and Interface user password. In Voyager, open System Administration, then Security, then Add User, and create a user for Reviewflowz that can read the Service Requests interface and your properties. Each vendor gets its own interface user, so this changes nothing for your other tools.
Voyager URL. In Voyager, open Administration, then About, then URL, and copy the part before /pages, like https://www.yardiasp14.com/48213harborview.
Database name. The name of your Voyager database.
Then enable the interface on each property you want under Interfaces, then Configuration (or Bulk Property Configuration for many at once).
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the Yardi Voyager card. If you already have an integration connected there, click Connect another integration first. Fill in the six fields, then click Connect Yardi Voyager. Your Voyager properties fill the Properties list.
Link your properties to locations
Under Properties, give each Property in Voyager the Reviewflowz location whose review profiles its residents should see. Only linked properties are read. Harborview Residential links Harborview Lofts and Maple Court Apartments, and leaves Riverside Commons unlinked. If your Reviewflowz account has one location, every Voyager property is linked to it for you the first time you connect.
Set up the request
Timing. Your delay counts from the moment itself: the move-in date, the start of the new lease term or the close of the service request. Harborview emails new residents 3 days after they move in.
Channel. Email, SMS or WhatsApp, set per message.
Message. Harborview's From name is "Harborview Residential", the Subject "Settling in, {{first_name}}?", which Ava Thompson reads as "Settling in, Ava?", and the Button text "Review us on Google". Try yours with Send myself a test.
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Harborview aims for as many Google reviews as possible. Show all options on the email lists every site instead.
Turn it on
Switch on the triggers you want, then open each request, such as Yardi move-in, and click Turn requests on. The Syncing panel's Asking residents about events after shows when you connected.
When a move-in is reversed or a request reopens
If a move-in is reversed, the resident moves out, or a service request is reopened before its request goes out, the request is withdrawn.
See what it brings back
Every review is matched to the resident and the property it came from. The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped for each request. The CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from Yardi Voyager.
Good to know
If the interface user's password changes or the user is disabled, the card turns red. Click Enter new credentials and enter the current login. Your property links and requests stay as they are.
If the card says Voyager no longer accepts your interface entity and license, ask your Yardi account rep to check the Service Requests license for your database. We check again every day and pick it up on our own.
If a linked property isn't set up for the interface, the panel names it. Enable the interface on it under Interfaces, then Configuration. Your other properties keep working.
The Syncing panel counts residents who can't be asked, such as a resident with no email or phone. They're still kept, so a review from that resident is matched by name.
Disconnect stops the reads and withdraws every request that hasn't gone out.
