Published on November 19, 2026

Email support is dead, long live support by email!

Ben Chuba
By Ben Chuba • 5 min read • Company

Sometimes, when it feels like you have an out there idea, the more you think and talk about things, the more clear it becomes that the idea isn’t out there at all. That’s the sort of process that led Mux, on the 1st of November 2026, to make the long debated decision to disable the ability to create tickets via email. But what does that actually mean in practice? Simply put: going forward ticket creation happens via our handy webform at mux.com/support, and ticket communication continues via the same trusty help@ email address. Let’s talk about why.

LinkWhy kill email ingestion?

In a word: spam. While we’re certainly no strangers to cleaning up the occasional email blasts, or requests from our “CEO” for Apple gift cards (I’m lucky my local pharmacy is within walking distance!): two major spam-adjacent events have driven up the need for this ingestion/communication split.

LinkMuse, Dots, and Grok Bot, oh my!

The recent rise in dedicated personal agentic AI has also led to an increase in well-tailored, convincing, and directed spam or phishing attempts. Muse hit 10 million users within one month of launch, and specifically advertises handling emails for you in their marketing. Even on legitimate requests, interacting with agents tends to be fairly effort-intensive. We’d rather they find our docs for agents first and foremost, leaving only the unanswered questions for their human counterparts (or our support team) to field.

Screenshot of Meta’s Muse agent marketing, headlined “Connects to your apps and builds its own tools,” showing Gmail, Instagram, and Facebook among the apps the agent can access.
Meta advertises email as a key feature of their new Muse agent.

LinkThe Support@ “Ticket Apocalypse”

On July 20, 2026, a rogue individual exposed a significant flaw in email etiquette and CC’ed together hundreds of support@ email addresses (a respectful BCC would be appreciated for future phishing scams, thank you very much!). Each support auto-responder created new tickets with us, to which we auto-responded, creating tickets with them. You can probably see where this is going, and regularly deleting 2000+ tickets isn’t where we want to be allocating our time.

There are some clever ways around this, specifically if the systems involved support RFC 3834, but we can’t count on that to be the case, and that’s speaking from experience: the 20th is just the worst this ever got, but it’s far from the only occurrence since.

Line chart of daily new Mux support tickets, flat near zero except for one sharp spike on July 20, 2026, caused by an auto-responder loop.
See if you can figure out which day is July 20th!

LinkWhat effect did this have on tickets?

Since making this change, we’ve been keeping a close eye on the emails that we’re receiving. The numbers bear out the need to make this change:

  • 73 percent of incoming emails were pure spam, phishing, or script injection attempts
  • Of the 27 percent that were legitimate, 78 percent of email senders went on to open a ticket through Mux’s support form
  • Incoming ticket counts have remained in line with historical baseline values

Additionally, one message immediately tested the limits of the new system: another case of an individual CC’ing together hundreds of support@ email addresses (this time a job application — they didn’t get the job). This email came in during off-hours, when our staff would not have been available to triage and get the situation under control as we had been able to previously. Under the previous system, this would have meant a ticket loop running unattended for hours. Now, these issues are dealt with swiftly and automatically, without any worry or input from our team.

Mux’s auto-reply email explaining that no ticket was created, directing senders to the online support form, and noting that an AI agent can help outside support hours.
Email us these days, and here’s what you’ll see.

LinkExtra credit

Of course, cutting down on spam isn’t all that we get out of directing developers to use our form for support rather than email. Having full control over the circumstances surrounding ticket submission allows us to collect and funnel additional information to our team, leading to better support experiences end to end. A user with a question about generating JWT tokens for Mux’s DRM features, may have context in their head that wouldn’t get relayed properly in pure text, but through our support form, we can ask them to pre-classify their ticket by category.

Mux support form with Category set to Mux Video, Subcategory set to DRM/JWT secure playback, plus Severity, Subject, and “How can we help?” fields.

Collecting this information also gives our automated Docs Agent crucial context, leading to better results when a developer needs an instant answer, or our team isn’t in the office.

Two buttons on the Mux support form, “Ask a human” and “Ask Docs Agent,” with a note that Mux’s team reviews every ticket and follows up during business hours if the agent can’t answer.
Talk to our Docs Agent, we promise they don’t bite!

LinkCan I still open a ticket without an account?

Yes! The last thing we wanted to do with this change is to put up a barrier to ticket creation that would lock out prospective developers, people having account access issues, etc.

While submitting a ticket from your actual account still gives our team the best context for answering your question, we definitely recognize that many questions need to be answered without an account.

Mux support page for logged-out visitors, with a highlighted “click here to submit a ticket” link for people without a Mux account or who can’t log in.
Submitting a ticket is as easy as clicking this link!

While the age of guessing a company’s support email address and firing off a quick request may be ending, Mux’s commitment to fast, quality, and personable customer support never will. Disabling email-based ticket creation allows our team at Mux to deliver even better support to you and your team, so if you’ve been waiting to reach out, we’d love to hear from you, there’s never been a better time.

Written By

Ben Chuba

Ben Chuba – Senior Customer Support Engineer, Team Lead

Tech enthusiast always chasing after the next new thing. Obsessed with solving your technical challenges. Proud owner of far too many board games.

Leave your wallet where it is

No credit card required to get started.