When a WhatsApp chat should become a ticket

Most of the time, a WhatsApp conversation is just that: a question, an answer, a thank-you. But now and then a customer brings a problem that three messages can't fix. A delivery that never arrived, a double charge, a service that needs a technician visit. The issue runs for days, passes through more than one person, and the chat turns into a river of messages where nobody can find the thread.

That's where a ticket helps. This article shows how to decide when to open one, what it needs, and how to keep it from turning into red tape.

A chat is not a ticket

The most common mistake is opening a ticket for everything. The team spends more time filling in fields than helping, and the customer who only wanted the opening hours gets a case number.

A conversation can stay a conversation when:

• the question is answered on the spot;
• it doesn't depend on anyone outside the chat;
• there's no deadline;
• nobody will need to look the case up later.

Signs it's time for a ticket

The issue won't be solved today. If it will run overnight or over a weekend, it needs a record beyond the chat.

It depends on another person or team. Billing, technical, logistics, a supplier. When the case leaves the hands of whoever received it, someone has to stay accountable.

It has a deadline, stated or implied. The customer said "I need it by Friday", or it's the kind of problem that gets worse the longer it waits.

The customer has come back more than once for the same thing. That's a sign the conversation alone isn't holding up.

You need to measure. If you want to know how many delivery problems happened this month, or how long they take to fix, loose chats won't tell you.

A practical rule: if someone on the team thinks "somebody will have to follow up on this later", open the ticket.

What every ticket needs

A number

The number lets you talk about a case without retelling the story. The customer says "my request 1042" and anyone on the team finds it. It also gives you a reference for emails and internal notices.

A subject and a description

The subject is one sentence: "Order 5531 didn't arrive". The description says what's known. Whoever opens the ticket tomorrow should understand the case without reading the whole chat.

An owner

One person, by name. A ticket without an owner is a ticket nobody sees. If the case moves to another team, the owner changes with it, and the history shows the handoff.

A category

Few of them, so they don't become decoration. Three go a long way: question, problem and request. As volume grows, split by real topic: delivery, billing, warranty. A category lets you look at the whole and see where service struggles most.

A priority

Low, normal, high and urgent. Define what each means in practice. Urgent is "the customer is stuck", not "the customer is angry".

A deadline

Really two: when to reply first and when to resolve. The reply deadline is a promise of attention. The resolution deadline is an honest target that depends on the kind of problem.

Deadlines should follow business hours. A ticket opened at 6:50 p.m. can't be late at 7:00 p.m.

A status

Few and clear: new, in progress, waiting on customer, waiting on a third party, resolved, closed. The two "waiting" statuses matter: when the ball is with the customer or a supplier, the deadline clock shouldn't run against your team.

Keeping the customer informed

The ticket is internal, but the customer needs to feel someone is on the case. Three messages are enough:

1. On opening: "We received your request. Your case number is 1042."
2. When information is missing: ask for what's needed, citing the number.
3. On resolution: say the case is done, again with the number.

What stays out of those messages matters just as much. The internal subject and the team's notes never go to the customer. "Customer complained three times, watch your tone" is for the team.

How the team follows up

A ticket only works if the team looks at it every day. Four views help:

• Mine: what's with me.
• My team's: what's with my department.
• Unassigned: what needs an owner today.
• Due soon: what's close to its deadline or already past it.

Once a week, look at the numbers: how many tickets are open, how many are late, how long first replies take, how long resolution takes and which category holds the most cases. That's how a recurring problem shows up before it becomes a crisis.

Simple rules

• A chat that's solved on the spot stays a chat.
• If someone needs to follow up later, it's a ticket.
• Every ticket has an owner and a deadline.
• The customer gets the number at the start and a notice at the end.
• Internal notes stay internal.
• Resolved tickets get closed, so the board shows only what matters.

How to do this in IntegraWhats

The Tickets app in IntegraWhats is part of the Pro and Business plans. You open a ticket from the chat, or directly, with a subject, description, contact, category, department, owner and priority. Each ticket gets a number and keeps its history: status and owner changes, internal notes, replies to the customer, pinned messages, attachments and linked conversations.

First-response and resolution deadlines are set per priority, in minutes, and counted within the channel's business hours. They apply to new tickets and can be edited in settings. When a deadline gets close or passes, the ticket shows the warning and the team is notified by email. While a ticket is waiting on the customer or a third party, the resolution deadline is paused. There are editable categories, customer notices that include the case number, list or kanban views, and a metrics screen with CSV export.

Frequently asked questions

Does every customer need a case number?

No. The number only helps when there's a case to track. Sending a case number to someone who asked about opening hours is red tape that pushes people away. Use it when the issue will last.

How many categories should I create?

Start with three or four and let use show what's missing. Too many categories get in the way: the team picks any one just to move on, and the data that comes out loses its value.

How long should I promise for the first reply?

What your team can meet consistently. It's better to promise a longer time and keep it than to promise fast and run late. Start from your real history and tighten over time.

Does the customer need to know we opened a ticket?

They need to know the case was logged and what its number is. The word "ticket" is optional. Many companies say "request" or "case number" and it works the same.