How Current sends email — and why two mail paths, not one

Current sends two very different kinds of email, and it deliberately sends them from two different places. Understanding the split helps you answer the question every admin eventually asks: "why did this email come from a generic address instead of our own domain?"

Sign-in codes, invitations, project digests, and in-app alert emails are transactional — they're triggered by something that just happened in the system, and they need to land in the inbox within seconds. Current sends these through Resend, a dedicated transactional email provider, from a single sending address: notifications@current.day.

• ＋Sign-in codes — the 6-digit two-factor code sent when a password sign-in needs a second check.
• ＋Invitations — the "you're invited to [workspace] on Current" email with an accept link, sent when an admin invites a teammate.
• ＋Project digests — a nightly summary of projects that need attention, sent to project owners.
• ＋Notification alerts — mentions, comments, new assignments, at-risk flags, weekly summaries, and CRM alerts, based on each person's notification preferences.

Because this is one sending domain used only for transactional mail, Current's operator handles the SPF and DKIM authentication records and keeps the domain's sender reputation clean. You never have to configure anything for this mail to arrive — it just works, the same way password-reset email from any SaaS product works.

Sequence and campaign email is different. When an account executive enrolls a contact in an AI sequence, the email doesn't come from Current's sending domain at all — it's sent through Microsoft Graph using that AE's own, already-connected Microsoft 365 mailbox. The message shows up in the recipient's inbox as if the AE typed it themselves, and a copy lands in the AE's own Sent Items.

See "AI sequences and campaigns" for how sequences are built and approved. This article is about the sending mechanics specifically.

Transactional mail (sign-in codes, invites, digests) and outreach mail (sequences, campaigns) have opposite reputational needs. Transactional mail is expected, opted-into, and rarely marked as spam — perfect for a shared platform domain with strong authentication. Outreach mail is higher-volume and higher-risk: if it went out from the same shared domain, one bad campaign could hurt deliverability for every tenant on Current, and — just as importantly — it would land in the recipient's inbox from a stranger's domain instead of your own team's real Microsoft 365 address, which reads as far less trustworthy.

Sending sequence email from each AE's own mailbox keeps your domain's reputation entirely in your own hands, keeps replies flowing straight into that AE's normal inbox, and keeps a hard daily send cap — 250 sequence emails per mailbox per day — so no single account can accidentally trigger a spam filter. Enroll more than that in one go and Current simply paces the rest over the following business days; nothing is dropped.

Every address that campaign and sequence email skips lives on one suppression list, and the Email (Resend) tile in Integrations opens a full Master unsubscribe manager for it. Search the list, add an address by hand, or bring a batch in from a file — every send re-checks this list at the moment it goes out, so a suppressed address is never emailed again.

• ＋Search — the whole list is searchable, so you can confirm in seconds whether a specific address is already suppressed.
• ＋Add by hand — type an address and it's blocked from every campaign and sequence immediately.
• ＋CSV upload — pick a .csv file (up to 5 MB); Current auto-detects the email column, previews how many addresses are valid, invalid, or duplicated within the file, and writes nothing until you confirm the import.

Sending is only half the loop. Delivered, opened, clicked, bounced, and complained events flow back into Current through a webhook you register in Resend — and it must live in the same Resend account as the API key that sends your mail. Without it, every campaign report shows zero deliveries and opens even when mail is landing fine, and bounced or complaining addresses are never added to your suppression list automatically.

• ＋Open Integrations → Email (Resend) → Manage. The Webhook endpoint URL box shows your workspace's unique URL — click it to copy.
• ＋In your Resend dashboard (the account whose API key is saved above): Webhooks → Add endpoint → paste the URL, and select the sent, delivered, opened, clicked, bounced, and complained events.
• ＋Copy the new endpoint's signing secret and paste it into the Webhook signing secret box in Current. Every event is signature-verified — an event that doesn't match your secret is rejected.
• ＋If you ever switch to a different Resend account (a new API key), re-create the webhook there and paste the new signing secret — webhooks don't move with the key.