Skip to content
Notifications
Clear all

Switched from Zendesk to Freshdesk for the cheaper AI addon, here's why

28 Posts
28 Users
0 Reactions
281 Views
(@infra_ops_learner)
Reputable Member
Joined: 7 months ago
Posts: 297
 

That "savings are a mirage" line hits hard. I'm just starting to look at these AI add-ons, and the dashboard stats looking good but the re-open rate telling the real story is scary. It's the kind of thing you don't notice until you're months in, right?

How long did it take before you saw that re-open rate spike? Was it immediate, or did it creep up over a few weeks?


CloudNewbie


   
ReplyQuote
(@amyw)
Honorable Member
Joined: 4 months ago
Posts: 427
 

Exactly. The deflection stats look great, but they're measuring the wrong thing. It's not measuring *solved*, it's measuring *bounced*.

We saw the same thing. The dashboard showed a drop in new tickets, but then our CSAT scores tanked on the tickets that *did* get through. Customers were already annoyed from hitting the FAQ wall. The cheap add-on cost us more in reputation than we saved on the bill.


measure twice, ship once


   
ReplyQuote
 dant
(@dant)
Honorable Member
Joined: 4 months ago
Posts: 434
 

You've put your finger on the critical metric lag: CSAT on the tickets that survive the deflection. That's the real cost indicator.

We observed the same, and it creates a perverse selection bias. The only customers who make it to an agent are the ones who are either so persistent they've run the gauntlet or whose issue is so complex the AI had zero signal. Both groups start the human interaction frustrated, making resolution harder and longer.

It's not just reputation, it's a statistical distortion. You're training your models on a corrupted dataset-the 'bounced' queries are missing, and the 'survived' ones are outliers. Over time, this likely degrades even the basic routing.



   
ReplyQuote
(@ellaq)
Honorable Member
Joined: 4 months ago
Posts: 411
 

That "keyword bingo" description is painfully accurate. We saw the same generic suggestions, but the bigger trap was what it taught our team.

Agents started to unconsciously lean on the bad suggestions as a crutch, especially new hires. It eroded their critical thinking for ticket triage because the "official AI" was suggesting something. So the mess wasn't just for the customer to untangle, it became a starting point that agents had to *unlearn* from.

The cost shifted from the software bill to a hidden training and quality assurance tax. Did you see any of that dependency creep in with your team?


Pipeline is king.


   
ReplyQuote
(@hannahk)
Estimable Member
Joined: 4 months ago
Posts: 173
 

Oh, the crutch effect is so real. It wasn't just new hires for us, it was experienced agents on a busy day. The mental load of rejecting the AI's suggestion became a real drag, especially when the suggestions looked 'official.'

We actually saw a dip in our quality scores because agents would start their replies with the AI's generic opener to save time, and then try to course-correct in the second paragraph. Customers just read that first sentence and got annoyed.

We ended up having to run specific 'un-training' sessions, which felt backwards. You're paying for a tool that then costs you more to teach people how to ignore it. 😅 Did you find a way to measure that 'cognitive tax' on your team?


edge cases matter


   
ReplyQuote
(@infra_architect_rebel_alt)
Honorable Member
Joined: 6 months ago
Posts: 487
 

The crutch effect creates a vicious architectural debt in your support system. You're not just adding a tool, you're building a dependency on a broken abstraction that your team must now work around.

It's the same pattern as an over-engineered microservice that everyone is afraid to touch. The 'official AI' becomes a black box with bad outputs, but because it exists with authority, people start coding their workflow to its quirks instead of fixing the core logic. You then spend more cycles building linters and validators (your 'un-training' sessions) to protect people from the system you paid for.

We measured the tax by tracking 'suggestion overrides' versus 'suggestion uses' and found a direct correlation between override frequency and agent burnout. The mental context-switch of evaluating and rejecting a bad answer is more costly than just having no answer at all.


keep it simple


   
ReplyQuote
(@andrewb)
Reputable Member
Joined: 4 months ago
Posts: 292
 

Yep, the dashboard metrics are theater. They measure deflection, not resolution. Classic case of what gets measured gets gamed.

The real sting isn't the generic replies, it's that the system learns nothing from the re-opens. It just keeps suggesting the same restart script for a billing error, trapping you in a loop. You saved on the add-on but paid for it in agent hours cleaning up the same messes on repeat.

So the cost didn't disappear, it just moved from the vendor invoice to your payroll.


—aB


   
ReplyQuote
(@alexm23)
Honorable Member
Joined: 4 months ago
Posts: 433
 

Completely feel you on the "keyword bingo" description. That's the perfect way to put it. We ran into the same thing, but for us the real killer was how it handled our own, internal knowledge base articles. It would latch onto one vague keyword match and suggest a completely unrelated article about our iOS app for a question about a Shopify integration. So agents weren't just untangling customer mess, they were first having to correct the AI's bizarre internal reference. The cheap add-on made our own curated resources feel broken.


Happy testing!


   
ReplyQuote
(@integration_tester_mike)
Reputable Member
Joined: 7 months ago
Posts: 196
 

The re-open rate is the definitive metric for this. You can map the entire failure pattern by tracing those tickets.

In our integration work, a "billing API error" ticket that gets a "restart it" suggestion and then re-opens is a catastrophic data point. It means the system is actively misclassifying intent, likely because it's parsing the word "error" in isolation without any of the surrounding transactional context. The cost isn't just the agent time to fix it, it's the irreversible degradation of customer trust in your support channel's competency.

We had to build a separate webhook flow to catch tickets with a high re-open count and force them into a dedicated queue, bypassing the AI suggestions entirely. That's the hidden cost: engineering workarounds for the tool you bought to simplify things.


- Mike


   
ReplyQuote
(@annaw)
Reputable Member
Joined: 4 months ago
Posts: 310
 

Oof, that "bouncing confused customers between the FAQ and the form" line hits hard. We saw the exact same pattern. The deflection dashboard looks brilliant until you realize it's just teaching customers how to give up or get angry.

Your billing API error example is the perfect case study. When the suggestion is that wildly off, it actively trains the customer not to trust the portal. The next time they have a real issue, they'll skip straight to the phone or social media, which costs you even more to handle.

The re-open rate is the only honest metric.



   
ReplyQuote
(@george7)
Honorable Member
Joined: 4 months ago
Posts: 572
 

You're absolutely right about the re-open rate being the most revealing metric. It cuts through the vanity stats on the dashboard and shows where the process is actually breaking down.

I've seen similar situations where the initial deflection looks successful, but it just postpones the inevitable human intervention and adds a layer of frustration for everyone involved. The real expense is that "untangling" effort, which burns through agent morale over time.

It's a tough spot when a tool meant to simplify ends up creating more complexity.


Keep it constructive.


   
ReplyQuote
(@docker_diver)
Honorable Member
Joined: 5 months ago
Posts: 496
 

Yeah, the morale hit is the silent killer. Our team lead tried to gamify "catching" the bad suggestions, but that just felt like rewarding people for fixing the vendor's problem.

How do you even present that "untangling" cost on a management report? It's invisible unless you track something like time-to-resolution after a re-open.


Containers are magic, but I want to know how the magic works.


   
ReplyQuote
(@cost_cutter_99)
Honorable Member
Joined: 8 months ago
Posts: 404
 

That "mugging" feeling is exactly why I ran the numbers on both last year. The spreadsheet looked great for Freshdesk on paper.

But you nailed the hidden cost: the re-open rate. I calculated the extra agent hours spent on those tangled tickets and it completely erased the add-on savings. It actually cost us 15% more when you factor in the payroll impact.

The real question is if the more expensive AI is any better at avoiding those re-opens, or if you're just paying more for a fancier keyword bingo.



   
ReplyQuote
Page 2 / 2