Skip to main content
GullySystem

Helpdesk Software for Tickets and Service Calls

Helpdesk software turns calls, WhatsApp messages and email into numbered tickets, each with an owner and a promised time. Four modules cover tickets, customer support, automation and a knowledge base.

How complaints go missing

The same complaint can arrive on WhatsApp, the landline and email. Without one queue, it is told to a technician on the road, answered by whoever holds the password, or fixed without the customer hearing.

  • A promise made on a call that nobody else heard
  • Two people working one complaint without knowing
  • A ticket closed while the customer still waits
  • A repeat complaint with no earlier history attached

The four parts of the helpdesk

The ticket is the core. The other three modules attach to it.

Ticket management

Each complaint gets one number, with an owner, a priority and the promised time. A ticket closes when the customer confirms it.

Customer support

Phone, WhatsApp, email, the website form and social messages feed a single queue, with the customer’s history alongside.

Helpdesk automation

Your own rules run without anyone in the middle. They cover assignment by area, escalation by time, acknowledgements and reminders.

Knowledge base

Answers your senior technician gives are written down and searchable. Customers use them out of hours, and new joiners read them before a first call.

Promised times and escalation

A promised time is useful only if the office learns of a breach before the customer does. Set the working hours and priorities you really use, and tickets surface while there is time to act.

  • Working hours and holidays counted against the clock
  • Escalation to a named person, not to a group
  • Parts used and site photographs stored on the ticket
  • Reopened tickets counted apart from new ones

When a small desk may not need one

Two people handling a handful of complaints a day can hold them in their heads. A helpdesk earns its place once volume passes what one person remembers, or customers start quoting dates back. The second reason is the better one.

One complaint from first call to closure

The helpdesk records each hand-off along the way. Follow a water purifier that stopped working, to see who touches the ticket and when. It is an everyday case, and a common one.

The customer’s first message

A customer sends a WhatsApp message about a purifier that stopped working. The message becomes ticket number 1043, with a promised time. Back comes the number to the customer. A reference to quote later is now in hand.

The coordinator assigns a technician

A coordinator sees the new ticket and checks the warranty on the record. A technician is named and the visit slot is added. The customer is told the day. Nobody has to ring round to find who is free.

The visit and the parts

At the house, the technician adds the parts used and photographs the old unit. These are saved to the ticket. If a spare is missing, the ticket shows the pending item rather than going silent.

Closing with the customer’s word

After the repair, the customer confirms it works. Only then is the ticket closed. A repeat call a week later reopens the same ticket, so the earlier history is in front of whoever answers the phone that day.

Settings to agree before the first ticket is raised

A helpdesk behaves the way the firm sets it. A few choices come first and shape every ticket afterwards. Settling them avoids the habit of closing complaints that customers still consider open. They take one meeting, no more than that.

What counts as one ticket

Decide whether a second problem from the same customer opens a new ticket or joins the first. The rule keeps counts honest. Staff follow it without debate when a call becomes complicated, and reports then compare like with like.

Who owns which kind of complaint

List the complaint types the firm handles and name the person or team for each. Billing questions go to accounts, while faults go to service. A misrouted ticket can still be moved. A note explains why it was moved.

What the promised times are

Set the time within which each type of complaint is acknowledged and resolved. Working hours and holidays are counted against the clock. Customers see the promise in the first reply. Staff therefore do not invent their own versions of it.

Who may close a ticket

Choose whether the agent who handled the ticket may close it or whether the customer’s confirmation is needed. Reopening is allowed. The record shows both events side by side, so any dispute about a closure can be checked quickly.

The first month of a service helpdesk

Start with a small slice. Customers and product models go in first, then a few complaint types, then the rest. Staff learn on real tickets with the old register still open, so a gap in the new setup never leaves a complaint unrecorded.

Customers and models loaded first

A ticket needs a customer record. Load the customer list, the addresses and the product models sold, with purchase dates for warranty checks. Messy old entries are fixed here, once, instead of by every agent on every call.

A few complaint types to begin

Begin with the complaints you hear every week. Give each an owner. Rare types go under one heading for now and are split later, once the first month’s tickets show which ones deserve their own owner.

Rules adjusted from real tickets

Some were needed. Others fired because a promised time was set too tight or an area had no named owner. Each rule change is noted with a date.

Make an informed decision

Agree the evidence before signing off this part.

Use a representative scenario to decide what this part of the system must show and where review is still needed.

The four parts of the helpdesk

What happens between reporting a fault and accepting the fix?

For “The four parts of the helpdesk”, walk through a fault reported outside normal hours. Agree the first responder, escalation path and evidence needed to close the incident, including what falls outside the support arrangement.

Background reading: ERPNext: support settings

FAQ

Frequently asked questions

Can customers raise a ticket on WhatsApp?

Yes. A message to your business number opens or updates a ticket, and the reply goes back on that same thread. Customers who prefer to ring still get a ticket, raised by whoever picks up the phone.

Does the helpdesk suit field complaints, not just email?

Yes. A technician opens the ticket on a phone at the site, records the parts used and attaches a photograph before closing. The customer confirms on WhatsApp.

What is the difference between ticket management and customer support?

Ticket management carries the job: number, owner, promised time and closure. Customer support carries the conversation across channels, so a customer who wrote on Instagram and then called is one person, not two.

Will a knowledge base bring our call volume down?

It can reduce repeated questions, not real complaints. Articles are worth writing for what the team answers every week, and worth skipping where a visit is needed anyway. No figure is promised.

Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements