How do I build a simple way for my team to log and track requests?

By Ranjit Bhinge, founder of Blur Studio · Updated · 8 min read

Short answer: A ticketing system is a shared list where every request gets one record with an owner, a status and a date. For a team of 10 to 30 people you need only six fields, four statuses and one weekly report. You can build it three ways: a ready-made helpdesk subscription such as Jira Service Management (Atlassian's tool for handling service requests), a no-code app on top of a spreadsheet or list, or a small custom app. Start with the smallest one that gives every request a single owner.

Ranjit Bhinge

You want your team to stop losing requests in email and chat, and you want a simple system you can set up without buying a full helpdesk.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Most small teams do not need a helpdesk with forty features. They need one place where a request goes in, someone owns it, and you can see what is stuck. This page gives you the smallest design that does that, then compares the ways to build it.

What a ticketing system actually is

A ticket is one request: "the printer is broken", "customer wants a refund", "please add a new hire to the system". A ticketing system keeps every ticket in one list, so nothing lives only in someone's inbox. Big tools add queues (lists of waiting work), portals where people submit requests, and service level agreements, often shortened to SLAs, which are promised response times. Atlassian's documentation for Jira Service Management describes these pieces: requests, queues, goals (its name for service level agreements) and help centers where customers send requests. You can get most of the value without any of them.

The minimal data model: six fields

A data model is just the list of facts you store about each ticket. Keep it to these:

  1. Title: one line saying what is needed.
  2. Details: a longer description and any files.
  3. Requester: who asked, and how to reach them.
  4. Owner: one named person, never a group. A ticket with a group owner has no owner.
  5. Status: see the next section.
  6. Dates: created, and last changed. Add a due date only if you will really use it.

Two optional fields earn their place later: a category (so you can see which kinds of requests repeat) and a priority (only two levels, normal and urgent, or people mark everything urgent).

The minimal workflow: four statuses

Use New, In progress, Waiting on someone and Done. "Waiting" matters most. It separates tickets that are stuck because of you from tickets stuck because of the customer or a supplier. Add statuses only when you can name a decision they change.

Three rules make it work:

  • Every new ticket gets an owner within one working day.
  • The owner changes the status when things change, not at the end.
  • Nobody replies to requests in side chats. The reply goes on the ticket.

The one report you need

Once a week, look at three things: how many tickets are open, how many have not changed in 7 days, and which category got the most new tickets. The second number is the useful one. If it keeps growing, you have a capacity or ownership problem, not a tool problem.

Four ways to build it

RouteSet-up timeOngoing costWatch out for
Shared sheet and a formAn afternoonFreeNo history, easy to break; a script can send email alerts but someone has to maintain it
List tool you already pay for (for example Microsoft Lists or SharePoint, if you use Microsoft 365)A dayIncluded in the plan you haveCustomising it takes patience; check your plan
Helpdesk subscription (Jira Service Management and similar)A few daysPer agent, per monthCost grows with the number of people working tickets
No-code or custom appOne to four weeksHosting, plus build cost if customYou must decide the rules up front

Helpdesk subscriptions charge per agent, meaning per person who works tickets. As of November 2026 these are the prices on the vendors' own pages:

  • Jira Service Management: a free plan for 3 agents with unlimited customers, 2 GB of file storage and 100 notification emails a day. Standard is shown at $21.50 per agent per month and Premium at $55.28. Customers who only submit requests are not charged.
  • Freshdesk (a helpdesk from Freshworks): Growth $19, Pro $55 and Enterprise $89 per agent per month billed annually, with a 14-day free trial and no permanent free plan. Ticketing and a customer portal come in every plan, and Pro adds multiple SLA policies and smarter routing of tickets to agents.
  • Zoho Desk (a helpdesk from Zoho): a free edition with 3 user licences and email ticketing. Paid editions start with Express, which adds web form tickets, workflows and escalations. Zoho shows rupees by default, so switch the currency to see the price for your country.

A team where three people handle requests and thirty submit them pays for three, which is usually where these tools fit best. A team where everyone works tickets pays for everyone.

What about SharePoint?

If your company already pays for Microsoft 365, a SharePoint or Microsoft Lists list with the six fields above is a fair first version, because nobody has to learn a new login. Check which features your plan includes before you plan around them. The limit is that complex rules, such as "a customer sees only their own tickets", are hard to build there.

A cost example for a small team (made-up headcount)

Say four people work tickets and thirty submit them. On Jira Service Management Standard that is 4 x $21.50 = $86 a month. On Freshdesk Growth billed annually it is 4 x $19 = $76 a month. The free Jira plan stops at 3 agents, so the fourth person pushes you to a paid plan. That cliff is worth knowing before you pick a tool: with 3 or fewer agents, a free plan may be all you need, and at 4 you start paying for everyone.

The cost that does not show on the pricing page is your time. A subscription still needs someone to set up request types, statuses and who gets notified. Plan a day or two for that, even with templates.

A rule for choosing

  • 3 or fewer agents, plain requests, email in and out: use a free plan or the shared list.
  • 4 to 10 agents, response-time promises to customers (SLAs), several channels: a subscription at the middle tier.
  • Customers must see only their own tickets inside your own system, or tickets must tie to your job and customer records: build custom.

The no-code route

A no-code builder lets you design screens by dragging pieces over your data. Glide, one such tool, says in its documentation that you can sync from Airtable, Sheets, Excel or use its own editor. That works well for an internal-only system with simple screens: a form to submit, a list of "my tickets", and a manager view. Read building an internal tool without a developer and building a simple internal dashboard without a developer for the details of this route.

The custom route

A custom ticketing system is a small web app with its own database. It makes sense when you need things a ready-made tool will not give you: for example, tickets linked to your own customer and job records, or customers who see only their own requests. Supabase's documentation describes row level security, where the database itself decides which rows each signed-in user may see. That is the safe way to do "customers see only their own tickets". The data model above is the whole design, which is why the build can be small. See internal tools for how I think about this class of software.

Where tickets come from

Requests arrive by form, email and phone. The form is easy. Email and phone are where tickets get lost, so connect them. For phone, see how to create support tickets automatically from phone calls. For email, forward a shared address into the system so each message becomes a ticket.

Worked example (made-up figures)

A 20-person property maintenance firm. Requests come from tenants by phone and email, about 25 a week. Two coordinators assign work to six technicians.

  • Week 1: a shared list with the six fields and four statuses, plus a web form. No cost.
  • Week 4: the weekly report shows 9 tickets untouched for over 7 days, all in "Waiting on someone", all waiting for parts. The fix is a supplier process, not software.
  • Month 3: tenants ask for status updates by phone, eating coordinator time. Now a portal where tenants see their own tickets starts to pay back, and the team compares a helpdesk subscription with a small custom app.

Rolling it out to the team

A ticketing system only works if people use it on day one. Pick a start date and tell the team that from that date, requests that are not in the system do not get worked. Run a ten minute walkthrough: how to submit, how to find your tickets, how to change a status. Name one person as the system owner, who cleans up the categories each month and chases tickets with no owner. For the first two weeks, review the list together in a short stand-up so people see that tickets are read, not just filed. After a month, drop any field nobody fills in.

Common mistakes

  • Too many fields. People skip them and the data becomes useless.
  • Group owners. Every ticket needs one name on it.
  • No "waiting" status, so stuck tickets look like slow ones.
  • Letting some requests bypass the system "just this once". Within a month it is back to email.
  • Choosing a tool before choosing the rules.

Build or buy

If your needs are plain support requests and fewer than five people work tickets, a subscription is usually cheaper than building. If tickets must tie into your own data, or you would pay per seat for many people, building starts to win. I cover the decision in build versus buy.

How I'd approach this

I would run the shared-list version for three weeks before buying or building anything. It is boring, and it shows you the real shape of your requests: which categories repeat, who gets overloaded, where tickets stall. Most teams learn that their problem is ownership, not software.

After that, decide with evidence. If the same two or three kinds of ticket make up most of the list, automate those first, for example by creating the ticket from the phone call or the email so nobody retypes it. If customers need to log in and see their own requests, I would build it custom with proper access rules in the database. If it is only your own team and a handful of agents, a subscription is fine. Keep the six fields and the four statuses whatever you choose, so you can move later without losing your history.

Questions people ask

Can I build a ticketing system in SharePoint?

Yes, a SharePoint or Microsoft Lists list with fields for title, details, requester, owner, status and dates works as a basic version, and it needs no new login if you already use Microsoft 365. Check which features your plan includes. It gets hard once you need rules such as customers seeing only their own tickets.

What fields does a simple ticketing system need?

Six: title, details, requester, one named owner, status and dates. Add category and a two-level priority later if you will use them. Every extra field is one more thing people skip.

How much does a ticketing system cost?

A shared list is free. Helpdesk subscriptions charge per agent per month. As of November 2026 Jira Service Management is free for 3 agents and $21.50 per agent per month on Standard, and Freshdesk is $19 per agent per month on Growth billed annually. A custom build costs a one-off amount plus hosting. The build versus buy guide explains how to compare them.

Do I need a ticketing system for a team of 10?

You need the habit more than the software: one place for requests, one owner each, a clear status. At 10 people a shared list does the job. Move to a tool when requests come from many channels or customers want to see their own status.

How do I turn phone calls and emails into tickets?

Forward a shared email address into the system so each message becomes a ticket, and use a phone assistant or a form for calls. The steps are in creating support tickets automatically from phone calls.

More in this topic: Problem solving: custom software (22 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…