r/mxroute

How do we stick it to the rest of the industry and actually use LLMs to responsibly help with customer support?

Most people these days would probably say "You can't." I get the instinct. Everyone is using AI wrong. EVERYONE. I cursed endlessly at the Disney Plus AI just the other day, worthless junk. Everyone is trying to use AI to replace humans on support, and force customers to talk to an AI. AI can't handle customer support, it's simply too complex.

For me though, I've been waiting for AI my whole life. This isn't something I'm trying to use to save money. I'm not trying to weight the loss of revenue vs the savings from firing the support team. So while everyone else is misusing AI to completely bomb customer support, I have a question to answer: How do I make everyone else look bad and use it the right way? 

I actually have an answer. Most of you that received a support ticket response in the last two weeks unknowingly saw the answer. It's actually pretty simple. That's why it makes everyone else look stupid, and I like that. I needed a confidence boost.

The answer is that it doesn't replace support at all. It's a tool that helps support run faster, smoother, and with more accuracy. Here's how it works:

Our obsessively secured, completely private and locally hosted LLM, read every support ticket that we've answered this year. It can access logs and basic account information by internal API, and no it has absolutely no way of exfiltrating that data. Nor does it have a way of accessing the functions that limit it's access. Simply, it guesses what we were most likely to say in reply to a support ticket, and it writes that in a draft. The human walks in, checks the ticket and draft, and makes a decision. Is this what I would have sent? If yes, send it. If no, reject it (and send feedback to the LLM). If almost, edit and then send. If the reply requires action from us, it determines what we were most likely to say and leaves us a note with the required actions to send the draft (if we agree, of course).

The customer never speaks to an AI. The AI simply helps the human reply faster. Less browser tabs, less log greps, less "I forgot how that feature works, let me check before I reply."

Just because everyone else is using it wrong doesn't mean we're not going to use it. We're just going to use it as a middle finger to all of them.

Our support ticket backlog is down to the smallest levels in years. We're almost completely caught up. A human has been involved in every single ticket. And best of all: We didn't have to increase prices to do it.

reddit.com
u/mxroute — 3 days ago

Documentation Improvements

The real large one is here:

https://docs.mxroute.com/docs/troubleshooting/smtp-rejections.html

This is the massive result of years of customers demanding we filter this or that better, and me wanting to return specific errors for different scenarios. It means we have quite a large number of potential SMTP responses, and keeping up with them can be a bit messy.

The next, the management.mxroute.com portal is now fully documented:

https://docs.mxroute.com/docs/management/

And finally, the panel.mxroute.com control panel is now fully documented as well:

https://docs.mxroute.com/docs/panel/

My position has been "The button is right there. You don't need to read an article to see it." Obviously, that attitude has been a failure. We're constantly asked questions about buttons that are right there. So there we are, complete product documentation.

reddit.com
u/mxroute — 4 days ago
▲ 18 r/mxroute

"This email account is suspected of being compromised"

A lot of you have seen this SMTP response. It means you tripped a filter designed to catch the moment that a bad actor successfully tests your SMTP credentials. It blocks all outbound mail until I personally review the behavior and either clear the block or open a support ticket with you indicating the problem, the evidence, and the path to resolution. It also catches you every time you send "SMTP test" because I'd rather catch an unimportant email than let a compromised account run free for a while.

There was a time where this would catch less than 5 email accounts per week, and this manual review consumed very little of my time. For a while now, it has consumed a great deal of time because you people can't keep your shit secure. It's fine I get it, things happen, but the real point is we've outgrown manual review.

The problem with automation has been that the decision to clear the block or suspend the email account requires strong reasoning well beyond the capability of scripting. You need an eye for it.

As of tomorrow, this job is being taken over by my GPU (in an environment so well secured it could only be explained by extreme paranoia). It has been trained on the data, and it has greatly exceeded the logic of both my filters and my reasoning. For the past week it has been running for observation and detection only. It had 1 false positive, while my outbound filters designed to catch these have had as many as 5 false positives per day during the same time frame. Each one of my false positives were unable to send mail for several hours while awaiting human review.

What this means for you:

  1. Faster resolution for accounts suspected of being compromised.

  2. No outbound block until compromise has been confirmed.

  3. Less false positives.

So basically, it's a win for everyone and a negative for no one. Except maybe for people who hate GPU workloads, but they're creeps anyway.

reddit.com
u/mxroute — 6 days ago

One time password generator on MXRoute

I have a web service that uses one time passwords for the login authentication. Given that MXRoute has a “no cold emailing” policy, would utilising their email servers to set this up violate their terms and conditions?

While it does not seem like it would violate the “cold emailing” policy (since users would be prompting the code to be generated) any input based on your experience would be greatly appreciated.

reddit.com
u/LabcoatMonkey — 9 days ago

Newsletters again

I'm looking for a new email provider for a non-profit railway enthusiast group in New Zealand. As well as general membership inquiries etc, we email out a newsletter 6 times per year to 550 of our members who provided email addresses when they joined, but this is not an automated process with self-sign-up.

The newsletters are generally updates about the various local chapters and railway preservation activities, but once or twice a year there is a promo for a new book published by the society.

Comments to the posts linked below suggest that promotional material forming a small part of a regular newsletter is OK, but somewhere mxroute said something like "if you're trying to find a way around our rules then it's marketing" and I don't want to risk getting the society cut off.

How close to the marketing line does this fall?

Older relevant posts:

https://www.reddit.com/r/mxroute/comments/1u862g8/optin_newsletters/

https://www.reddit.com/r/mxroute/comments/1kplts2/mxroute_also_as_a_newsletter/

PS: Previously posted as a comment but got no reply to one of the posts above

reddit.com
u/trainchaser_nz — 11 days ago

Reseller plans listed, but not available?

I'm trying to setup a Reseller 75 plan/account for my business, but all Reseller plans are shown as unavailable this morning. Any insight into when these may be available again, or do I need to look elsewhere? Thanks!

reddit.com
u/eight_heads — 14 days ago

Reseller user impersonation for API

Spent a few hours today redoing the user impersonation system on the panel. Mitigating third-party bugs caused unnecessary complications in that code path, which held back this change. The result: resellers can now manage customer accounts via API. This enables the easier creation of custom control panels for resellers who want to completely own the UX.

Alright, back to support tickets and migrating Dovecot indexes to SSD on the Safari server.

api.mxroute.com
u/mxroute — 11 days ago