Skip to main content

Spring Release Spotlight Nova Intelligence Follow-Up: What We’re Hearing From Teams

  • September 8, 2026
  • 0 replies
  • 20 views

Deja
Forum|alt.badge.img+14

Since Nova Intelligence launched with Iterable’s Spring 2026 release, we have been listening to how teams are evaluating Nova Intelligence Agents within their existing campaign workflows.

One pattern stands out: teams are getting further when they introduce agents into familiar, reviewable work rather than beginning with an entirely new or expansive workflow.

Pre-send review and focused performance questions are surfacing most often, while troubleshooting and personalization logic are emerging in more targeted ways. Teams are also considering where human review should remain, how agents fit alongside existing tools and processes, and what would make an initial use case valuable enough to repeat.

Here is a closer look at what we are hearing.

 

Teams Are Starting With Work They Already Understand 👀
 

The clearest pattern is that teams are not beginning with their largest or most complex workflow.

They are starting with campaigns, journeys, and questions they already understand. This gives them an existing process and expected outcome to compare against when reviewing an agent’s response.

The decision is often less about which capability sounds the most advanced and more about where the team can quickly determine:

  • Was the output relevant?
  • Did it help us reach an answer faster?
  • What still requires human judgment?
  • Would we use it for this task again?

Teams are not always deciding what an agent should replace. They are looking for the point in an existing QA, reporting, technical, or AI-assisted process where it can add value.


 

Where Teams Are Exploring Agents
 

The conversations furthest along tend to involve a defined task or question rather than an entire campaign workflow.

We are hearing teams explore agents for:

  • Pre-send review: A first review of a campaign or template already in progress
  • Performance questions: A focused question about recent campaign performance that might otherwise require digging through reports
  • Troubleshooting: A specific error, unexpected campaign behavior, or journey issue the team is already investigating
  • Personalization logic: A first draft of Handlebars or other logic that the team can review and test

Pre-send review and focused performance questions are the most common areas across the conversations we reviewed. Troubleshooting is beginning to emerge, while personalization logic is showing more limited usage.

Across these areas, teams are generally treating an agent’s initial output as a draft, diagnosis, recommendation, or first pass. People still apply brand context, technical knowledge, and judgment before deciding what to use.

 

What This Signals 🔎
 

The common thread is not one particular agent or use case. It is the move from general interest toward a trusted, repeatable place for agents within everyday campaign work.

So far, the conversations suggest teams are exploring that move by:

  • Beginning with work they already understand
  • Keeping human review in the process
  • Focusing on a specific task or question
  • Comparing the experience with their current workflow
  • Deciding whether the result is useful enough to repeat


Where to Learn More

 

What Are You Trying?

Have you used an agent for one of these workflows? Share which area you started with and one thing that made the experience more useful. If you haven't tried one yet, which workflow would you like to understand better?