Customer Support

How to run nps and csat surveys as Real Estate Founders

Customer SupportFor Real Estate Founders2 apps12 steps~24 min to set up

You close a deal on a multifamily property and six months later you realize your tenants have no formal way to tell you the roof is leaking or the HVAC is loud. You're collecting feedback through a mix of text messages, a Google Form you built in 2023, and the occasional Yelp review you find by accident. NPS and CSAT are things you know matter — especially when you're raising a second fund and LPs ask about tenant retention rates — but standing up a real survey system means paying for Typeform, figuring out how to pipe responses into HubSpot, and building a report by hand every quarter. Nobody on your team has time for that, so it doesn't happen.

Build this on Starch → See the apps used

Customer SupportFor Real Estate Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated NPS and CSAT survey system tied to your tenant and investor contact records in your Starch CRM, so every relationship has a feedback trail

A live dashboard that surfaces response scores by property, tenant cohort, or LP segment — no manual report assembly required

Follow-up automations that flag detractors in your CRM and draft a personal outreach email the same day a low score comes in

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM Email Agent

Data sources & config

Connect Gmail using Starch's scheduled-sync integration so survey emails send from your real address and responses sync back automatically. Your tenant and LP contact data lives in the Starch CRM. Connect your survey response form data by linking Google Sheets from Starch's integration catalog — the agent queries it live when your dashboard or automation runs. For any survey tool like Typeform or Jotform that doesn't have a direct sync, Starch automates submission retrieval through your browser — no API needed.

Prompts to copy

Build me an NPS survey workflow for my tenants. After a tenant's 90-day mark and again at lease renewal, send them an email survey asking 'How likely are you to recommend living here?' on a 0–10 scale, then one follow-up question based on their score. Log every response back to the tenant's contact record in my CRM with a score, date, property name, and the verbatim comment.

Create a CSAT trigger: whenever a maintenance ticket is resolved, send the tenant a one-question satisfaction survey 24 hours later. If their score is below 7, automatically flag the contact in my CRM as 'needs follow-up' and draft a personalized apology email for me to review and send.

Build me a survey response dashboard that shows average NPS by property address, CSAT trend over the last 90 days, percentage of detractors vs promoters, and a list of every open follow-up flagged in the last 30 days.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect Gmail through Starch's scheduled-sync integration so outbound survey emails go from your real address and inbound replies are captured automatically in your tenant contact records.

2 In your Starch CRM, add a custom field for NPS score, CSAT score, last survey date, and survey follow-up status — describe these fields in plain English and Starch builds the schema.

3 Tell Starch to build a 90-day NPS trigger: 'When a tenant contact's move-in date is exactly 90 days ago, send them an NPS email from my Gmail asking the standard 0–10 question and one open-text follow-up. Log the response to their CRM record.'

4 Tell Starch to build a lease-renewal NPS trigger: 'Sixty days before a tenant's lease end date, send another NPS survey. Tag the contact with their score and whether this is their first or repeat response.'

5 Configure the maintenance CSAT flow: 'When I mark a maintenance ticket as resolved in my CRM, wait 24 hours, then send a one-question CSAT email. If score is under 7, flag the contact for follow-up and draft a reply for my review.'

6 Set up an LP sentiment survey: 'Every quarter, send my investor contacts a short CSAT survey about communication quality and reporting. Log responses with their LP tier and property exposure so I can correlate satisfaction with fund performance.'

7 Build the response dashboard: 'Show me average NPS by property address, CSAT trend by month, promoter vs detractor split, and a table of every contact flagged for follow-up in the last 30 days — sorted by score ascending so the worst responses are at the top.'

8 Use the Email Agent to draft follow-up messages for detractors: 'For every tenant flagged as a detractor this week, draft a personal email acknowledging their concern, referencing the property name and their specific comment, and offering a call.'

9 Add a monthly digest automation: 'Every first Monday of the month, send me a Slack summary of the prior month's NPS and CSAT averages by property, count of open follow-ups, and any contacts whose score dropped more than 2 points from their last survey.'

10 Connect Google Sheets from Starch's integration catalog if you're already logging responses there — the agent queries it live and pulls historical scores into your dashboard without a full migration.

11 Review your CRM contacts quarterly and ask Starch: 'Which tenants haven't received a survey in more than 180 days? List them by property and move-in date.' Use this as a manual outreach prompt for properties where automated triggers may have missed someone.

12 Use your survey data during LP reporting: tell Starch to pull average tenant NPS per property and include it as a section in your next investor update, alongside occupancy rate and NOI figures.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 Tenant Feedback Review — 3-Property Portfolio

Sample numbers from a real run

Maple St. Fourplex — NPS	72
Riverside Duplex — NPS	41
Oakwood 8-unit — NPS	68
Maintenance CSAT (portfolio-wide)	74
Open detractor follow-ups	4
LP satisfaction CSAT (Q1)	88

You ran NPS surveys at the 90-day mark for every tenant who moved in during Q4 2025 — 11 tenants across three properties. Maple St. and Oakwood came in strong at 72 and 68 NPS respectively. Riverside Duplex flagged immediately: two tenants scored 3 and 4, both citing slow responses to HVAC complaints. Starch flagged both contacts in your CRM and the Email Agent drafted personalized outreach within the hour — you reviewed, edited one line, and sent both. You also ran your first LP CSAT survey ahead of a fund close call; your five LPs scored you an 88, which you dropped into the investor update Starch assembled from your QuickBooks and Plaid data. Going into the LP call, you knew your weakest property by name, had already followed up with the unhappy tenants, and had a number — 88 — to point to on the investor side. That's a 2-hour setup for data most real estate operators of your size simply don't have.

Measurement

How you'll know it's working

Net Promoter Score by property address (tracked per survey cycle)

CSAT score per resolved maintenance ticket, trended by month

Detractor follow-up rate — percentage of sub-7 scores that received a personal reply within 48 hours

Tenant retention rate correlated with NPS cohort (promoters vs detractors at prior renewal)

LP satisfaction CSAT by fund and quarter, referenced during capital raise conversations

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Typeform + HubSpot + Zapier

Typeform handles the survey UI well, but you're paying three subscriptions and building Zaps to get response data into HubSpot — and HubSpot still won't know it's looking at a tenant from a specific property unless you configure that mapping manually.

Google Forms + Google Sheets

Free and fast to set up, but responses live in a spreadsheet disconnected from your CRM, follow-up is entirely manual, and you'll rebuild the same pivot table every quarter to get a number you can show an LP.

SurveyMonkey

Solid survey tooling and decent reporting inside the platform, but it has no concept of your properties, your tenant contact records, or your deal pipeline — so every insight stays siloed and you're still copying data by hand.

Qualtrics

Enterprise-grade and genuinely powerful, but priced and scoped for teams with a dedicated CX analyst — not a solo operator managing three properties who also closes deals and handles LP communications.

On Starch RECOMMENDED

One platform — crm, email agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch actually send surveys from my real Gmail address, or does it come from some generic platform email?

Starch syncs with Gmail directly — surveys go out from your real address. One thing worth knowing: the Gmail OAuth consent screen currently shows the underlying connector name rather than 'Starch,' so if a tenant looks carefully at the authorization screen, they'll see that. Starch-verified branding is on the roadmap. For most operators this is a non-issue, but it's honest to say it upfront.

What if my tenants submit maintenance requests through a property management platform that isn't in Starch's integration catalog?

If the platform has a web interface you can log into — AppFolio, Buildium, Rent Manager — Starch can automate actions through your browser directly, no API needed. You'd tell Starch: 'When a ticket is marked resolved in Buildium, wait 24 hours and send a CSAT email.' That's a browser automation workflow, and it's a standard Starch pattern.

Does Starch store historical survey responses, or is it querying them live each time?

Survey responses logged to your Starch CRM are stored there and available historically. If your responses come from an external source like Google Sheets, Starch queries that live when your dashboard runs rather than maintaining a separate archive. For most feedback workflows this works fine; if you need a long-term data warehouse of every response going back years, Starch isn't a data warehouse product — it's a live data surface.

Can I segment NPS scores by property, by tenant type, or by lease length?

Yes — because the NPS scores live as fields in your CRM contacts, and your CRM schema is built around how you work. Tell Starch to add a 'property address' and 'lease type' field to tenant contacts when you set things up, and your dashboard can slice scores any way you want: 'Show me NPS for month-to-month tenants vs annual leases at Riverside Duplex over the last six months.'

Is Starch SOC 2 certified? Tenant contact data is sensitive and I have LPs who will ask.

Starch is not currently SOC 2 Type II certified. If your LPs or institutional partners require SOC 2 before data can touch a platform, that's a real constraint to weigh. For operators running smaller portfolios with individual LP relationships, this is typically not a blocker — but it's worth knowing before you make a decision.

What's the fastest way to get this running if I already have tenant contacts in a spreadsheet?

Tell Starch: 'Import my tenant contacts from this Google Sheet — map the property address column to a CRM field called Property, the move-in date column to Move-In Date, and email to Email. Then build me an NPS trigger that fires 90 days after move-in for any contact where the NPS Score field is blank.' Starch connects Google Sheets from its integration catalog and queries it live. Import takes a few minutes; your first surveys can go out the same day.