When a resident's move-in date arrives in Buildium, Reviewflowz asks them for a review of their new home, after the delay you choose. Every review that comes back is matched to the move-in and its property.
How it works
A resident's lease reaches its move-in date in Buildium.
Within the hour, the resident becomes a contact in Reviewflowz.
The request goes out after your delay.
Their review is matched to the move-in and its property.
What triggers a request
Trigger | When it fires | Who is asked |
Move-in | Within the hour of the move-in date arriving: we read your leases every hour, looking back three days | The residents on the lease |
From each lease we take the resident's name, email and phone, the property and the move-in date. We text only residents who opted in to texts in Buildium. Residents in the EU or UK are never emailed, only texted, and only if they opted in. Residents who have moved out, cosigners and leases with an eviction filed are never asked. Enter move-ins in Buildium by three days after the move-in date: a move-in keyed later than that isn't asked.
When you link a property, we import its last 90 days of move-ins so the reviews you already have are matched to them. If your account isn't set up by location, that import runs when you connect. None of those residents is messaged.
Connect Buildium
Buildium's Open API comes with the Buildium Premium plan, and an admin switches it on.
In Buildium, go to Settings, then Application settings, then Api settings, turn on Open API and save. Then go to Settings, then Developer Tools, and choose Create API Key. Give it View access to Rental properties and units, Leases, Tenants and Account information (read-only is enough), then copy the Client ID and Secret. Buildium shows the secret only once.
In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the Buildium card. Paste the Client ID and Client Secret and click Connect Buildium. A key that can't read what we need is refused on the spot, with the reason. Connecting adds a Move-in trigger, switched off.
Link your properties to locations
Link each rental property you want review requests for to the Reviewflowz location whose review page its residents should see. Cedar Row Property Management links Cedar Row Flats, Elm Street Townhomes and Lakeshore Commons to their own locations. Properties you leave unlinked aren't read. Added a property in Buildium? Click Refresh list. If your account isn't set up by location, every residential property is read.
Set up the request
Timing. Cedar Row emails 7 days after move-in. Delays go up to 7 days, with up to 3 messages, and follow-ups stop once a resident clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, one per request.
Message. The From name is "Cedar Row Property Management", the Subject "Settling in, {{first_name}}?" and the Button text "Review us on Google". Marcus reads "Settling in, Marcus?". Try yours with Send myself a test.
Direct reviews to. Smart routing shows one button and picks the site per resident for your objectives. Cedar Row's is "Get as many reviews as possible" on Google. Show all options on the email gives each site its own button, on email only.
Turn it on
Switch on Move-in. That creates its request, "Buildium move-in". Open it from Sends to, finish the message and click Turn requests on. Residents are asked when they move in from the day after you connect Buildium or link their property, with the trigger on. Asking residents who move in from shows the first day after you connected. A move-in dated before the day residents are asked from, or seen while the trigger was off, is kept for matching and never asked.
When a move-in changes
If a lease is deleted, a resident is removed or moves out, the move-in date is moved to a day that hasn't come yet or an eviction is filed before the request goes out, the request is cancelled. A message already sent can't be pulled back.
See what it brings back
The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. The CRM Integration widget tracks requests, links clicked and reviews matched for Buildium.
Good to know
Syncing shows when we last read your leases, the date from which residents are asked, and how many moved in over the last 30 days with an email or phone we may use. Connection shows your Buildium account ID and its status.
If Buildium stops accepting the key, say it was deleted, the Open API was switched off or the plan changed, an Access refused card appears. Disconnect and connect again with a new key: your property links and triggers are kept.
Only the teammate who connected Buildium can change its settings.
Disconnect stops reading your leases and cancels the requests that haven't gone out. Your contacts, requests, property links and triggers are kept.
We read only what we need. Dates of birth, tax IDs, emergency contacts, rent and deposits are never stored, and nothing is written back to Buildium.