You can query for records with no email address to find people who cannot receive email communications. Use this approach to improve contact data quality, identify records that need follow-up, and support communication readiness.
Try a Slate example 💼
Copy this Suitcase ID and paste it in Database → Suitcase Import to import a pre-made example query:
97fd0b3a-4e9e-414e-ae0c-1161e286da7d:slate-admissions-showcase💡 Tip
Find this query and other importable examples in the Admissions Showcase environment.
Reviewing records with no email address
A missing email address can prevent a person from receiving messages, reminders, campaign communications, and other outreach. A query for records with no email address gives your team a working list for data cleanup and follow-up.
The example returns one row per person and includes the person’s first name, last name, email address, and mobile phone. Because the query is designed to find records without email addresses, the email export may appear blank or show a placeholder value.
Building the query
Create the query
Go to Queries / Reports.
Select New Query.
Configure the following settings:
Name: Records with no email address
Folder: Select the folder where the query should be saved.
Type: Configurable Joins
Base: Person
Select Save.
Add the no-email subquery filter
The filter is the core of the query. It checks whether the person has an email address, then returns only records where that email-address check does not find a value.
Does not have an Email Address
Select Subquery Filter.
Name the filter Does not have an Email Address.
Configure the subquery to check the person’s email address field.
In the subquery, add a filter for Person / Email where the email address exists.
Set the parent subquery filter to Not Exists.
Select Save.
This configuration returns people for whom the email-address subquery finds no matching value.
Add exports
Exports do not determine which records qualify for the query, but they control what the reviewer can see in the results. Add exports that help your team identify the person and choose the next follow-up action.
Select Export.
Add exports such as:
Person / First
Person / Last
Person / Email
Person / Mobile Phone
Select Save after each export.
Add the optional Relations join
The importable example includes a Relations subquery join. This join is not required to identify records with no email address, but it can support additional exports if your team wants related-person context for follow-up.
Select Subquery Join.
Create a subquery join that returns a relation row for the person.
Name the join Relations.
Select Save.
Customizing the results
After you identify the core population, adjust the query for your cleanup workflow. For example, you might add filters for active records, specific populations, entry terms, record types, or assigned staff. You can also add exports for phone numbers, addresses, record status, populations, or staff assignments so each reviewer has the context they need.