SuprSend

Introducing preference conditions and digest schedules, your users decide what makes a notification worth sending to them, and how often they want it. What this gets you: • Turn an overwhelming category into a summary: Let your customers pick Daily or Weekly in their preference center and get one digest instead of a notification at a time. • Alert only when it matters: Customers can set their own threshold, like an error rate or a spend limit, and hears from you only when the number crosses it. The condition resolves automatically at send time. • Let an admin set notifications categories based on user roles, so finance gets billing alerts and managers get usage limit and invoice alerts. Your users get the flexibility and control over their notifications.

We're #hiring a new Go Developer in Bengaluru, Karnataka. Apply today or share this post with your network.

We're #hiring a new Founder's Office - GTM in Bengaluru, Karnataka. Apply today or share this post with your network.

We're #hiring a new Sales Development Representative - Core Team in Bengaluru, Karnataka. Apply today or share this post with your network.

Today we're introducing Segment Lists in SuprSend. Now you can build a list by filtering on user properties and the events your users have performed. This solves the use cases most marketing teams run into: ⏵ Usage-based upsells: users past 80% of their plan limit, prompted before they hit the ceiling ⏵ Win-back: accounts quiet for 30 days get a re-engagement email ⏵ Targeted announcements: enterprise customers in a specific region What we did differently is that rather than defining a segment in a form builder, you write SQL on top of your user and event data. There's no limit to the kind of filters you can create. Postgres and ClickHouse functions are both supported, so joins, aggregates, time windows, and JSON access all work the way you'd expect. Worried you don't know SQL? Our Agent got you covered. Define your segment in plain English and it writes the query for you. Sample queries and setup are in the docs: https://lnkd.in/dazcvzsE

We shipped dark mode. 🌚🌝

We're #hiring a new Agent Engineer in Bengaluru, Karnataka. Apply today or share this post with your network.

SuprSend is officially the #1 notification infrastructure on G2 Our users had opinions this season. The good kind: 🎖️ Easiest To Use 🎖️ Most Implementable 🎖️ Easiest Setup 🎖️ Best Meets Requirements 🎖️ Best Support 🎖️ High Performer 🎖️ Highest User Adoption A massive thank you to every customer who took the time to share their feedback. If you're evaluating a notification system for product and customer engagement, stop second-guessing and try us out today. #NotificationInfrastructure #G2

Today we're launching SuprSend Agent Skills. AI agents already know about SuprSend. But knowing about SuprSend and using it correctly are two different things. Skills are an open set of instructions that teach AI agents how to build on SuprSend correctly. If you use Cursor, Claude Code, Codex, GitHub Copilot, or any agent on the Agent Skills open standard, you install them in one command. Without Skills, an agent fills the gaps with invention. It hallucinates CLI flags, writes node_type values that do not exist, and answers from a training snapshot that may be months old. You spend more time fixing the output than the agent saved you. Four skills ship today: → Docs and product knowledge: live, LLM-friendly doc endpoints, so the agent checks current SuprSend docs before acting instead of guessing → Workflow generation: the full workflow node reference, so the agent generates valid workflow JSON against the real schema → CLI and tooling: the complete CLI command reference with per-command tips, so commands run right the first time → Template and channel content: the variant envelope, multi-tenant and multi-lingual variants, and per-channel schemas for all 9 channels Skills load through progressive disclosure, so they do not bloat the context window. And they are not just for coding agents. The same knowledge layer backs the in-product Agent, MCP, the CLI, and the Slack Agent. Read more: https://lnkd.in/gYN2u34s Docs: https://lnkd.in/gg9ggzYj

Today we're launching the SuprSend Agent Plugin. One install gives your coding agent everything it needs to work with SuprSend. It bundles the SuprSend MCP server and our agent skills, so the agent can author workflows, templates, schemas, events, categories, and translations, and follow SuprSend primitives without manual configuration. The plugin format is shared across Claude Code, VS Code Copilot, and GitHub Copilot CLI, so you install it wherever you already work. The skills are the part that matters. They carry SuprSend's domain knowledge, the workflow node schema, the template variant schema across all nine channels, and the full CLI reference. A few things this unlocks: → Integrate SuprSend into your product: Add the SDK, drop in the in-app inbox or preference center, and set up event triggers on product actions, from a prompt in your codebase. → Set up your account and test data: Describe when a notification should fire and the agent builds the workflow, generates templates across channels, and configures a preference hierarchy from category defaults to tenant overrides to user choices. → Query and debug: Ask why user 583 never got a notification, how a workflow performed this week, or how many users opted out of a category. You get an answer, not a pile of raw logs. Setup in 2 simple steps: https://lnkd.in/gjPWNbaZ Read more: https://lnkd.in/gDSYU9fp