Find the right plan for your needs

A notification is defined as a message triggered to a single user or object on any downstream channel (eg. Email, Push, In-app, SMS, Slack, Webhook, etc).

• If a workflow triggers notifications to one user on multiple channels (e.g., Email, SMS, and In-app), each channel counts as a separate notification.

• If a workflow triggers a call to a webhook endpoint, it counts as a separate notification.
‍
• If a workflow triggers notifications to multiple users in bulk request, each user’s notification is counted separately.
‍
• Notifications that are failed by SuprSend due to reasons like user opt-out or inactive channels, etc, they are not counted towards billing.
‍
• If a notification is successfully triggered by SuprSend but is failed by the downstream provider, it will be counted towards billing.
‍
• In case of batching / digest where multiple requests are batched or grouped into one notification (e.g., a digest email), it counts as one notification for billing.

• If a notification is triggered to an object which has it own channel (e.g., object feed), it is treated like a user channel and counts as one notification. Additionally, if the object has subscribers and notifications are sent to them, those are also counted separately.

Yes, we do offer MTU model (unique users who are triggered a notification in any given month) alongside notifications triggered count. Contact us to let us know your billing requirements and we will prepare a custom plan.

Yes, we do not charge based on number of requests you make to SuprSend to trigger your designed notification workflows. However, to ensure smooth system performance, we have a generous fair limit on the number of requests allowed.

If we detect an unusually high volume of requests, which is typically caused by a bug or misconfiguration on your end, we will reach out to address the issue and ensure uninterrupted service.