Email address mapping for CSV contact imports

Business problem

The current contact import flow via CSV only supports Phone Number and Name as native fields, lacking a standard option for Email. This forces users to create custom fields as workarounds, skips contacts that only have an email address, and creates friction for teams who primarily communicate via email-centric or omnichannel workflows.

Wished result

Native email address mapping during the CSV contact import process. Users should be able to import contacts using an email address as a primary identifier, allowing for seamless database migration and support for email-based communication without requiring a phone number for every record.