---
title: "Querying for Records with No Email Address"
slug: "querying-for-records-with-no-email-address"
status: "new"
updated: 2026-06-18T22:19:32Z
published: 2026-06-18T22:19:32Z
canonical: "knowledge.technolutions.net/querying-for-records-with-no-email-address"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Querying for Records with No Email Address

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](/docs/suitcase-import) ID and paste it in **Database → Suitcase Import** to import a pre-made example query:

```SuitcaseID
97fd0b3a-4e9e-414e-ae0c-1161e286da7d:slate-admissions-showcase
```

> [!NOTE]
> 💡 Tip
> 
> Find this query and other importable examples in the [Admissions Showcase environment](/v1/docs/showcase-environments).

## 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.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Querying for Missing Email Address.png)

## Building the query

### Create the query

1. Go to **Queries / Reports**.
2. Select **New Query**.
3. 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
4. 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

1. Select **Subquery Filter**.
2. Name the filter **Does not have an Email Address**.
3. Configure the subquery to check the person’s email address field.
4. In the subquery, add a filter for **Person / Email** where the email address exists.
5. Set the parent subquery filter to **Not Exists**.
6. 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.

1. Select **Export**.
2. Add exports such as:
  - **Person / First**
  - **Person / Last**
  - **Person / Email**
  - **Person / Mobile Phone**
3. 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.

1. Select **Subquery Join**.
2. Create a subquery join that returns a relation row for the person.
3. Name the join **Relations**.
4. 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.