Jonni Lundy
Chief Operating Offer
Resend
Resend is a communication platform designed specifically for developers to build, test, and send transactional and marketing emails at scale.
Industry
Developer Tools
Support team
5
Monthly Volume
4,000
website
www.resend.com
Resend provides email infrastructure for developers. When their business grew 5x in a single year, support volume followed the same trajectory. Rather than scaling headcount to match, they built custom automation layers on Plain's API that now resolve over third of all support conversations without a human touching them.
When Product Growth Outpaces Team Growth
A single issue category, domain verification, was on track to consume 53 full days of agent time over the course of a year. That number alone told the story of what was coming.
JP Valery, Customer Success Engineer at Resend, mapped the full volume distribution across all issue types and modeled the cost against another fivefold growth year planned for 2026. The projected annual ticket load climbed above 100,000 that would require human handling.
"We’re often talking about 1% issues: minor bumps that compounds with scale into creating burdening drag for your support team and customers alike"
JP Valery
Customer Success Engineer
At that scale, throwing headcount at the problem wasn't a viable strategy. The team needed a way to absorb the volume operationally and sustainably.
With a five-person support team already manually handling 4,000 tickets a month, the math was straightforward: Resend could either hire aggressively and hope headcount kept pace, or find a way to resolve most of the conversations before they reached an agent.
They chose the second path and built it on Plain.
A Custom Automation Layer on Plain's API
Resend built three interlocking systems on Plain's platform, each addressing a different layer of the support problem.
Automated Triage and Resolution
Every incoming conversation now passes through an automated pipeline that classifies the issue, pulls in the relevant account data, and drafts a response. Plain's thread-level webhooks make this possible by giving Resend programmatic control over each conversation as it arrives. The team built the logic; Plain provided the infrastructure to run it at scale.
The pipeline works in three stages: a parser identifies what the customer is asking about, a contextualizer retrieves only the data needed to address that specific issue, and a handler generates a response. For well-documented, repeatable, and easy-to-process issues, this pipeline resolves conversations in seconds with no agent involvement.
Live Account Context on Every Ticket
Every ticket opens with live account data already surfaced, eliminating the need for agents to switch between systems to understand who they are talking to and what state that customer's account is in. Plain's customer cards and thread events make this automatic. At 4,000 support tickets a month, cutting even five minutes of context gathering per conversation reclaims an estimated 330 agent hours monthly. That efficiency gain applies whether or not a team has built any automation at all.
Graduated Trust for New Automations
Resend built a graduated trust model so new automations can be rolled out safely, rather than all at once. Features like notes, thread events, and enriched ticket context give the team the visibility they need to review how each automation behaves before it ever reaches the customer.
New automations always start with human review and approval. As they prove reliable over time, the team can give them more responsibility. What begins with a person checking every response can eventually run on its own, once the results are consistent. This approach lets Resend expand automation coverage without putting support quality at risk.
Because every part of the support stack is accessible through Plain, Resend can connect their own tools, adapt their logic over time, and keep extending the system as their operation grows.
Four Months In
Between November 2025 and March 2026, Resend tracked measurable gains across their support operation:
Automated resolution rate: 10% to 33%
One in three support conversations now closes without human intervention. For a five-person team handling 4,000 tickets a month, that shift removes hundreds of conversations from the manual queue each month.
Zero negative customer sentiment
Customers have not flagged automated replies as lower quality and for the most part haven’t realized it was an automated reply. The team has observed no change in how support interactions are perceived since automation began.
Faster responses on common issues
Customers writing in about known, well-documented problems now receive accurate answers in seconds rather than waiting for an agent to work through a queue. Customers care more about the outcome than the process: what matters is getting unblocked as fast as possible. When the ticket resolution is automated, it empowers them rather than keeping the issue standing in their way.
Higher-value work for human agents
The conversations reaching agents now skew heavily toward complex, context-dependent issues, the kind of work where experienced support professionals have the most impact.
What's Next for Resend
Resend's near-term goal is to reach over 80% fully automated resolution. Plain's architecture lowers the barrier to experimentation, which means the team can test new automation categories without disrupting how agents work day-to-day.
Resend's fivefold growth year did not break their support operation because the underlying infrastructure was designed to be extended, not configured. Plain gave them the API surface to build exactly what they needed, and the freedom to keep building as the business scales—and will accompany them as they repeat-or-exceed that growth this year.
