How should AI responses surface "Only on Nabe" data to agents?
Option 1: With Nabe Tags
Nabe-exclusive data points are subtly tagged inline. Sources section below the draft reinforces the platform's unique value.
✨
Nabe AI
ResidentAgent
Draft a response about parking on N 6th St for my client Sarah
✓ Searching neighborhood data...
✓ Checking resident reviews...
✓ Drafting response...
Here's a draft based on what Nabe residents are saying:
✉
Draft for Sarah Chen
✎
Hi Sarah! Great question about parking on N 6th. Street parking is tight but manageable — most residents say they find spots within 1–2 blocks. There's a garage on Berry St ($250/mo) that several tenants in the area use. The good news: the building at 245 N 6th has a bike room, and the area has great transit (L train is a 4-min walk), so many residents go car-free.
I pulled parking insights from 8 resident reviews and 3 building profiles.
✨ Only on Nabe
8 resident reviews · 3 building profiles · 2 tenant comments about parking
What this does
Tags show agents exactly which insights come from Nabe's unique resident data. Reinforces "you can't get this anywhere else" without disrupting readability.
Option 2: Clean & Action-Focused
No tagging or highlighting. The draft is clean and ready to send. Focus is on the action, not the source.
✨
Nabe AI
ResidentAgent
Draft a response about parking on N 6th St for my client Sarah
✓ Searching neighborhood data...
✓ Checking resident reviews...
✓ Drafting response...
Here's a draft for Sarah about parking on N 6th:
✉
Draft for Sarah Chen
✎
Hi Sarah! Great question about parking on N 6th. Street parking is tight but manageable — most residents say they find spots within 1–2 blocks. There's a garage on Berry St ($250/mo) that several tenants in the area use. The good news: the building at 245 N 6th has a bike room, and the area has great transit (L train is a 4-min walk), so many residents go car-free.
Based on resident reviews and building data. Want me to adjust the tone or add anything?
What this does
Keeps the draft clean and scannable. The agent's focus stays on reviewing and sending, not on where data came from. Faster workflow, less visual noise.