SuprSend
Day 11 after signup
SuprSend Product Updates
SuprSend MCP is LIVE! We also made platform more deeper for tenancy, added one-click unsubscribe
Why it works
- Lead with a concise summary of the biggest changes so readers can scan the issue before deciding what to explore.
- Give each major update its own section with a practical use case and a relevant next step, then group smaller changes into a compact roundup.
How it is built
- Date and introduction
- Key updates summary
- Major feature explanations
- Minor updates roundup
Email copy
SEPTEMBER 2026 New in SuprSend Hey [First name], here's what we shipped recently! TL;DR SuprSend MCP: work with SuprSend from your AI tool Inbox connection status: users see when the inbox can’t connect Sub-tenants: set preferences and branding once, every team below follows Per-tenant user profiles: one user, a different profile per tenant One-click unsubscribe: an Unsubscribe button in Gmail and Yahoo Workflow cancellation node: stop notification workflows from the builder SUPRSEND MCP Run SuprSend from Claude, Cursor or ChatGPT Ask your AI tool to set up SuprSend in your app, build a workflow, or find out why a user missed an email, and it does the work right from the chat. No SQL, no API calls and no jumping between dashboards. Agent skills are built-in, so the agent already knows SuprSend schema and how workflows, templates and data fit together before it changes anything. https://mcp.suprsend.com Learn how to setup → LIVE CONNECTION STATUS Your users see when the inbox can't connect Your in-app inbox now shows users when it can't reach SuprSend, with a status dot on the bell and a banner that says what's wrong: they're offline, there's a connection issue, or there's an authentication issue. It's on by default in @suprsend/react v1.3.0. See how connection status works → SUB-TENANTS Set up tenant hierarchies with built-in inheritance Your customers aren't flat, and now their setup in SuprSend doesn't have to be. You can mirror their org chart with a company at the top and teams and projects beneath it, up to five levels deep. Notification preferences, branding (logo, colours, social links), tenant properties and vendors set on the company apply to every sub-tenant under it. A team only changes what's different for it, and everything else comes from its parent. Blocks are final. If you turn off a channel or a category for the company, no team below can turn it back on. See how sub-tenants work → PER-TENANT USER PROFILES Keep user details separate for each app When one user is on two of your apps, a single profile meant one set of details for both. Alerts could reach the wrong app, and an update from one app could overwrite what the other relied on. Per-app profiles fix that. Each user can keep a separate push token, email, phone number, Slack connection, preferred language or any custom property for every app. See how per-tenant profiles work → ONE-CLICK UNSUBSCRIBE Let people unsubscribe without leaving the inbox Promotional emails from SuprSend now carry the one-click Unsubscribe header, so Gmail and Yahoo show an Unsubscribe button next to your sender name. This opts the user out of just that category, with no landing page, while receipts, OTPs and alerts keep arriving, and it keeps your bulk sends in line sender rules. WORKFLOW CANCELLATION NODE Stop reminders the moment they’re no longer needed A running workflow can become pointless the moment the user takes the action it was made for: they pay invoice, finish onboarding, or cancel the order. Add a Cancel Workflow node to the workflow that handles that action, and it stops the related workflow runs for that user right away, with no API call. Minor but mighty updates Per-service workspace keys: each backend service can have its own key and secret, which means rotating one no longer disrupts the others. Single-tenant Teams bots: Teams bots created after Azure's July 2025 change now connect, with new App Type and Tenant ID fields in setup. $tenant replaces $brand: templates and workflows now share one variable for tenant data, and anything still using $brand renders as before. Mailgun for broadcasts: already sending through Mailgun? Your broadcasts can use it too. Web push in broadcasts: one campaign can now reach people in their browser as well as by email, SMS and mobile push. User Schema page: every user property you track sits in one place with its type and an editable description, which helps teammates and the SuprSend Ag