Key Takeaways

  • Resend scaled past four million users while managing technical email deliverability hurdles like DKIM, SPF, and CNAME record setup.
  • Early support volume created severe operational friction, leading CEO Zeno Rocha to admit, “I was so stressed out. I'm like dude I just need someone to be sitting on the chair.” (play from 17:50)
  • Rocha stopped ad-hoc customer replies, forcing agents to spend up to ninety minutes building public guides before closing a conversation.
  • Systematic documentation allowed Resend to identify structural developer pain points and adopt open protocols like Domain Connect to automate DNS setup entirely.
  • Lean developer tooling companies can turn support debt into compounding assets by adopting Resend's Link-Only Support Policy.

The Resend's Link-Only Support Policy

When developer products scale quickly, customer support often turns into an unscalable sinkhole. For Resend, the breaking point came from DNS configuration. Developers kept getting stuck setting up DKIM, SPF, and CNAME records. Rocha noticed that his team was writing the same detailed technical explanations repeatedly across hundreds of support tickets. He realized: “The majority of the questions we get today is just like people not able to set that up. And it's fascinating because we're serving a new audience, right? It's an audience that doesn't even know how to troubleshoot.” (play from 20:10)

Instead of hiring an army of reps to type custom explanations into private ticket threads, Rocha enforced a strict operational rule: “you can only respond to a ticket with a link. So you cannot just give the answer right away.” (play from 18:35)

The framework operates on three strict rules:

  • Prohibition of Direct Text Answers: Support agents are forbidden from typing a standalone answer directly into a support ticket.
  • Knowledge Base / Docs Publication: When a ticket arrives, the agent must pause, author a thorough public knowledge base article or documentation page that solves the issue, and publish it.
  • Link-Only Delivery: Respond to the user's ticket providing only the link to the freshly minted documentation, creating compounding reusability for all future inquiries.

Rocha acknowledged the upfront operational cost: “You had to stop write a knowledge base article, write a docs and then so it takes like an hour and a half maybe for you to answer a ticket. But guess what? Now you're sending that link all over again.” (play from 18:42)

Writing a public guide turns a single ticket into a permanent asset. Once published, that single URL resolves hundreds of subsequent inquiries from other users facing the identical issue, while also training search engines and AI developer tools on how to configure the platform.

When This Works (and When It Doesn't)

This rule works best when scaling technical developer products where repetitive edge-case questions, such as DNS record configuration, threaten to overwhelm a lean engineering team. In developer tooling, users encounter identical technical friction points: API key validation, webhook signatures, and DNS records. Creating a public knowledge base eliminates repeated engineering interruptions.

The policy breaks down during high-touch enterprise sales, account outages, or billing investigations. If an enterprise customer paying fifty thousand dollars a year hits a billing bug or platform downtime, pasting a generic documentation link feels insulting and dismissive. Do not apply link-only support to urgent production incidents, account security reviews, or high-value enterprise accounts that require white-glove empathy.

What to Do With This

Audit the last twenty customer support tickets your startup received this week. Group them by topic to locate the single technical issue that appears at least three times, such as OAuth callback errors or environment variable setup.

Draft a public troubleshooting page that walks through that exact failure state with code snippets and error screenshots. Next, inform your engineering and support teammates that manual text responses for this issue are now banned. When the next inquiry arrives, send a brief message with only the URL to that published page. Track ticket resolution times over the next fourteen days to measure the reduction in repeated queries.