I’ve worked with several call center clients recently, and a recurring pain point is that HubSpot treats email as the unique identifier for contacts — but phone number has no equivalent enforcement. It isn’t required, doesn’t need to be unique, and accepts free-text input that breaks any downstream deduplication logic.
For businesses that operate entirely over SMS or phone (no email touchpoints), this is a real barrier to adoption. I now have to explicitly caution these clients about data integrity risks and, in some cases, recommend a phone-first CRM instead — which isn’t a conversation I want to have.
The ask: A portal-level setting that elevates the phone number property to a strict, formatted, primary-key-capable field. This could include:
- E.164 or standardized formatting enforcement
- Uniqueness validation at the contact level
- Deduplication logic based on phone rather than (or in addition to) email
This would open HubSpot up to a meaningful segment of call center and SMS-based operations that currently can’t rely on it as their system of record. Bundled with phone number formatting tools, it’s also a natural micro-product or add-on opportunity.
A simple “Call Center Mode” toggle in portal settings would be the ideal UX — low friction, opt-in, and scoped so it doesn’t affect existing email-primary workflows.