Skip to content
Urbero
  1. Help
  2. /features
  3. /comments

Comments

Talk about a unit where the unit lives. Mention a teammate. Keep the thread honest.

Last updated: 2026-05-10

Comments are short notes attached to a unit. They show on the unit detail page as a thread, and they preview in the Notes column of the Inventory table. Today only units carry comments — a later release will extend the same primitive to deals, buildings, and team threads.

Where comments show up

  • Unit detail page — the Comments section near the bottom shows the full thread, oldest at the top.
  • Inventory table — Notes column — hover the Notes cell to see the last two comments from the past 90 days in a popover. The popover also has an inline composer.

Posting a comment

  1. Type into the composer. The body cap is 280 characters — short, focused notes only.
  2. Optionally @mention a teammate (see below).
  3. Click Post.

Comments save immediately and appear in the thread for everyone with read access.

Why this matters

A note pinned next to the unit is searchable a year from now. A note in a group chat is gone by lunchtime.

@mentions

To pull a teammate's attention, type @ in the composer. An autocomplete dropdown opens with brokerage members of the unit's owning brokerage. Keyboard: ↑ / ↓ to move, Enter or Tab to pick, Esc to close. You can't mention yourself or anyone outside the brokerage.

How tokens are resolved

The system resolves each @token in this order:

  1. Exact email match — @taylor.gardner@livinnewyork.com lands on that account.
  2. Email prefix match — @taylor.gardner lands on the account whose email starts with taylor.gardner@….
  3. First-name match — @taylor lands on the first Taylor on the brokerage.

If you have two Taylors and want a specific one, use the email-prefix form.

Every mention also lands on your /inbox page (sidebar link), which mirrors the bell inbox.

Correction replies (the ↳ pattern)

Comments are append-only — no Edit button, and the system never edits a past comment. To fix a typo or update a prior statement, post a reply; the convention is to start the reply with ↳ correction:.

Example:

Taylor — 2026-05-10 9:14 AM Owner is asking $4500, willing to come down to $4300 for a 24-month lease.

Taylor — 2026-05-10 9:16 AM ↳ correction: $4350 not $4300. Heard from him just now.

The ↳ marks the reply as a correction. The original stays put so a month from now anyone can see what was said, when, and how it was corrected.

Audience: who can read this comment

Every comment has an audience scope, picked when you post.

  • Internal (brokerage only) (default) — only brokerage staff (admins, agents, photographers of your brokerage) can read it. Landlord admins, viewers, and external roles can not see it. Use this for agent-to-agent context, pricing strategy, or anything you wouldn't want forwarded.
  • All viewers (incl. landlord) — visible to everyone with read access to the unit, including landlord admins and viewers. Use this for status notes the landlord side legitimately needs.

The default of Internal (brokerage only) is deliberate: it stops accidental leaks of internal commentary to a landlord viewing their own portfolio. There's no global default to flip — you pick per comment.

Typed comments — suggested rent

Most comments are plain text. Select the Suggested rent kind in the composer and the comment carries a dollar value alongside the body. The latest top-level suggested-rent comment surfaces in the Suggested Rent column on the Inventory table, so the whole team sees the same recommendation without scrolling a thread. Use this when you've done the comp math and want the number visible at a glance.

/inbox — your mention feed

The /inbox page lists every comment that mentions you. Each row shows the unit, author, body, and a relative date — click to jump in context. Mark all read clears the unread count, same pattern as the bell. Self-mentions are filtered.

The bell inbox is for system notifications. The /inbox is for human mentions. Separate, so neither becomes noise.

Related