Quick intro: we're the team behind SuprSend, a notification infrastructure platform. Today we're launching SuprSend Agent, and we wanted to share what we built, how it's wired, and the guardrails we put around it.
The 30-second version
SuprSend Agent is an AI agent that lives inside the SuprSend dashboard. You describe what you need in plain English, and it builds, configures and debugs your notification setup for you.
It's connected to:
- the full SuprSend API surface
- the product documentation
- agent skills
- domain knowledge about how notifications actually work
So it doesn't just fire off API calls. It understands your use case, picks the right tools, applies the correct configuration, and tests the result.
Try it: SuprSend Agent | Docs: read the docs
Why we built it
Notifications are deceptively deep. One message passes through several layers of logic: who gets it, on which channel, at what time, with what content, and what happens if the user does (or doesn't) act. Every layer has to be configured, tested and iterated.
That depth is what lets a platform handle real-world use cases. It's also why it takes days to build a mental model before you configure anything.
The agent shifts where that effort goes:
- New users skip the upfront learning curve. Ask the agent how things work, and let it set up your first workflows.
- Existing users skip the click-through. No more hopping between screens to change a vendor, check an object or tweak a template.
What you can do with it
1. Ask anything (without opening another tab)
Data modeling, how a feature works, what an error means, best practices, how to approach an integration. It answers from the docs.
"How do preferences cascade from defaults to tenants to end users?"
2. Manage your assets from a chat
The agent can create, retrieve, update and commit across tenants, objects, preferences, vendors, translations and schemas.
"Update the SMS vendor for tenant cypher and show me the current preference categories."
3. Design and test a notification from one prompt
This is the one we're most excited about. Normally you decide everything yourself: flow structure, timing, branching, channels, and how the content should read on each one.
Now a prompt like this is enough:
"Set up a trial expiry reminder for new users."
The agent will:
- Map out the workflow nodes
- Set the time delays
- Add the branching logic
- Pick the right channels
- Design and personalize the templates with variables
- Test the result across every channel
You describe the outcome. It handles the build.
4. Ask your analytics anything
A fixed dashboard only answers the questions it was built for. The agent reads your notification data through a semantic layer over the data lake, so you can ask things like:
- Which notifications performed worst in the last 30 days?
- What's the best performing template this week?
- How do channels compare across segments and tenants?
- How many workflows are active?
"Show me delivery and open rates for the weekly-digest workflow, split by tenant, for the last 30 days."
It returns the answer, can visualize it as a chart, and can post it straight to Slack.
5. Debug "why didn't they get it?"
We all know this one. A notification doesn't arrive, and the cause could be a channel issue, a preference opt-out, a tenant override or a vendor failure. Finding it means digging through logs and screens.
"User john@cypher.com says he's not getting emails. What's wrong?"
The agent traces the delivery, finds what stopped it, explains the cause and suggests a fix.
"Cool, but is it safe on a live workspace?"
Fair question, and honestly the one we spent the most time on. The agent acts on real organizational data, so safety is built into every step:
| Guardrail | What it means |
|---|---|
| Workspace-scoped access | Every session is limited to one workspace. A conversation in one can't read or change data in another. |
| Service token auth | Each session uses a workspace-scoped JWT that expires and auto-refreshes, so access is short-lived by default. |
| Permission before changes | The agent asks for confirmation before any edit. Updates read the resource's current state first, so nothing is silently overwritten. |
| No destructive deletes | Deletes aren't exposed to the agent at all. Only low-risk, reversible operations (like removing a user from a list) are allowed. |
| Validated, not guessed | It runs on validated SuprSend schemas and product knowledge, so it uses correct parameters instead of guessing. |
Who is it for?
Developers, product managers, marketing, customer success and ops teams. Basically anyone who manages notifications but doesn't want to write integration code for every change. Work that used to wait on engineering can now happen in a conversation.
A bigger shift
This launch is part of a larger direction: SuprSend is becoming AI-first notification infrastructure, where you operate the platform by describing what you need instead of learning every knob and switch.
Try it and tell us what you think
Start with a first prompt in the dashboard: Try SuprSend Agent
We'd love to hear from you in the comments:
- What's the first thing you'd ask the agent to build?
- What guardrails would you want on an AI agent that touches production config?
- What's the most painful notification bug you've ever had to debug?
We read every reply. 👇
Top comments (0)