Freshdesk Occasional Agents

Some people touch five tickets a month. A full seat for them is silly, and the Freshdesk occasional agent model is built for exactly that shape.

Full time against the Freshdesk occasional agent

Freshdesk splits agent seats into two types. A full time agent holds a permanent licence, billed per seat per month, and logs in whenever they like. An occasional agent does not hold a licence. They consume a day pass on the days they actually work in the helpdesk.

Both are real agents. Same interface, same ability to hold a role and a scope, same ability to be assigned tickets and reply to customers. The only difference is how the seat is paid for.

That last point matters more than it sounds, because it rules out the mistake people make with light-agent style models on other platforms. An occasional agent is not a limited agent. They are a normally powerful agent on a different meter.

How a day pass gets consumed

The mechanic is simple and the edge cases are where people get surprised.

A pass is consumed when an occasional agent performs work in the helpdesk on a given day. Once consumed, it covers that agent for the rest of that day, so a person who answers one ticket and a person who answers forty cost the same single pass.

Passes are bought in bundles and drawn down from a shared pool. Any occasional agent can use any pass in the pool, which is what makes the model work for a rota of engineers where you never know which two will be on call this week.

The details that actually vary by account: the price of a bundle, whether unused passes expire, exactly which actions trigger consumption, and which plans offer the option at all. Those move, so check the current Freshworks docs and your own billing page rather than trusting a number you read in a blog post, including this one.

The maths of when it saves money

Do the arithmetic before you decide, because it flips faster than people expect.

The comparison is straightforward. A full seat costs a fixed amount per month. An occasional agent costs the pass price multiplied by the number of days they log in. So there is a crossover point, a number of active days per month, above which the full seat is simply cheaper.

Work out your own crossover: divide your monthly seat cost by your per-pass cost. That's roughly how many active days a month an occasional agent can have before you should just buy them a seat.

In practice the model is a clear win for two shapes. Engineers and specialists who get pulled into support a couple of times a month. And seasonal surge cover, where you need eight extra pairs of hands for three weeks in December and none in February.

It's a clear loss for anyone who logs in most working days. A person who touches tickets twelve or fifteen days a month is usually cheaper on a full seat, and easier to reason about on the invoice.

Who should be occasional

A short list that covers most real teams.

Backend engineers who pick up escalated bugs. They need to read the conversation and add a note. They do not need a permanent seat.
Account managers who step in on a handful of their own customers issues.
Finance and billing staff handling the occasional refund dispute.
Holiday and peak cover, where the alternative is paying for seats that sit idle for ten months.

And who should not: anyone on the rota. Anyone with an SLA target against their name. Anyone who is measurably in the helpdesk every week. Those people are full time agents wearing a costume.

Two things that catch people out

First, budgeting. Day passes are a variable cost, which means a bad month can produce an invoice nobody forecast. Watch the pool balance the way you would watch any consumption meter, and set an internal alert when it drops below a couple of weeks of normal use.

Second, the accidental login. If an occasional agent opens the helpdesk to read something and performs an action, the pass is gone. Tell people this. The fix is usually to route what they need into Slack or Teams as a notification so nobody burns a pass to read one sentence.

The teams who get real value from occasional agents treat the pool as a shared budget with an owner. The teams who quietly overspend treat it as free.

FAQ

Frequently asked questions

Who should be a part time agent?

Anyone who touches the queue less than a day a week. A Freshdesk part time agent on day passes costs less than a full seat, and the maths flips somewhere around eight or nine active days a month.

What is an occasional agent in Freshdesk?

An agent who doesn't hold a permanent seat licence and instead consumes a day pass on each day they work in the helpdesk. They have the same capabilities as a full time agent, just a different billing model.

How much does a Freshdesk day pass cost?

Pass pricing and bundle sizes change and vary by plan and region, so check the current Freshworks pricing page and your own billing screen rather than relying on a published figure.

Does a day pass cover a whole day?

Yes. Once consumed, that pass covers that agent for the rest of the day, whether they answer one ticket or fifty. Two agents working the same day consume two passes.

When is a full seat cheaper than day passes?

Divide your monthly seat price by your per-pass price. If the person logs in more days a month than that number, buy them a seat. Anyone on the regular rota is almost always cheaper on a full licence.

Can occasional agents be assigned tickets?

Yes, they can be assigned tickets, added to groups and given roles like anyone else. Just be aware that assignment does not consume a pass, but the agent acting on the ticket does.

Cheaper seats, same duplicate problem

Every agent you add is another chance for two people to answer the same question more than once. Ticket Merger merges the duplicates before that happens.

Start free trial

14-day free trial. No credit card required.