Inbox Expo takeaway: Interactive email didn't fail. The economics did

Some time after Inbox Expo 2026, I’m still thinking about the Interactive Email Panel discussion. For years, the email industry has treated interactive email as a technology problem. Our thoughts revolved around standards, client support, rendering engines, and email clients. Yet, after watching interactive email evolve over the last decade, I think we can look at it from a different angle.

Key takeaways

1. Interactive email stalled because the cost of building and maintaining it outweighed the benefits for most teams.
2. AI is finally rewriting that math by making interactive email faster to build, test, and maintain.
3. Every email now has two readers: the human recipient and the AI systems that determine whether the message deserves attention.
4. The interactive experiences that scale best are usually the simplest: polls, ratings, preference updates, RSVPs, and other friction-reducing actions.
5. Fragmentation is a permanent characteristic of email. Build for everyone first, then enhance for clients that support advanced functionality.
6. The future of interactive email depends less on new standards and more on making interactive experiences easier, cheaper, and more reliable to produce at scale.

Interactive email never had a technology problem

Here’s an observation that may be unpopular: AMP and interactive email worked. Years ago, the industry proved that it was possible to collect data, submit forms, show dynamic content, update information in real time, and even support complex shopping experiences directly inside the inbox. It wasn’t theoretical.

At the same time, interactive email was never synonymous with AMP. Features such as accordions, carousels, polls, countdown timers, forms, and other interactive experiences can be implemented using different technologies. 

But teams discovered that building an interactive email and maintaining one are two completely different things. Interactive email came with several challenges:

• Apple Mail never supported AMP;
• Outlook never supported AMP;
• Gmail required registration and verification;
• every AMP email required an HTML fallback;
• production teams had to maintain multiple versions of the same experience;
• testing and QA became significantly more complex.

As a result, the question was no longer whether interactive emails could be built, but whether they could be produced efficiently and consistently: “Can we justify building this every week?" 

The answer ultimately depended on three factors: reach, economics, and trust. Apple Mail and Outlook never supported AMP, limiting reach. Maintaining multiple versions of the same experience increased production costs. And Google’s registration and verification requirements made AMP feel more like a privileged feature than an industry standard.

That's why interactive email remained popular among innovators and motivated teams with clear business cases. For many organizations, interactivity became a campaign tactic; something you showcased occasionally rather than built into an everyday production process.

The industry spent years in a deadlock

As a result, interactive email spent years sitting somewhere in the middle: impressive enough to generate conference presentations, but difficult for mainstream adoption. Yes, many of those limitations are still here today, but 2026 feels different.

What changed? The production cost collapsed

For a long time, interactive email required development skills, extensive testing, and significant QA effort. Even when teams saw the value, the production overhead outweighed the benefits. 

I saw another interesting example during the panel discussion. Brice Douglas from Zaymo described an approach that I think reflects where the industry is heading: instead of asking marketers to rebuild their workflow, they take an email created in Klaviyo, add interactivity, and hand it back. No platform switch, no complete rebuild. It sounds simple, but that's exactly the kind of production thinking that interactive email has often lacked. The easier we make interactivity fit into existing workflows, the easier it becomes to justify at scale. 

I’m not talking about AI generating a block of code and calling it a day because that’s rarely enough. The last 10% of email production is often where all the complexity lives: client-specific rendering issues, Outlook workarounds, size limitations, and countless edge cases.

What excites me isn’t AI generating code. Email has too many edge cases for that alone to be transformative.

The real breakthrough is AI-assisted production workflows that help close the loop between creation, testing, and QA:

• generating client-safe code;
• adapting experiences for different environments;
• identifying rendering issues before testing;
• accelerating QA processes;
• reducing repetitive development work.

In other words, AI is becoming useful because it helps generate code, identify rendering issues, test emails, and resolve problems before a campaign reaches production. That’s the shift that changes the economics.

The inbox is becoming an AI surface

I’d like to mention another transformation happening today: the inbox itself. Apple Intelligence summarizes messages before recipients open them. Gmail and Yahoo continue investing in AI-powered organization, prioritization, and categorization. The inbox experience is being shaped by algorithms before the recipient ever interacts with a message.

Marketers should keep in mind that every email now has two readers:

1. The human recipient.
2. The AI system estimating whether that recipient should pay attention.

For years, email teams have been optimized for human attention. Subject lines, previews, design, and content all served the same goal. Well, now we need to think about trust and relevance differently.

The inbox is shifting from a collection of messages to an AI-mediated environment. Algorithms decide what deserves attention before humans ever make that decision. That’s a much bigger change than whether an accordion expands or a form submits inside an email.

What interactive email actually looks like in production

One of the most interesting questions I received from the audience was about what truly works at scale. The interactive experiences that consistently survive production reduce friction without introducing new risks.

Here are some examples:

• polls and surveys;
• NPS collection;
• preference updates;
• RSVP confirmations;
• onboarding checklists;
• accordions and tabs;
• image galleries and carousels;
• countdown timers;
• simple data collection forms.

Interestingly, the most impressive demos are often the hardest to scale. In-email checkouts, fully dynamic content, and highly personalized real-time experiences can be powerful, but they also introduce significant engineering, testing, and maintenance requirements. The interactive experiences that survive long term are usually much simpler.

What do these examples have in common? The email still succeeds even if the interactive layer fails. The moment an email becomes unusable without the interactive component, you've created a single point of failure in an environment you don't control. The most successful teams build a solid HTML experience first and then layer interactivity on top through progressive enhancement.

Fragmentation isn't going away

Another topic we discussed during the panel was fragmentation. People often ask whether the industry will converge around a single standard. I don’t think that’s the future. Apple, Google, and Microsoft have spent years moving in different directions, and I don’t see strong signals that this will change.

The practical future is a production model built around:

• a reliable HTML foundation;
• progressive enhancement where supported;
• automated adaptation across clients;
• a single workflow that produces multiple experiences.

Email’s greatest strength has always been reach. The fact that it renders differently across environments is the price we pay for that universality. However, I view it as a permanent characteristic of the channel, not a flaw.

Wrapping up

For the first time in years, I see several trends moving in the same direction:

• more examples and reusable patterns exist than ever before;
• major platforms are expanding support;
• interactive components are becoming available to teams that lacked technical resources;
• we’re finally addressing the factor that held adoption back: production economics.

I’m optimistic because we’re finally solving the problem that mattered most: the production economics of interactive email.

Interactive email could always work. The question was whether organizations could build, maintain, test it, and prove its value without creating operational overhead. In 2026, I’m starting to think the answer is becoming yes. 

Interactive email’s second act may be much more interesting than the first one. In a few years, I suspect we’ll stop talking about “interactive email” the same way we stopped talking about “responsive email.” It’ll just become “email.”