5 signs it's time to switch your helpdesk

Switching helpdesks is operationally annoying enough that most teams stay one or two years longer than they should. The problem with delaying is that the cost of staying compounds: AI bills creep, admin time eats engineering hours, and the team starts working around the platform instead of in it. Here are the five signs that the relationship has aged out of fit.

Sign 1: Your AI bill grew faster than your conversation volume

If you're paying per-resolution or per-session AI fees, look at the last 6 months of invoices. AI cost per conversation should stay flat or fall as your volume grows (because resolution rate improves with grounding maturity). If your AI cost per conversation is rising, the metering model is fighting your scale, not supporting it.

Threshold: AI cost rising more than 1.5x the rate of conversation-volume growth over a 90-day window.

Sign 2: You upgraded a tier just to unlock one feature

This shows up classically with reporting (Zendesk Explore, Freshdesk Analytics), AI (Freshdesk Freddy add-on), or compliance (Front Compliance, Zendesk Advanced Data Privacy). The upgrade always costs more than the feature would justify standalone, because the vendor designed the tier-gate to capture additional spend.

Threshold: more than one tier upgrade in 12 months for a single capability.

Sign 3: Your team built a workaround instead of asking the platform

If the engineering team is writing scripts to enrich tickets, the support manager is maintaining a Notion dashboard because the built-in reports don't cover what they need, or somebody is manually copying data between systems daily — the platform has stopped serving the team. The workarounds compound and become the new dependency.

Threshold: more than 3 hours per week of manual workaround work that should be in-product.

Sign 4: A channel your customers expect isn't supported

This is especially common for emerging-market and DTC teams. WhatsApp is supported but Telegram isn't. SMS goes through a third-party connector that breaks twice a month. The X DMs your CEO promised in a tweet take 4 days because nobody on the team has access. The platform's channel coverage hasn't kept up with your customer base.

Threshold: more than one channel where you're either unsupported or paying for a fragile third-party connector.

Sign 5: Procurement is asking the same questions every renewal

If finance is asking for usage forecasts that you can't reliably provide because the bill is too lumpy, or legal is flagging the contract because clauses around AI metering aren't bounded, or security is asking about prompt-injection posture and the answer is "we'll get back to you" — the platform's commercial and trust posture is no longer ahead of the buyer's bar. That's a leading indicator that the renewal is going to be hard.

Threshold: more than two unresolved procurement questions at renewal time.

What to do once you've spotted three of the five

If you've nodded along to three or more of these signs, run a 30-day evaluation against an alternative. Pick a vendor whose pricing model fixes Sign 1 (per-conversation pass-through), whose plan structure fixes Sign 2 (no tier upgrades for single features), whose feature set fixes Sign 3 (built-in reporting and automation), and whose channel coverage fixes Sign 4. Compare the loaded cost over a 24-month horizon. If the math works, the operational benefit is real and the migration is the cost of getting there.

How Deskwoot handles each sign

• Sign 1: per-conversation pricing scales linearly, never punishes growth
• Sign 2: 3 tiers, all major features available on Pro
• Sign 3: built-in reporting, visual rule builder, no scripting required
• Sign 4: 8 first-class channels including Telegram, LINE, SMS, X DMs
• Sign 5: published pricing, fixed AI rate, prompt-injection protection by default