Skip to main content

FluentCRM

#Feature Request

Feature Request: Allow contacts/leads without an email address

Now that FluentCRM already supports SMS and WhatsApp messaging, I think it is becoming increasingly important to allow contacts or leads to be created without requiring an email address.

Currently, email is still mandatory when creating a FluentCRM contact. This creates a significant limitation, especially for B2B sales workflows.

In many real-world situations, the first piece of information we get from a lead is simply:

  • Name
  • Company
  • Phone number / WhatsApp

And sometimes we do not get the email until much later in the sales process.

If SMS and WhatsApp are becoming native communication channels inside FluentCRM, requiring an email before someone can even exist as a proper CRM contact feels increasingly inconsistent.

Ideally, FluentCRM could allow a contact to be created using either:

Email OR phone number as the primary identifier

and then enrich the contact later when additional information becomes available.

This would be especially useful for:

  • B2B prospecting
  • WhatsApp leads
  • SMS campaigns
  • Phone enquiries
  • Sales teams collecting leads manually
  • Events, networking and offline lead generation
  • Forms where asking for an email creates unnecessary friction

For us, this can become a real blocker when we have a perfectly valid lead and phone number, but simply do not have their email yet.

With Messaging already moving beyond email, I think the contact model should eventually do the same.

  • 7 likes
  • 1 comment

Debo Ogunrinde

Jorge de los Reyes 

Ai response..

FluentCRM requires an email address because email serves as the unique identifier (the core database key) for every contact record.

In digital marketing and WordPress user management, an email address is necessary for several fundamental reasons:

1. Database Architecture & Unique Mapping

In FluentCRM, a "Contact" is mapped directly to a unique email address string. Without an email address, the system cannot create a database row for that person. Even if you are utilizing the new SMS marketing features in FluentCRM 3.0, the plugin treats the email as the primary anchor for the contact profile.

2. WordPress User Syncing

FluentCRM integrates deeply with the WordPress user database (wp_users), where an email address is a strict requirement for registration. If you want to automatically sync customers from WooCommerce, members from MemberPress, or standard WordPress users into FluentCRM, they must have an email to sync properly.

3. Compliance and Unsubscribe Tracking

Global anti-spam regulations (like CAN-SPAM and GDPR) require automated systems to track consent and unsubscribes accurately. Email marketing networks rely on the email address to manage:

  • Suppression lists (ensuring bounced or unsubscribed users aren't messaged again).
  • Double opt-in verification to prevent fake signups.

Workarounds if you only want to collect Phone Numbers

If your business model only collects phone numbers (e.g., for SMS-only marketing), you can bypass this limitation using one of two methods:

  • Generate Placeholder Emails: Use an automation tool (like Zapier, SureTriggers, or Fluent Support workflows) to automatically generate a fake placeholder email (e.g., phone_number@yourdomain.local) when a user signs up with just a phone number.
  • Use a Multi-Field Form Builder: Use Fluent Forms to hide the email field from the user, use a hidden field to auto-populate a random placeholder email, and map the user's phone number directly into FluentCRM's phone field.