How to choose a ticketing system for a small business (without paying for an enterprise help desk)

Search for "best ticketing system for small business" and you'll find lists of help desks built for customer support teams: live chat, call center features, SLAs per agent, per-user pricing. Great if you run a support department. Overkill if you're a pet store with three locations, a property manager or a clinic.

Here's a shorter checklist, written for businesses where "the support team" is whoever's working today.

1. Can requests come in the way people actually send them?

Not every request is an email. Staff report broken equipment in person, customers fill out a form, a tenant scans a QR code on the wall. Look for:

• A web form you can link to or put on your website
• A QR code you can print
• An email address that turns messages into tickets
• A way to type one in when someone calls

2. Does each kind of request get its own fields?

A repair needs a location, an urgency and a photo. A supply order needs items and a quantity. A time-off request needs dates. One generic "description" box means you'll be asking follow-up questions forever. Check that you can set up different forms and fields for different kinds of work without a consultant.

3. Can you enforce your own steps?

"New, In progress, Done" is a start. Better: your own steps, and rules like "can't mark Resolved until the cost is filled in." That's what makes the reports trustworthy.

4. Does the person who asked hear back automatically?

Half of "any update?" messages go away when requesters get an email when work starts and when it's done, plus a page where they can check. This is the feature small businesses notice most.

5. Can people outside your team use it without an account?

Customers, tenants and part-time staff shouldn't need a login to send a request. And if you're on Google Workspace or Microsoft 365, your team should be able to sign in with those accounts.

6. Is pricing sane for a small team?

Per-agent pricing adds up fast when everyone at the store needs to update a ticket now and then. Watch for minimum seat counts, features locked to top tiers, and "contact sales."

7. Will it still make sense with more locations?

If you have (or plan) more than one location, check that tickets can be assigned to a location, that each location can have its own inbox, and that reports split by location.

8. How hard is it to move in?

The best tool is the one you actually switch to. Can it import your spreadsheet history? Does it come with templates for common requests? Can you be live in an afternoon?

Where TicketStacker fits

We built TicketStacker for exactly this kind of business. Each kind of request lives in its own "stack" with its own form, fields, steps and rules. Requests arrive by form, QR code or email; requesters get updates without an account; and reports show volume, time and cost by location. Smart import brings your spreadsheet history over in minutes.

We're honest about where we're not the right choice: if you run a large customer support team that lives in live chat and phone queues, a full help desk will fit better.

Try it

Join the pilot. It's free while we build TicketStacker with a small group of businesses.