The Core Issue with Contact Columns
Smartsheet Contact columns are fundamentally not reliable because they don’t represent people consistently. The same person can appear as a name in one place and an email address in another, depending on user status, permissions, ownership, or whether the data is viewed in a sheet, report, automation, or export. Since there’s no way to control or lock the display format, the column behaves differently across contexts—making it unpredictable and impossible to standardize.
Why This Makes Them Unusable
This inconsistency breaks core functionality. Reports treat names and emails as different people, automations can misfire or route incorrectly, and exports and integrations require constant cleanup. You can’t reliably group, count, automate, or integrate contact data when the same value changes formats behind the scenes. As a result, Contact columns cannot be trusted as a system‑of‑record field.
Call to Action
This needs a product‑level fix. At a minimum, Smartsheet should allow admins or sheet owners to enforce a consistent representation (name only, email only, or both) or expose a stable, underlying identifier that reports, automations, and integrations can reliably use. Until this is addressed, teams are forced into workarounds that add complexity and undermine confidence in the platform.
