Two people from your team answered the same enquiry on the same day. A customer wrote in last Thursday and nobody replied. You found the message four days later sitting in a shared inbox that nobody owns.
The problem was not that your team did not care. The problem was the inbox. A shared inbox has no status. It has no owner. It is a list of emails, and nothing in it tells you what is waiting, what is done, and what has fallen through.
You needed a queue. Something where every incoming enquiry becomes a ticket, every ticket has a status, and every ticket has a person responsible for it. Freshdesk came up. Free plan. You signed up.
It works. The ticket list is there, the assignee field is there, and the status is there. The problem is not that Freshdesk fails to do the job. The problem is that it is built to do thirty other jobs alongside it, and the platform you are running is sized for a customer support operation, not a three-person team handling twenty tickets a week.
The Four Things Your Team Actually Opens
A ticket queue. A status on each ticket. An assignee. A reply thread.
That is the job. You know a ticket exists, you know whether it is open or resolved, you know whose responsibility it is, and you can see what has been said. Everything else is infrastructure for a support operation that does not look like yours.
Freshdesk also gives you Freddy AI, a chatbot builder, a knowledge base, a community forum, customer satisfaction surveys, SLA policies with escalation rules, multilingual support and localisation, Freshcaller voice integration, ticket field customisation at scale, and analytics dashboards. None of it is hidden. It is all sitting in the platform, waiting to be configured, adding to the surface area of a tool you opened to solve a very small problem.
- Freddy AI answer bot and chatbot builder
- Knowledge base and community forum
- Customer satisfaction (CSAT) surveys and reports
- SLA policies and escalation rules
- Multilingual support and localisation
- Freshcaller voice integration
- Ticket field and form customisation at scale
- Analytics and performance reporting
- Ticket queue with status (open, in progress, closed)
- Assignee per ticket
- Reply thread and internal notes
- A way to see what is still waiting
Who Freshdesk Is Actually Built For
Freshdesk is a serious tool for customer support teams handling hundreds of tickets a day across multiple channels. Businesses with dedicated support agents, SLA commitments, and a support operations function. Teams where someone's full-time job is to configure and maintain the helpdesk.
The free plan is a hook. It gives you enough to get started and to get your ticket data into the platform. The features that make Freshdesk genuinely useful at scale, including automation rules, advanced reporting, and SLA management, require paid plans. Growth starts at around A$20 to A$25 per agent per month.
If your business has three support agents and twenty tickets a week, Freshdesk is built for a different customer. You are not running a support operation. You are running a queue. A queue does not need a helpdesk platform.
A Note on the Free Plan
Freshdesk's free plan is real. For up to ten agents, there is no charge. If cost is the only question, the free plan is a reasonable answer at small scale.
But cost is not always the only question. A Merebase app makes sense when you want the tool built exactly for your process, not the other way around. It makes sense when you want your ticket data on your own hosting rather than inside Freshdesk's platform. And it makes sense when you want to pay once rather than depend on a platform that can change its pricing or terms at any time. A platform that is free today has changed its plans before and will change them again.
What you build is yours. The data is yours. The tool does not disappear because a pricing team in San Mateo changed the free tier.
What a Merebase support ticket tracker Includes
A Merebase support ticket tracker is built for the job your business actually has. You describe the statuses you use, the way enquiries come in, how your team assigns work, and what information belongs on a ticket. The app is built to do exactly that.
What a Merebase support ticket tracker includes:
Support ticket queue with status (open, in progress, waiting, closed). Customer intake form so enquiries come straight in without a customer login. Assignee and status tracking per ticket. Reply thread and internal notes per ticket. Search and filter by status or assignee. Data export. Unlimited agents. A$499 once. You bring your own hosting. A basic plan runs A$5 to A$20 a month.
There is no AI bot to configure. No knowledge base to populate. No SLA policy to set. The app does the queue. Nothing else clutters the screen.
Customers Do Not Need an Account
One of the things that gets quietly complicated in a helpdesk platform is how customers actually submit tickets. Some platforms want customers to create an account. Some route everything through email. Some need you to embed a widget and configure the routing.
A custom intake form is built into the app from the start. A customer fills in the form. The ticket appears in the queue. Your team picks it up. Customers do not need a login. They do not need to know what software you are using. They fill in a form and wait for a reply.
Three Years of Freshdesk Growth vs. A$499 Once
Freshdesk's free plan holds up well at very small scale. But if your team grows to a point where you need automation rules, or if Freshdesk changes the free plan terms, the Growth plan at around A$22 per agent per month becomes the cost of running a queue.
Three agents. Three years. That is the cost of staying on a platform subscription for a tool that does more than you need.