Overview
Some things worth noting upfront:
the more data sources you add, the more complete a picture you get of your customers' experience and the goings-on within your communities.
different feature bundles include different data sources - contact us at [email protected] if you’re unsure what your current bundle includes.
Benefits
The below table gives you an idea of the benefits of connecting each data source; for further information on each, use the table of contents at the side to navigate through each type.
Below is the high level process; you can find technical documentation here.
Provide us with the following information:
Community name
Unit count
Community email address(es)
Grant permissions to our app.
Add the required inboxes to a security group or authorize permissions.
Adjust access control.
And that's it! The data will start flowing through our models.
Notes
You can also connect individual staff members' inboxes. You'll need to let us know when staff leave/join though.
It's OK if there are multiple inboxes per community (e.g. a separate one for leasing vs maintenance, etc)
Reviews/Surveys/Other Customer Feedback
Google Reviews
Contact us to let us know you are interested in this data plug
Navigate to this URL to authorize access
Log in to your Google account (note that the person doing this must have administrative rights)
Click Authorize
Data will start flowing through our models and contributing to your community scores and summaries.
Note that it's also possible to send this data via csv extracts if you'd prefer (though we would recommend the direct connection to ensure data freshness).
Surveys
Let us know you are interested in this data plug
Send us a sample extract from your survey provider
We'll send you the URL to an area (Amazon S3 bucket) for you to send files (ideally in csv format), and a key to access the area
Agree any frequency, naming convention, etc details with us
That's it! We'll start picking up the files and ingesting the data.
Notes
Anonymous surveys are still worth sending as long as there is a community identifier (e.g. community name).
Reputation.com
If you use reputation.com and receive the data feed from them, we can ingest this information.
More information on how to connect coming soon.
SMS
If your company uses text messages to speak with residents, we can consume these conversations. In order for us to ingest these data, your options are:
provide your Twilio (or other provider) account API
provide the API of your preferred provider
provide a timed (daily/ hourly) extract
Voice
If your company uses calls to speak with residents, we can consume these conversations as voice transcripts. In order for us to ingest these data, your options are:
provide your Twilio (or other provider) account API
provide the API of your preferred provider
provide a timed (daily/ hourly) extract
Resident feed
Let us know you are interested in this data plug
Send us a sample extract from your PMS
We'll send you the URL to an area (Amazon S3 bucket) for you to send files (ideally in csv format), and a key to access the area
Agree any frequency, naming convention, etc details with us
That's it! We'll start picking up the files and ingesting the data.
General notes on sending csvs
No need to send the full list with every extract - a file with changes only (i.e. removals/additions) is fine.
If there is no information to send, we recommend sending an empty file with headers only.