One group chat per client: how B2B teams track every request without the client seeing a ticket

A client writes in your shared WhatsApp group that the invoice bills 500 boxes when 450 arrived. Everyone saw it. Nobody owned it. Three weeks later they ask where the credit note is.

You can keep the group and still know who owns each request and how long it took, and the client never sees a ticket. Below: which messages need one, and how to time a chat that never ends.

A Tuesday in a client group

Kestrel Packaging supplies boxes and lids to bakeries and café chains. Every client has a WhatsApp or Telegram group with Kestrel's account manager, the warehouse lead and someone from billing.

On Tuesday the group "Kestrel x Bakehaus" gets 23 messages: pallet photos, a thumbs up, a question about Friday's delivery. One line from Bakehaus's finance manager says invoice 2291 bills 500 boxes when 450 arrived.

Nobody picked that line up. When Bakehaus asks 3 weeks later where the credit note is, nobody can say when the request came in or how long it sat.

Agencies, suppliers and software vendors with a few large accounts often work like this, because clients like it.

Why a group chat breaks the usual support numbers

Help desks measure work from when a ticket opens to when it is solved. Zendesk's help center, for example, defines full resolution time as the "duration between ticket creation and its most recent resolution". That works when one email thread is one request.

A client group never ends. If it started in March, its resolution time in October is 7 months, which says nothing about Tuesday's invoice. Mix a few of those into your averages and the number stops meaning anything.

Nobody owns what everyone sees

The second problem is ownership. Everyone sees everything, which feels like control until you have 15 groups.

Plain sells support software for teams that serve clients in shared Slack channels. It puts the limit at 10 to 20 channels without a common queue before messages start getting missed. That is a vendor's own estimate.

So cut the endless group into rounds that each have a start and an end. Pull the few messages that need real work out into tickets with an owner. The client keeps writing where they always have.

Which group messages deserve a ticket

Most of what happens in a client group is not a request. A ticket for every message buries the real ones a second time.

A message earns a ticket when at least one of these is true:

• Someone outside the group has to act, like the warehouse or billing.
• It cannot be finished while you are in the chat, because you wait for a carrier, a supplier or a fix.
• It holds a promise or a date, like "we'll send the credit note by Friday".
• The client may come back to it in a month: a complaint, a price change, a change to the contract.

Rounds: a resolution time for a chat that never ends

A round starts with the client's first message after you last closed things out. It ends when you resolve. Resolving is your bookkeeping; the client keeps writing in the same group.

How Deskwoot counts a round

In Deskwoot, a Telegram, LINE or WhatsApp group is one conversation that reopens whenever someone writes, however long ago it was resolved. Reports leave that conversation out of resolution time and give each filed round its own.

A filed round begins just before the client's first message of that round and ends at the resolve. So its resolution time is how long that one request took. When the client wrote nothing new since the last resolve, nothing is filed.

What Resolve asks you

With tickets switched on, Resolve asks how the chat ends:

• Without a ticket only resolves it.
• Keep as a resolved ticket files the round as a ticket that is resolved from the start, for your records and Reports. It notifies nobody.
• Create an open ticket for a team resolves the chat and leaves a ticket open for the team that still has work to do.

The arrow next to Send also offers Send and keep as a resolved ticket.

File every round, or decide each time

An inbox can file rounds for you. Switch on File every resolved interaction as a ticket in the Tickets card of the inbox's General tab.

Every resolve then files its round, whether a person, a macro, an automation rule, inactivity or the client ended it.

One side effect: a lone "thanks" after a resolve reopens the group and becomes a tiny round of its own. Where most messages are real work (orders, deliveries, invoices), accept that for complete data. In chatty groups, leave the switch off and pick Without a ticket for small talk.

Resolve by hand, with a timer as the safety net

Resolve by hand when the request is done, because that moment is what your resolution time measures.

As a safety net, give the inbox an auto resolve rule, say 2 days without activity. Set Skip when the customer is waiting for an agent reply to Yes, so a client message nobody answered is never closed by the timer.

The auto resolve message never goes into a group. A round closed by the timer does count those idle days in its resolution time.

A summary of each round

Summarize resolved conversations, under Settings > Conversation Workflows, has Copilot write a summary of each round into its filed ticket.

AI conversations count once per conversation per calendar month. So a month of summaries for one group is 1 of the 300 that Enterprise includes.

Pull the real work out into a ticket

For the invoice, the account manager makes a ticket straight from the group. Use Create ticket from this message next to the message, or Create ticket in the header.

1. Pick the messages the ticket is about, up to 500. Nothing is sent to the client.
2. Add a title, an internal summary, a category and the team or teammate who works on it.

Draft with Copilot writes the title and summary from the picked messages and nothing else, and you can change both.

Keep open work in sight

A private card in the group's conversation shows the ticket's number, title, status, team and assignee as it moves.

The group's Details tab lists its latest tickets, so whoever opens the group next sees what is still open.

Answer from the ticket

When billing has the answer, they use Reply to customer on the ticket. The reply goes out in the group, on the group's channel, as an ordinary message from your team.

Send and wait sets the ticket to Pending until someone in the group writes again. In a busy group that message may be about something else, so read it before you assume the client answered.

Which groups can come in

• On WhatsApp, Deskwoot handles groups created with Meta's Groups API on the WhatsApp Cloud API. Meta offers it to businesses with an Official Business Account and caps a group at 8 participants. Numbers on the WhatsApp Business app get no groups.
• WhatsApp groups are invite only: the client joins through an invite link your business sends (Meta Groups API).
• On LINE, your Official Account joins groups once you enable "Allow bot to join group chats" for your channel (LINE Developers).
• On Telegram you add your bot to the group. The Telegram setup guide covers the privacy setting that decides whether it reads every message.

Make each group the client's record

In Deskwoot each group is one contact of its own. On Telegram, each person who writes also gets a contact of their own. On LINE and WhatsApp, members become contacts when they also chat with you directly.

An organization ties these together. A direct message from Bakehaus's finance manager then shows up as Bakehaus, with a few colleagues listed next to the chat.

Two ways to make the organization

• Create organization from this group sits under the Organization field of the group's contact and of the conversation's Details tab. This button works at any time.
• Every group is an organization, under Group Chats in the General tab of a Telegram, LINE or WhatsApp inbox, does the same for each group the next time it writes.

Teammates who connected their Telegram under Settings > Notifications are left out, and so are blocked contacts. WhatsApp sends no group name, so the switch skips WhatsApp groups until you give the group's contact a name.

What goes into the notes

Then fill in the organization's Notes. The useful notes are the dull ones:

• who may approve costs
• who gets invoices
• what response time the contract promises
• what went wrong last quarter

When the account manager is on holiday, that page is the handover. The Organization section in each of the client's conversations links to it.

Why the satisfaction survey waits

Take the cracked lids. The account manager answers ("our quality team is on it, you'll hear from us by Thursday"), resolves the round and opens a ticket for quality.

A survey sent now would ask the client to rate a promise, and either score would be about the wrong thing.

Zendesk's advice on survey timing, on its blog, points the same way: when tickets are often reopened, "you might want to wait longer so your results aren't skewed by an irritated customer".

How Deskwoot times the survey

Deskwoot holds the survey while a ticket made from that round is still open. It sends the survey through the chat once the last of them is resolved.

Tickets never send a survey of their own, and a ticket left open from an earlier round does not hold up a later one.

Surveys in groups

In groups, only Telegram gets a survey at all, and only with Surveys in group chats switched on. CSAT comes with Business and Enterprise.

The group then gets one survey message, and each person who wrote since the last resolve can rate once. LINE and WhatsApp groups get no survey, so ask those clients on your regular account call.

A weekly review built on rounds

Once rounds are filed, Monday has real numbers. In Reports, set the type in the filter row to Tickets and the period to Last 7 days.

1. Click the Resolution time number and sort the list behind it by Longest resolution first. Each row names the contact, which for a round is the group, and shows how long it took. Open the 5 slowest and ask what they waited on.
2. Check Backlog right now for what is still open or pending, by age. Anything older than your contract promises goes to the top of the week.
3. Count rounds per client. Export the tickets as CSV; the Contact Name column holds the group's name, so a pivot table shows who sent the most requests. A client who causes 3 times the work of the others deserves a talk about the price of the contract.
4. Update the organization's notes with anything new: a person on the client's side, a changed delivery address, a promise you made.

The guide to the lists behind a number covers sorting and downloads.

What it takes in Deskwoot

Tickets, filed rounds and open tickets for a team come with Enterprise, at $12 per agent a month or $9.60 billed annually. Organizations and the Telegram, LINE and WhatsApp channels are not limited to Enterprise.

You can check every step before you sign up: Resolve a chat with or without a ticket, Create a ticket from a chat and Organizations. The overview is on the ticket system page, and plans are on the pricing page.

A first week with one group

Start with the client group that gave you the most trouble last month. Make it an organization, write 5 lines of notes, file its rounds for a week, then look at the slowest one.

After that week you know when each of that client's requests came in and how long it sat, and the client never left the group.

Every new workspace starts with 7 days of Enterprise free, without a card, for up to 30 seats including yours. When the trial ends, the workspace stays on the free Hacker plan unless you pick a paid one. Create your workspace and connect that one group first.