Running on Freshdesk?

Freshdesk automations or SLAs misbehaving? We clear the backlog.

Freshdesk is easy to bring up and slowly accumulates workarounds until nobody is sure which observer, supervisor rule or scenario is handling an incoming ticket. We follow a sample ticket through the rulebook, align your SLAs with reality, and rebuild the custom-app webhooks so dispatch stops leaving tickets unassigned on weekends.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

freshdesk-api.log

still broken

What it is

Freshdesk at a glance

Freshdesk is a cloud helpdesk from Freshworks, launched in 2010 and based in San Mateo and Chennai. It turns email, chat, phone, WhatsApp and social messages into a single ticket queue, with a Kanban-style agent UI, SLA tracking, and a marketplace of apps that extend the ticket side panel.

Mid-market and SMB support teams tend to pick it as a lower-friction alternative to Zendesk, with the Freshsales and Freshchat products stitched in through the broader Freshworks suite. Automations run on three rule engines: dispatchers on creation, observers on update, and supervisors on schedule. Knowing which fires when is usually what separates a clean inbox from one nobody trusts.

Type
SaaS helpdesk and ticketing
First released
2010
License
Proprietary, per-agent subscription
Maintained by
Freshworks Inc.
Typically used for
Multi-channel customer support, SLAs, ticket routing, customer portal

The honest version

Freshdesk pros and cons

No technology is all upside. This is where Freshdesk earns its place and where it tends to cause trouble.

Where Freshdesk is strong

  • Easy to adoptThe default setup gets a support team taking tickets in hours, not weeks. The UI is kind to new agents and the training cost is low.
  • Three rule engines cover most flowsDispatchers handle creation routing, observers react to changes, and supervisors run on a schedule. Between them, most queue logic is possible without writing code.
  • Omnichannel is built inEmail, chat, phone, WhatsApp, social and the customer portal come into the same queue at the same tier, so agents are not switching tools to answer a message.
  • Freshworks suite integrationFreshsales, Freshchat and Freshservice share identity and contacts natively, which removes a layer of connector work for teams already on the platform.
  • Reasonable per-agent pricePricing at the Growth and Pro tiers compares favorably with Zendesk, which still wins the budget conversation at many mid-sized shops.
  • Custom-app frameworkThe sidebar app SDK lets you pull context from internal systems next to the ticket without a redirect or a popup.

Where Freshdesk bites

  • Three rule engines are easy to confuseWhich of dispatchers, observers or supervisors applied to a ticket is not always obvious from the activity log. Teams end up with conflicting rules nobody wants to delete.
  • Reporting is unevenThe built-in dashboards cover surface metrics; anything deeper usually means exporting to a warehouse or paying for Analytics Pro. Custom metrics can be harder to build than you expect.
  • API rate limits are strictPer-minute caps on a plan level mean bulk operations have to pace themselves. Sync jobs that worked at twenty agents fail at eighty without rework.
  • Marketplace apps vary in qualitySome are well maintained; some have not been touched in years and silently stop working after a platform update, leaving you to notice when agents complain.
  • Attachment limits hit real ticketsThe twenty megabyte per-ticket cap is small for teams dealing with screen recordings or diagnostic bundles. Workarounds all have trade-offs.
  • Migrations in and out are painfulRound-tripping tickets, time entries and private notes between Freshdesk and other helpdesks loses more fidelity than the marketing materials suggest.

Sound familiar?

Common Freshdesk problems we fix

The Freshdesk problems that bring people to us, and what you have once each one is fixed.

Observer skipped: condition did not match

Observers are not firing when expected

A condition set to any-event rather than status-changed, a group-scoped rule applied to tickets in a different group, or an order-of-rules issue where a prior observer closed the ticket.

Observers trigger on the right updates

HTTP 429: Rate limit exceeded

API jobs hit the per-minute limit

A backfill that polls /tickets every second, a webhook replay without backoff, or a reporting script that lists one page per minute for every agent.

Jobs paced inside the quota

SLA breach: first_response_due_by exceeded

SLAs breach despite agents being online

A business-hours calendar that still uses last year's holidays, a priority mapping where nothing maps to the right SLA, or a dispatch rule that never assigns a group so the clock never pauses.

SLAs reflect real response times

Webhook to custom app failed with status 500

Custom-app webhooks silently drop

An endpoint that times out above the ten-second limit, a payload that trips a strict JSON parser on the far side, or an OAuth token the installer never rotated.

Webhooks deliver and retry

Supervisor rule last executed over 24 hours

A supervisor rule never runs on the right tickets

A supervisor set to run hourly whose criteria exclude every ticket because a field was renamed, leaving the dashboard quietly aging stale items.

Supervisors doing their nightly work

HTTP 400: product_id is not a valid product

Ticket creation from an integration fails

An external form posting a product identifier from a different environment, or a required custom field whose dropdown was pruned in setup.

Intake creates tickets cleanly

Freshdesk-Marketplace install failed

A marketplace app will not install

A manifest asking for a scope the account does not grant, an older iparams schema, or a product version the app has not been updated for.

App installs and renders

Attachment upload rejected

Agents cannot attach a diagnostic bundle

Files above the per-ticket cap, or attachments that total more than the ticket-level limit after agent replies add context.

Attachments routed around the cap

What we do

Freshdesk help, from rescue to upkeep

Call us for one failing automation, or move the whole helpdesk setup onto us.

Rescue
Tickets going unassigned, SLAs breaching invisibly, or a marketplace app locking agents out. We stabilize the queue first and explain what caused it second.
Automation audit
Dispatchers, observers, supervisors and scenarios reviewed in order, with conflicting rules retired and the surviving ones documented.
SLA and business-hours cleanup
Calendars, priorities and policies brought back in line with the way your team actually works.
Custom-app development
Side panel apps and serverless functions written to the Freshworks developer platform, with proper OAuth and retries.
Reporting and warehouse exports
Ticket, agent and conversation data piped out to BigQuery, Snowflake or Looker when the built-in dashboards stop keeping up.
Managed Tech
Monthly automation reviews, rate-limit watchers, webhook dashboards and a US engineer to call when something behind the agent UI changes.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Freshdesk alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Freshdesk questions

Something else? Call+1 737 727 7327

Why are my Freshdesk observers not firing?

Observers run on ticket updates, which sounds obvious until you check whether the update actually changed the field the observer watches. A dispatcher may have already moved the ticket to a group the observer is scoped out of, or a prior observer may have changed status and ended the chain. We trace it ticket by ticket using the activity log.

How do we stop breaching SLAs on tickets that agents answer quickly?

The common answer is that the SLA clock does not pause the way the team assumes. Business-hours calendars with wrong holidays, priorities that map to the wrong policy, or dispatch rules that never assign a group all leave the clock running. Fixing the policy and the calendar together is almost always what the team wanted.

Can we migrate from Zendesk to Freshdesk without losing history?

Mostly, yes. Public ticket content, requesters and tags move cleanly. Private notes, time entries, macros and some custom-field types need per-field work, and attachments sometimes have to be rehomed outside of the migration tool. We plan the cutover with a parallel window so customers do not see a gap.

Why do our custom-app webhooks fail intermittently?

The three usual causes are endpoints that occasionally exceed the ten-second response budget, payloads that trigger a stricter JSON parser only when optional fields arrive, and OAuth tokens that expire during a long execution. Logging on both sides and a short retry queue clear up most of it.

Is Freshworks reporting good enough for exec dashboards?

For agent and ticket volume metrics at a weekly cadence, yes. For cross-channel analysis, custom funnels and cohorts, most teams end up exporting to a warehouse. We build the pipeline from Freshdesk to the warehouse your BI team already uses so the exec view is not stuck in the helpdesk tool.

How much does Freshdesk help cost?

Quotes are at no charge. Tell us which rules are misbehaving and what the queue is doing, and a price lands in your inbox before any work begins.

Free estimate

Freshdesk acting up?

Share the queue behavior and any relevant rule names, and a Hawkins.Tech engineer replies with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.