SMF·FRESHDESK
Can a prompt replace Freshdesk?
Customer support — ticketing help desk
Exhibit tracking slip
Verdict
Freshdesk is the traditional shape of this category: tickets with priorities, SLA clocks, business hours and escalation rules. All of it is ordinary software and a weekend gets a working version, which is why this is a kinda rather than a no. The gaps are operational rather than technical — sending from a domain with a reputation, staying up, and the day-pass and AI metering that make the paid tier elastic in a way a fixed self-hosted install is not.
Exhibit A — The prompt
Received on31.07.2026Build a ticketing help desk whose SLA clock is honest.
Stack: your choice, Postgres, Docker Compose. Inbound mail via a signed provider webhook, outbound via a transactional provider on a domain you own with SPF, DKIM and DMARC.
Ticket model: subject, requester, assignee, status (open, pending, on hold, resolved, closed), priority, and a threaded message list. Threading by Message-ID and References with a subject-plus-sender fallback.
The SLA engine is the build, and getting it right is the difference between this and a mailbox:
- Define business hours per weekday plus a holiday list, in a configurable timezone.
- Define SLA policies matching on priority: a first-response target and a resolution target, in business hours not wall-clock hours.
- The clock starts on the first inbound message. It pauses whenever the ticket is pending or on hold — that is, when the ball is in the customer's court — and resumes when they reply. It stops on resolve.
- Every ticket shows time remaining, not time elapsed, and turns visibly urgent below a configurable threshold. A breached ticket is marked permanently: fixing it later must not erase that it breached.
- Store every pause and resume as a row, so the elapsed calculation can be audited rather than trusted.
Automations, kept to a readable rule table: on a trigger (created, updated, time elapsed) with conditions on fields, run actions (set priority, assign, add tag, send a templated reply). Rules run in a listed order and the ticket records which rules fired, so a mysterious assignment can be explained.
Canned replies with placeholders, a public status-free knowledge base of articles insertable into replies, and CSV export of tickets with their SLA outcomes.
One report: SLA attainment by priority per week, and the top five automation rules by fire count.
Write tests for the business-hours clock across a weekend, across a holiday, and across a daylight-saving change, and for pause and resume producing the same total as a manual calculation.
Do not build mobile apps, an AI agent, or a marketplace.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the mobile apps and push notifications when an SLA is about to breach
- B.2 the Freddy AI copilot and the automated AI agent sessions
- B.3 day passes for occasional agents, which is a genuinely good idea
- B.4 the marketplace of prebuilt integrations
- B.5 hosted uptime on a channel customers use when they are already unhappy
Prior art
Exhibit C — Why people still pay: ticketing operations at scale
Because SLA enforcement is only worth anything if somebody is woken up when it breaches, and because at nineteen dollars an agent the arithmetic against a self-hosted install plus your own time rarely favours building.
Questions
Why do business hours make the SLA clock hard?
Because a four-hour target that starts at 5pm on a Friday is due at 1pm on Monday, and every timezone, holiday and daylight-saving change is a chance to get that wrong. Tests for exactly those three cases are why this is a weekend and not an evening.
Why must a breach be permanent?
Because the point of the record is to learn from it. If resolving a ticket clears its breach flag, your SLA report will always look excellent and always be useless.
What is a day pass and why mention it?
Freshdesk sells $2 single-day agent access, so somebody who touches support twice a month does not need a full seat. It is a pricing idea a self-hosted install does not need to replicate — everyone can just have a login — but it explains why the paid tier is cheaper than the seat count suggests.
Can I get my Freshdesk tickets out?
Yes: the account data export produces tickets, contacts and knowledge-base articles, and the API pages through conversations if you want the threads with attachments. Fetch the attachment URLs before the account closes; they stop resolving afterwards.
Related tools
Receipt