Over the past few months, AI customer service has gone live across LF. We've heard both support and skepticism — faster responses, but also feelings of less personal interaction, or feedback that didn't seem to lead anywhere. We've read all of it. This article addresses four things directly: why we chose AI CS, why fast replies can become an experience problem, whether switching back to human agents would change outcomes, and what the operations team is doing behind the scenes.

Every point deserves a real answer. No official language to deflect — just our actual judgment.

Why we chose AI CS: three things it consistently gets right

The decision wasn't about "AI being smarter." The logic is simpler: AI performs no worse than human agents on the vast majority of issues — and it consistently delivers three things human CS historically struggled to guarantee. We're not claiming AI is a perfect solution, but the reasons for choosing it are real.

Fast response. First replies used to take 1–3 business days, longer during busy periods. That wait is now essentially gone. Most players will have felt this directly.

Stable throughput. Backlog and unanswered tickets were common before. Daily volume has increased several times over; going unheard has become the exception.

Consistent attitude. Every submission is treated the same — ticket #1 or #100, regardless of tone. During peak periods, human agents couldn't reliably guarantee this. AI can.

On "consistent attitude": CS is repetitive and emotionally draining. When someone is processing their seventieth angry complaint of the day, staying fully attentive takes real effort to sustain. AI doesn't have this problem — it doesn't get tired, doesn't accumulate emotional weight, doesn't have off days.

These aren't claims — they're what actually happened.

Fast AI replies that feel "lightweight": that feeling is valid

AI's speed can itself be a problem.

Seconds-fast replies make it hard to feel "someone actually read my message." With human agents, the wait carried a signal: someone is looking into this seriously. AI removed the wait — and that signal with it.

We've made adjustments: adding a status message before the formal reply, referencing the player's specific situation in responses. But these changed the form without fixing the underlying missing signal.

The deeper challenge: players don't just need an answer — they need to feel someone is responsible for their issue. AI can't fully deliver that yet. We're working on it, but we won't say it's solved.

Issues AI can't resolve: human agents would have the same outcome

Real frustration: a lot of words, no real result. But in most cases, the reason isn't AI — it's that there's no answer available right now.

Common situations: a game rule won't change because someone complained; a bug is confirmed but not fixed yet; account issues lack the info needed to locate them; a request is beyond current scope — not from unwillingness, but from real limitations.

In all these cases, human agents could only deliver the same message more warmly — same outcome, warmer delivery.

The path to solving these issues runs through game design and operations decisions — not through the customer service layer.

Worth saying directly: when a player is already frustrated and gets an AI reply — especially realizing they're not talking to a real person — the emotional need doesn't get met. That part isn't good enough, and we're not going to offset it with "overall efficiency improved."

Both are true: AI is making this community work better, and some experiences still fall short. We're not using one to paper over the other.

The operations team is still here: your feedback is in the pipeline

AI handling tickets doesn't mean the team stepped back.

Before, repetitive tickets consumed all available capacity. AI freed that up for upstream work: analyzing recurring issues, pushing them to design and version planning, handling complex cases that require human judgment.

When a bug is reported enough times, it gets technical priority. When a request type keeps appearing across versions, it enters design review. This pipeline used to short-circuit. Now it's running — several long-running issues have had targeted changes in recent versions. Not coincidence.

Your feedback didn't disappear. You just can't see where it went.

Three changes you can point to

Three specific examples, not abstract claims.

Account security improvements. Account issues — can't recover, binding errors, login failures after switching devices — consistently ranked highest in feedback. After AI absorbed a large volume of these cases, the back-end gained a clear picture of where failures clustered. This drove changes to the account security system. The secondary email feature is one result: an additional way to protect and recover accounts. It's fully rolled out.

Bug identification speed. Before: CS compiles complaints → categorizes → passes to dev → dev reproduces → identification begins. Every link costs time. Now the back-end runs real-time anomaly monitoring, and AI cross-references player descriptions with system log signals — closing the gap between "players reported this" and "dev knows the root." Many issues this version were identified several times faster.

Payment and order queries. Before, every case required a human to manually log into the back-end — limited by shift hours, next-business-day waits were the norm. Now AI retrieves order and payment records directly. Most query issues are automated: submit, get a confirmed result in minutes.

Same logic across all three: AI handled what needed handling, so speed and coverage both went up.

One thing that helps everyone: when reporting a Bug or functional issue, describe the steps to reproduce it — what you did, what triggered it. That's the key information for technical investigation, and clear steps make a real difference in how fast we can find the root cause. Not a format requirement, but the one thing that genuinely matters.

Comments in the relevant thread are the most direct feedback channel — more visible than opening new posts or sending private messages. We're reading.

For issues involving account details, orders, or other personal information, please submit through the Support module rather than posting publicly — we can't protect personal information in public posts.

The team is giving everything we have to improving the game. It's getting better — and every piece of feedback you've submitted is part of that.

LF Operations Team

ShireHub

Coal