Spark Mail

Spark is ready for iOS 27. Siri now knows what's open in Spark and can act on it — the exact message you're reading, the thread you're in. "Archive this one" knows which one. 📅 Calendar for Siri & Shortcuts — create, move, or cancel Spark calendar events by voice or automation, without opening the app. 📱 Free window resizing — Spark adapts to whatever size or shape you resize it to. Feels right wherever you're working. Read more: https://bit.ly/sparkios27

Tomorrow, Wednesday at 15.00 CET — Sergey and Artiom are doing a live demo: how to connect your AI agents like Claude, OpenAI's Codex, Cursor directly into Spark. If you're building with AI and want to see where email fits in, it's worth 45 minutes of your time. Register link in the comments ↓

Notion Mail's promise was a personalized email experience — one that actually learned how you work. And now, when you need to switch, Spark can pick up where you left off. AI picks up the busywork in the background, so when you open your inbox, what's left are the decisions only you can make. Still 20% off if you're moving from Notion Mail — through November 1. Codes in the comments 👇

Trust isn't given all at once. It's given in degrees — and the degree matters more than the trust itself. That's the thinking behind Spark CLI's agent permissions 📊 Delegation only works when you set its terms, so Send sits at the top of a four-level ladder, chosen per account, per shared inbox: Off — the agent can't see or touch anything. Read — it can look, to answer your questions. Triage — it can draft and sort, but nothing moves until you say so. Send — it can act on your behalf, fully. None of this lives in the agent's judgment. It lives in Spark itself. Delegate as much or as little as you want. The line stays where you put it.

The best way to understand what Spark CLI does isn't a feature list — it's the prompts people reach for without thinking. Four our team runs constantly.

📥 The usual advice for an overflowing inbox is to find a better system. Artiom's inbox got easier a different way — by keeping the one he already had, and handing the upkeep to an agent. Artiom is a Senior Customer Success Specialist at Spark. His mailbox is the personal layer — key accounts, escalated threads, relationships he handles one-on-one because that's what they need. A personal inbox fills up like any other, though. Dozens of threads a day, and before he could answer any of them, he had to sort the whole thing — what's new, what's urgent, what could wait. He already had a system for that. Folders built over years: Need Reply, Escalated to QA, Demo Request. The folders worked. Keeping them updated by hand, every morning, before he could actually help anyone — that was the cost. So he described that same system to an agent, connected through Spark CLI, instead of switching to a different one. "I didn't adopt someone else's system. I described the one I already had, and now it maintains itself." Now the agent runs that sorting pass twice a day, filing threads into those same folders and surfacing what needs a reply today. He opens his inbox already knowing where to start. "It hasn't replaced me. It's removed the forty minutes of sorting before I could start helping people." The full article: https://lnkd.in/dRhFDURy

Spark has always been built to keep your inbox private and secure. Now, that comes with an outside seal: Readdle, the company behind Spark, is ISO/IEC 27001-certified 🔐 If you haven't heard of it, ISO/IEC 27001 is the international standard for managing information security. It's not just servers and encryption — it covers the people, decisions, and everyday processes. For Spark, an accredited external auditor checked things like how information security is organized and maintained, how the team detects and handles security risks, and how staff is trained. Nothing changes about how you use Spark. What's different is that the practices behind it now have independent confirmation.

You leave a meeting. An hour later, could you say exactly what was agreed? 👀 Ask Spark's AI Assistant to pull it from your meeting notes — no re-reading the thread, no re-watching the recording. Artiom walks through it. If you're already running an AI agent day to day, Spark CLI puts your inbox and meeting notes in reach of that agent, too.

Most people already trust their AI agent with the easy stuff — summarize this, draft that, tidy a folder. The inbox is usually where it stops. Spark CLI connects any MCP agent — Claude, Codex, Cursor, and others — to every account you've added to Spark, plus your contacts, meeting notes, and calendar. What you do with that is up to you: ask a single question your search bar can't answer, let it pick up how you write from your sent mail — or add more context yourself — so drafts are waiting when you're back, or set up a routine that checks your inbox on its own. Five ways to put Spark CLI to work, from one question to a full routine — https://lnkd.in/dHbD8eee

You've got 12 open threads with potential partners, 4 intros you still owe, and a follow-up you've been meaning to send since Tuesday — and none of that means you're behind. It means you're the person other people are waiting on, which is a different problem than the one most email apps are built to solve. Spark's built for people keeping a dozen things moving at once, not for getting to zero 💌