What Is a Ticketing System? Tickets vs. Live Chat

Some customer requests can't be solved in a few minutes of chat: tracing a transaction, investigating a technical error, or a return that involves the warehouse. If those requests only live in a chat history, a few days later nobody remembers which ones were followed up. That's what a ticketing system is for.

This article explains what a ticket is, how it differs from live chat, how to prioritize tickets and where SLAs come in. At the end you'll see how a conversation becomes a ticket in Hodhod.

What is a ticketing system?

A ticketing system turns every customer request into a "ticket": a numbered record with a clear owner, a priority, a status and its full history. Instead of requests getting lost in an email inbox or a chat log, they all sit in one list, and you can see who owns each one and where it stands.

What makes up a ticket?

Number: a unique ID the customer and your team use to refer to the request.
Customer and history: who asked, and every message exchanged.
Owner: the agent or team responsible for following up.
Priority: how urgent it is.
Status: which stage the request is at.
Deadline (SLA): by when it must get a reply or be solved.

The ticket lifecycle

Most ticketing systems use stages like these:

Status	Meaning
Open	The request is logged and nobody has started on it yet
In progress	A teammate is working on it
Waiting on customer	The team needs information or confirmation from the customer
Resolved	The issue is fixed and a final answer was sent
Closed	The record is archived after resolution

Tickets vs. live chat

Aspect	Live chat	Ticket
Response time	Real time, within minutes	Asynchronous, hours to days
Best for	Quick, simple questions	Requests that need investigation or follow-up
Customer presence	Must stay on your site	Not needed — replies reach their email
Follow-up	Within the same chat	With a number, an owner and a deadline

They aren't competitors. The best teams start in chat and turn the conversation into a ticket when needed. Three good signs it's time to convert:

The answer needs more investigation or another team.
The customer can't or won't wait on your site.
The request must be tracked until it's solved, not just until the chat ends.

Prioritizing tickets

Not all tickets weigh the same. A common scheme:

Urgent: the customer is completely blocked or money is involved — a payment that went through but wasn't recorded, for example.
High: a serious problem with a temporary workaround.
Medium: a question or issue with no special rush.
Low: suggestions, feature requests or general questions.

Write your priority rules down and train the team on them. If everyone prioritizes by gut feeling, the list slowly fills with "urgent" and priority stops meaning anything.

What is an SLA?

An SLA (service level agreement) is your commitment on response times. In support, three numbers usually matter:

First response time: from when the request is logged to the first human reply.
Next response time: after each new customer message, until the team's next reply.
Resolution time: from when the request is logged until it's fully solved.

A starting point (tune the numbers to your team's capacity):

Priority	First response	Resolution
Urgent	1 hour	8 hours
High	4 hours	1 business day
Medium	1 business day	3 business days
Low	2 business days	1 week

If your team isn't available around the clock, count SLAs during business hours only — otherwise every ticket logged on Friday night is already overdue on Monday morning.

Best practices for ticket follow-up

Give every ticket one owner. A ticket that belongs to everyone belongs to no one.
Tell the customer what's happening. Even without a final answer, a short update ("we're checking with our finance team") builds trust.
Write canned replies for frequent requests, so answers stay fast and consistent.
Review the SLA report weekly. If one type of ticket keeps missing its deadline, the problem is the process, not the agent.
Make sure it's really solved before closing. Closing too early only creates duplicate tickets.

Tickets in Hodhod

In Hodhod, chat and tickets live in one panel:

Convert a conversation to a ticket: open the ⋮ menu at the top of the conversation and choose "Convert to Ticket". If the customer has no email on file, Hodhod asks for it.
Email follow-up: once converted, your team's replies are also emailed to the customer, so the follow-up continues even after they leave your site.
Ticket list: every ticket gets its own number and shows up on the "Tickets" page with its status, priority, owner and SLA status; you can change the status right from the list and filter by status or priority.
Priority: set it from the conversation sidebar, or automatically with Automation rules.
SLAs: create an SLA policy under Settings → SLA (first response, next response and resolution times, with an "Only during business hours" option) and apply it to the conversations you choose with the "Add SLA" action in an automation rule. SLA reporting lives under Reports.

To see this flow on your own work, request a free demo.

Frequently asked questions

Do small teams need a ticketing system?

As soon as you have requests that can't be solved in the same conversation, yes. Even with two agents, it's hard to know what was followed up and what slipped through without tickets.

How is an SLA different from a "typical response time"?

A typical response time is what happens; an SLA is what you've committed to. An SLA has a specific deadline, and the system shows which requests are close to it or past it.

Does the customer need an email address to convert a chat into a ticket?

In Hodhod, yes — ticket follow-up continues by email. If the customer's email isn't on file, you're asked for it during conversion.