How Notification Engagement Helped Evocalize Boost Repeat Purchases by 27%

Small teams have to be ruthless about where they spend engineering resources. Nick Markman, VP of Product at Evocalize, knew this early on.

Instead of pouring time into building a notification system from scratch, his team built with SuprSend—and increased repeat purchases by 27%.

SuprSend is a centralized notification infrastructure that’s built for multi-channel delivery, user preferences, and multi-tenant systems. It’s powerful and flexible, so teams can ship both product-critical and engagement notifications fast.

Here’s how Evocalize replaced a limiting setup and turned notifications into a product growth driver.

What does Evocalize do?

Evocalize is a collaborative marketing platform for real estate and mortgage professionals. Their users—think local real estate agents and loan officers—want leads, but don’t have the time or know-how to master digital marketing.

Since most of Evocalize’s go-to-market is B2B2C, they’re often one step removed from the end-user. That makes notifications critical, especially for:

• Reaching users directly (in-app and email)
• Communicating updates independent of partner platforms
• Re-engaging users who aren’t logging in often

Why switch to SuprSend?

Previously, Evocalize had built on Magicbell and it had several limitations: 

• Heavy engineering dependency: Any new email or logic change meant dev tickets and handoffs. Even minor tweaks required HTML work and engineering lift.
• Multi-tenancy workarounds: Each partner needed their own branding, but the system wasn’t built for it. The team had to hack around SES with custom templates.
• Lack of observability: No easy way to track delivery, failures, or logs. The team had to build visibility layers themselves.

A well-timed email turned into a game-changer. Evocalize wasn’t actively looking but once they saw SuprSend in action, it checked all the boxes: 

• Built-in support for multi-tenancy
• Self-serve workflows
• Template management
• Clean documentation and APIs
• Isolated environments for staging and production workflows
• Usage-based pricing (no upfront barrier)

“ SuprSend was simple to integrate, powerful out of the box, and priced in a way that didn’t create friction.”
Nick Markman, VP of Product at Evocalize

Fast, Frictionless Integration in One Sprint 

Evocalize migrated their core notifications in a single sprint—with just one backend engineer handling most of the work. The team:

• Set up tenants and synced users
• Defined events and templates
• Embedded SuprSend’s inbox with native-looking UI 
• Validated in staging, then went live on production

Implementation wasn’t just fast—it was frictionless.

“As far as new platform integrations go, this was as straightforward as it gets. We didn’t need a weekly check-in or project plan. Our engineers read the docs, we had maybe one kickoff call, and then we were off and running. SuprSend allowed us to be autonomous.”
Nick Markman, VP of Product at Evocalize

And support didn’t drop off after go-live.

“Credit to the SuprSend team—they’ve been super responsive. Any time we had a question, we got same-day answers. That level of support didn’t stop after onboarding either, which is rare. Usually, the attention fades after implementation. Not the case here.”
Nick Markman, VP of Product at Evocalize

Building Workflows Without Engineering Dependency

One of the team’s big wins? Being able to create logic-heavy, multi-channel workflows, without looping in engineers every time.

Nick took us through an example. He has set up a workflow that nudges users to set up lead alerts that notify them when a new lead comes in and even configure auto-respond on their behalf.

When a user logs in for the first time, a workflow gets triggered. Evocalize sends: (event, recipient, token). That token hits their internal notification API, which fetches contextual data like user settings or program details on-demand.

The flow checks:

• Is lead alerting enabled for this tenant?
• If yes, wait 3 days
• Then send:
  
  • An in-app nudge
  • An email (if enabled)

“It’s a simple message—but complex logic. And I was able to build the whole thing myself.”
Nick Markman, VP of Product at Evocalize

Easy Debugging with Logs 

The process of building and validating new notifications has become significantly more efficient with SuprSend. The only engineering requirement now is to implement the new event, or add a few properties to the API. Once that’s done, Nick and his team can take it from there in staging. This allows them to:

• Fire events in staging
• View payloads directly in SuperSend's logs
• Copy the token and run internal API calls in Postman to see exactly what data is returned
• Configure workflows using real data

Additionally, SuprSend’s analytics inside the workflow has proved useful. 

“When we first launched in production, we ran into a small issue—just some missing data in a notification. I got an email from SuprSend summarizing the error with a direct link to debug it. I hadn’t set that up, didn’t even know it was a feature—but it just worked. I clicked through, found the issue, and fixed it right away. That kind of out-of-the-box visibility was a really nice surprise.”
Nick Markman, VP of Product at Evocalize

Embedded & Branded In-App Inbox

Evocalize uses SuprSend’s out-of-the-box Inbox UI with light customization to match the app’s look and feel. The inbox surfaces notifications like program updates or alerts, right where users already manage their day-to-day. It feels native—and reduces the need for email overload.

Multi-Tenant Aware Preference Center

As a B2B2C platform, Evocalize supports multiple partner brands—each with their own end-users, branding, and notification needs. That made multi-tenancy a must-have, especially for managing preferences. 

“We’d mostly been sending transactional messages at first, but once we added more marketing-oriented notifications, we needed preferences. We created all of those in SuprSend, and then pulled them into our front end with your APIs.”
Nick Markman, VP of Product at Evocalize

They were able to:

• Display category/subcategory/channel-level options
• Hide irrelevant categories to reduce UI noise
• Match the look and feel of their app while keeping full control over user preference logic

Thanks to multi-tenancy-aware theming, the hosted preferences page reflects the correct logo and branding for each customer account.

Measurable Impact Realized on Business Metrics

Before SuprSend, even a simple email often required the involvement of design, product spec, backend engineering, template integration, and more. Now? Engineers send the trigger. Product owns the rest.

And it’s not just faster—it performs better. The results spoke for themselves. Nick compared purchasing users who clicked through SuprSend-powered notifications vs. purchasers who didn’t:

And this was just two months in. Evocalize expects these differences to compound as notification strategy matures.

What’s Next for Evocalize

Now that the core notification setup is stable, the Evocalize team is shifting gears—from replicating existing logic to unlocking what wasn’t possible before. The roadmap includes:

• Running experiments: adding segmentation, A/B tests, and dynamic paths to improve engagement
• Expanding access: bringing support and ops teams into SuprSend or integrating it into internal dashboards
• Exploring new channels: SMS is on the radar—especially given how text-heavy their end users are
• Leveraging smart delivery: optimizing send times and channel selection based on user behavior and availability

“We’re past the parity phase. Now it’s: what can we do that we couldn’t before? SuprSend is super self-serve, but there’s a ton of power under the hood. And the team’s been great about helping us unlock that.”
Nick Markman, VP of Product at Evocalize