The single email limit in Salesforce is a daily total for the whole org, not per user. It counts every outside address your org sends a single email to from Apex, the API and, in newer orgs, flows and email alerts, and the day runs from midnight GMT. Pick your edition above to see the limit, what counts toward it and how to check it.
What counts and what doesn't
Orgs created in Spring '19 or later count email alerts, simple email actions, flow Send Email actions and REST API sends to outside addresses as well as Apex. Older orgs count only Apex and the other APIs, and the tool's Why says how to find your org's date. Every address in To, Cc and Bcc counts, duplicates included, and so do your own users' addresses unless Apex sends to them by user ID.
Emails written in the composer, Compliance BCC copies and system emails such as password resets don't count. The number of sendEmail calls in one Apex transaction is a separate limit, and so is the API call allocation your integrations share.
How to check and reserve
Read SingleEmail in the org's limits resource, or paste the Apex snippet from the section below into the Developer Console. Before a large job, call Messaging.reserveSingleEmailCapacity with the number of addresses: it fails at once if the day would run out, instead of halfway through the job.
When the single email limit runs out
Sends fail until midnight GMT and are not retried, so queue them for after the reset. Send internal notifications by user ID so they stop counting. Salesforce Support raises the limit only for production orgs, never for marketing or sales follow ups, and its limit increase article says a lasting increase needs DKIM and a low rate of permanent failures.
If Apex mainly writes enrichment back to Salesforce records, Oneprofile can do that from one table, at a rate you set.
