Helpdesk & Complaint Ticket Tracker · for Small businesses & service providers
A customer helpdesk with a public ticket form and private follow-up links
A customer fills in the public form and gets a ticket number and a private link; your team assigns the ticket, replies, adds notes the customer never sees and moves it to resolved. A customer reply reopens it; closed is final. Spam is kept off the form by a hidden honeypot and a per-address hourly limit.
One-time payment · full source code · instant download · optional installation add-on · non-refundable
Sound familiar?
- Complaints arrive by phone, WhatsApp and email and the same customer is answered three times — or never.
- Helpdesk SaaS is priced per agent per month and expects an email inbox to connect.
- Nobody knows which tickets are older than two days.
- Two staff edit the same ticket and one overwrites the other.
How it works
- 1
Publish the form
Link the public ticket form from your website; customers choose a category and priority and get a ticket number such as TKT-00001 and a secret follow-up link.
- 2
Work the queue
Assign tickets to agents, reply, add private internal notes, set open → in progress → resolved. Filter by status, priority, agent or search.
- 3
Keep it honest
A customer reply reopens a resolved ticket; closed is final. Stale-page protection stops two staff overwriting each other, double-submitted replies are stored once, and the dashboard flags tickets older than 48 hours.
Nothing is changed in your ad accounts automatically: every recommendation is approved and applied by you, and drafted campaigns arrive paused.
What you get
- Public ticket form with category and priority, honeypot and hourly rate limit
- Ticket numbers and secret follow-up links — customers need no account
- Staff replies and private internal notes; open, in progress, resolved, closed statuses
- Assignment to agents; filters by status, priority, agent and search
- Dashboard: open, in progress, unassigned, high priority, older than 48 hours
- Full PHP + MySQL source code; one-time purchase
The full list of what is in the download (9 items from the README) is on the product page.
Screenshots
From the application itself, with sample data.
A good fit if… and not if…
Good fit
- Small service businesses, software vendors and housing societies handling complaints
- Teams that reply from the ticket page rather than an inbox
- Developers adding a support desk to a client's site
Not the right tool when
- Email in and out (replies are read on the ticket page via the private link)
- File attachments, SLA timers beyond the 48-hour flag, canned replies, satisfaction surveys or live chat
- Separate staff logins with permissions — agents are names you assign tickets to
Questions small businesses & service providers ask
Does it send emails?
No. Customers follow and reply through their private link; you may add email sending as a customisation.
Do customers need an account?
No. The ticket number and secret link are the account.
Can several agents log in?
There is one admin login; agents are names tickets are assigned to. Per-agent logins would be a customisation.
How is spam handled?
A hidden honeypot field and a per-address hourly limit on the public form.
Can a closed ticket be reopened?
Resolved tickets reopen when the customer replies; closed is final — open a new ticket.
Can I see it first?
Yes — preview pages with sample data.