---
title: "Email me tomorrow’s cleans · BlastoClean docs"
description: "Set up a personal evening email for the next calendar day, with exceptions first and selected locations together."
url: "https://www.blastoclean.com/docs/tomorrows-cleans"
---

# Email me tomorrow’s cleans

Scheduling · Web and mobile · 3 min read · Updated October 14, 2026

**Owners and managers can opt into one personal evening email for tomorrow’s cleans. Choose the locations, send time and planning timezone; the email highlights work that needs attention before listing the day.**

**Email me tomorrow’s cleans** is a personal, optional evening email. It starts
off for everyone, including existing accounts. Each owner or manager turns it
on for themselves; nobody can enroll another staff member or enter an outside
email address.

## Turn it on

On the web, open **Settings → Notifications → Email me tomorrow’s cleans**.
On your phone, in an app version that includes this feature, open
**Settings → Email me tomorrow’s cleans**.

1. Turn on the switch.
2. Select the locations whose schedules you manage.
3. Choose the evening send time and digest timezone. The default is **6:00 PM**
   (**18:00** in the phone app, which takes 24-hour time).
4. Leave **Email me even when there are no cleans** off to skip empty days, or
   turn it on to receive a short no-jobs email.
5. Save your digest.

It goes only to your current account email. Turn the same switch off to stop
future digests. The feature uses the scheduling access already included in
your plan. Combining multiple locations requires Business. There is no plan
change, AI dependency or credit charge.

You can select up to 100 locations on Business; the selection count shows
which locations are included. If a plan change makes a saved selection too
large, the digest pauses. Choose locations within the displayed limit and
save to resume, or turn the digest off.

## What “tomorrow” means

The **digest timezone** determines both the evening send time and the planning
calendar date printed in the email. Selecting one location defaults to that
location’s timezone. Selecting several defaults to the company timezone. You
can choose another named timezone, such as `America/New_York`.

For example, an email sent on October 7 for **October 8** includes October 8’s
bookings at every selected branch. It does not look at a rolling next 24 hours.
Each visit shows its booked local time and timezone, so an east-coast and a
west-coast branch can share one email without implying their 9:00 AM visits
happen at the same instant. A pending reschedule stays at its current booked
time, with a warning, until the change is accepted.

The schedule is checked every 15 minutes. Choose a send time between 4:00 PM and
9:59 PM (16:00–21:59 in 24-hour time, as the field label shows). A delayed send can catch up during the following two hours, within the
same evening; an old digest is not sent the next morning. Named timezones
follow daylight-saving changes.

## What the email contains

Work that needs attention comes first: unassigned or unconfirmed visits,
pending schedule changes, and missing customer, site or time details. Then
come full counts and a compact list grouped by location, with local time,
customer/site, every assigned crew member and status.

Scheduled, confirmed and change-requested visits are included. Canceled,
completed and no-show visits are excluded. Long lists keep their full totals
and show how many more visits or exceptions remain, with links to the correct
location and planning date. Schedule links require sign-in and current access.

The email excludes access codes, private notes, customer contact details,
financial information and attachments. It includes an **as-of timestamp**.
Later edits appear in the live schedule and the existing event alerts; they
do not cause another full digest for that date.

## Access and delivery

Each included location requires an active membership and an effective owner
or manager role there. Being an owner does not add branches outside your
memberships. Access, your opt-in and plan availability are checked again before
dispatch and on a safe retry. Archived locations and deactivated users are
excluded.

There is one digest per person, company and planning date, rather than one
email per branch. Successful sends are not repeated. If the email provider
may have accepted a message but delivery cannot be confirmed, the system
leaves it unconfirmed instead of risking a duplicate. Continue to use the
[schedule](/docs/scheduling-a-visit) as the current source of truth.

The [notification bell](/docs/notifications), customer
[reminders and confirmations](/docs/reminders-and-confirmations), weekly owner
digest and follow-up alerts keep their existing behavior.