Emails 1pm sends | 1pm Help

1pm sends emails sparingly, and there is no "you might also like" upsell. Most of what 1pm sends is in direct response to something you or your crew did.

Three things aren't, and they're worth naming up front so none of them arrives as a surprise. There's a short onboarding series over your first few weeks (see Informative emails below). There's an optional weekly summary, off until you turn it on. And a dormant account does get written to, several times over, before anything happens to it. All three are covered below.

This article catalogues the lot: what gets sent, when, why, and what you can do if you'd rather not receive a particular one.

The sender domain

Every transactional email from 1pm to you comes from the mail.1pm.app sender domain. Replies route to [email protected], which is a real inbox a real person reads.

Emails 1pm sends to your clients on your behalf are different. Invoices, card requests, agreements, event portal invites, appointment emails and your automations' client emails go out under your business name, and a client who replies reaches your account's email address, not us. If you have verified your sending domain, they are sent from your own address too, the same one your lead emails use. Lead emails work slightly differently: a reply goes back into that lead's conversation in 1pm (see how lead reply emails work).

Emails you may receive after signing up for a free trial, or on an ongoing basis (until you unsubscribe), containing links, information and tips come from news.1pm.app, and these are generally sent automatically (until you unsubscribe or the email flow ends).

If you're sifting your inbox for a missing message, search "1pm" or "mail.1pm.app" rather than the subject line. Search across all folders and tabs (Promotions, Updates, Spam, Junk), since the first time 1pm emails a new address the receiving server often hasn't decided where to file us yet.

Account-related emails

These are tied to your 1pm account itself. You get them because of something you did on your sign-in or account settings.

The welcome email. Sent the moment you sign up. Confirms your account is created and links you back into the app. One-off.
The email-verification code. A six-digit code sent the moment you sign up, and again whenever you resend. Valid for 30 minutes. See Verifying your email address.
The password-reset link. Sent whenever you tap Forgot password? on the sign-in page. Single-use, valid for 24 hours. See Resetting your password.
The email-change confirmation. Sent to your new email address when you change the email on your account. The link in this email is the only way the change actually goes through; if you never click it, the change is dropped. See Your profile and display name.
The 2FA backup-code notice. Sent when you enable two-factor authentication. Contains a printable set of backup codes in case you lose your authenticator app. See Two-factor authentication.
The export-ready notice. Sent when an account data export you requested is ready to download. See Exporting your account data.
The account-deletion confirmation. Sent the moment you confirm account deletion, summarising what's gone and where any retained business records live. See Deleting your 1pm account.
The inactivity warnings. Four of them, at 60, 30, 7 and 1 day out, once an account has been dormant long enough to start the removal process. Each names both dates: the day you lose access, and the day the data would actually go. Signing in at any point stops the whole thing.
The deactivation notice. The fifth email, sent if none of the four reached you and the account has been locked rather than deleted. It says what happened, that nothing has been removed, and how long is left to restore it yourself. See Inactivity and automatic deletion.
The seat-change notice. Sent to the account owner when a colleague accepts an invitation to the account or is removed from it, with the new seat count and what the subscription costs from here. See Managing your subscription.

You can't unsubscribe from these. They are direct responses to things you asked for or to events that affect the account itself. If you don't want them, the lever is to not do the action that triggers them (don't request a password reset, don't change your email, etc.).

Informative emails

We send some emails from news.1pm.app depending on your current status within the app. For example, if you are a trial user we may send you occasional email updates reminding you when your trial is about to end. You might call emails from news.1pm.app nurturing emails to help point you in the right direction. Emails from news.1pm.app are sent automatically in a sequence depending on what status or action you have taken.

You can unsubscribe from these from within any of the emails sent by news.1pm.app.

Billing emails

These come from Stripe directly, not from 1pm, but they're sent on 1pm's behalf and you signed up to receive them when you added a payment method.

Receipts for each successful charge. Sent the moment Stripe successfully bills your card.
Failed payment notices. Sent each time Stripe attempts to charge your card and the attempt fails (expired card, declined, bank block). Stripe retries automatically over a few days. See Managing your subscription.
Trial-ending heads-up. Sent a couple of days before your trial ends, so you have time to add a card if you want continuous access.
Subscription-state notifications. Sent on cancellation, on resumption, and on plan changes (monthly to annual or vice versa).

You can update the billing email address Stripe uses for these inside the Stripe customer portal. If you want them to go to your bookkeeper rather than you, set the billing email there.

Crew-side emails

These are the emails your crew receive after you've shared their run-of-show link. You can think of them as "things 1pm sends on your behalf when you ask it to."

The share-link invitation. Sent when you click Email link in the Share panel for that crew member. Contains a single, tokenised URL to their run-of-show view, with a short note from you (or a default note) and your branding (logo + accent colour) if you've set one. See Sharing the live link.
The request email. Sent when you ask a crew member to upload a document or answer a question (e.g. via the Asking crew for documents and info flow). Contains a deep link straight to the request form on their crew page.
The event-request email. The same shape as a crew request, but sent to every crew member assigned to the event in question, asking them all for the same thing. See Asking everyone for the same thing.
The RSVP invitation. Sent when RSVP mode is enabled on an event. The body asks them to confirm whether they're attending, what dietary needs apply, and any extra fields you've added. See Collecting RSVPs from your crew.

Each of these is triggered by an action you take in the planner. The five-minute resend cooldown on the share-link button prevents accidental duplicate sends.

Everything above happens because you pressed something. Automations are the other half, and the difference matters: their whole purpose is mail that goes out without you pressing anything, on a schedule you set once.

Two more categories reach crew that way:

The system emails and your own automation rules. Chasers for outstanding requests, a warning before a dated certificate lapses and another after it has, a nudge on a rejected upload nobody has replaced, a prompt to re-send a document that carries no expiry date at all, and whatever rules you have built yourself. Two reminders ship switched on: the outstanding requests reminder (7 days after the invite, and again at 14, until they finish) and a last reminder 7 days before the event to anyone still not done. The document reminders ship switched off, so nothing starts chasing your crew about their paperwork until you decide it should. See Automations.
The status-update email. Sent from the event when you move a crew member's status and choose to tell them, carrying your wording for that status, copying you in so both sides hold the same record, and carrying their own link where the event has that option switched on. See Crew statuses.

Three further automations report to you rather than to crew, and are worth knowing about because they arrive unprompted: an alert when an invite is never opened (switched on from the start), and, once you enable them, one when an upload has been sitting unreviewed, and one the moment the last person on an event finishes everything required.

Separately from all of that, the weekly summary is an optional Monday-by-default digest of what is still outstanding across your events. It is off until you switch it on, and you choose the day, the hour and the address it goes to. See The weekly summary email.

How to stop a particular email

The honest answer for most emails is: stop the action that triggers them.

For share-link invitations: copy the link from the Share panel and send it via your own channel (text, WhatsApp, etc.) rather than clicking Email link. The crew member gets the link the same way; 1pm doesn't send anything.

For request and event-request emails: build the request, but skip the automatic send by sharing the link to the request manually. The crew can still respond; you just got there a different way.

For RSVP invitations: the same. You can copy the RSVP URL from the event and send it however you like. The RSVP page works without the invitation email having been sent.

For billing emails: change the billing email in the Stripe portal to a different address (e.g. your accountant's), or, if you genuinely want them off, accept that you'll lose visibility into failed payments and missed charges. The trade-off is rarely worth it.

For account emails: you can't stop these and you wouldn't want to. If your inbox is being flooded with verification codes, it's usually because someone is bashing the Forgot password form. Email [email protected] and we can look at the pattern from our side.

What if I'm getting too many emails

This is almost always a share-link cascade e.g. you sent every crew member their link in one sitting, and each of those went to a real address that also forwarded to you for some reason. Common culprits: a shared inbox that aliases to multiple recipients, an email forwarding rule that copies you on outgoing mail, a CRM that's been wired in to BCC everything sent from the account.

Look at the From and To headers on a couple of the recent messages. The To will tell you which crew the message was actually addressed to, and from there you can trace why your inbox is getting copies.

What if I'm not getting emails I should be getting

Same checklist as missing crew-link emails: check spam, junk, Promotions/Updates, your company email gateway. Verification emails and password resets are especially likely to be quarantined by corporate mail filters because they look like account-takeover bait.

If you've been through that checklist and an email genuinely isn't reaching you, email [email protected] from a different address. A real person reads that inbox and can check the send log on our side.

Send limits

1pm meters outgoing email two ways.

The headline limit is a monthly allowance: 200 emails a month on a free trial, 1,000 a month on a paid plan. It covers everything 1pm sends on your behalf, the share-link invitations, the request and RSVP emails, and so on. See Your monthly email allowance for how it's counted and what happens when you reach it.

On top of that there's a daily surge guard of 200 outgoing emails per account per day, which resets at midnight UTC. This one only bites if you fire a very large batch in a single sitting (a 200-plus crew event, every link sent at once). Hitting either limit is rare; if you do, copy-link is the workaround.