SuprSend
Day 33 after signup
Oct'26 🎃 | Product Updates
What we built in the dead of the night: MCP updates, CLI releases, sub-tenants and broadcast precompute.
Why it works
- Start with a concise highlights list so readers can scan the main changes before diving into detail.
- Pair technical updates with practical examples that show when each capability is useful.
- Give each feature its own section and a focused next step, making a broad update roundup easier to navigate.
How it is built
- Seasonal opening
- Update highlights
- MCP use cases
- CLI and CI/CD updates
Email copy
Hey [First name], This Halloween season, SuprSend MCP learned a few new tricks. It can now take on almost any notification job you give it. We also shipped a few more features along the way. TL;DR SuprSend MCP: Early adopters already running their notification work from their AI tools CI/CD with the SuprSend CLI: release notification changes from your pipeline Broadcast precompute: large scheduled broadcasts that start sending on the dot Sub-tenants: model your customer’s org once, and every team below follows it MCP UPDATES Teams are running their notifications through AI A few weeks after launch, SuprSend MCP is out of BETA. 20+ teams have the MCP running in their AI tools, and the most active user has made 3,000+ tool calls. Here’s what they’re using it for: Designing templates and workflows: A proptech company created a full team-invite flow from scratch, tested it in staging, and shipped it to production without opening the dashboard. Building lists and segments: A data team previewed audience segments and matched their dynamic list members against their data warehouse before sending. Triggering broadcasts: A creator platform dry-ran a product launch, then sent it to four lists in waves, checking delivery after each one. Debugging delivery failures: When a daily digest stopped after a release, an identity verification company read the step logs of failed runs to find the cause. Cancelling workflow runs: When an event was called off, a learning platform stopped about 150 pending reminders before any went out. Tracking delivery and engagement: An operations software company pulled monthly sends, deliveries, opens, and clicks for 13 digest notifications in one conversation. Build, debug, and manage your notifications from the AI tool you already use, without switching to the dashboard. Connect your AI tool in 2 minutes → COMING SOON Interactive UI to preview workflows and templates right in the chat, plus safe previews of sent messages. NOTIFICATIONS AS CODE Release notification changes automatically with GitHub Actions Ship workflows, templates and other notification assets from a CI/CD pipeline with the SuprSend CLI, using GitHub Actions. Review every change in a pull request and test in staging before it reaches production. See the GitHub Actions setup → CLI UPDATE CLI v1.1.0. category pull and push now carry the Is commercial setting, so your one-click unsubscribe setup can live in Git too. BROADCASTS Time-sensitive broadcasts now reach users on time On a large list, a broadcast can spend 5 to 30 minutes fetching profiles, checking preferences, and rendering every message before the first message goes out. That’s too late for time-sensitive notifications like a market open or a flash sale. Precompute does this prep up to 2 hours ahead and stores each rendered message, so a large broadcast deve at its scheduled minute. Learn more → SUB-TENANTS Set up tenant hierarchies with built-in inheritance Sub-tenants let you set up a hierarchy of tenants, where settings at the top flow down to every level below. For example, in a project management app, one customer workspace can have dozens of teams, each running its own projects. Without a hierarchy, you’d set preferences for every team one by one, and any change at the top means updating all of them again. If the workspace admin turns off email for issue updates, every team and project below inherits the setting. If one team wants cycle reminders on Slack, it changes only that setting, and the rest still comes from the workspace. If SMS is blocked at the workspace, it stays blocked for every team and project below. Branding and custom properties work the same way, so every team’s templates pick them up automatically. Learn more → Until next month, Team SuprSend Docs · Changelog · Slack community You're getting this because you build on SuprSend. · Unsubscribe