Case study · Ice-cream manufacturer · August 31, 2026

A back-office request at 2 p.m.,
in use before 4

An ice-cream manufacturer was trialling our LINE AI customer service. Their contact person looked at the back office and asked a few questions in our LINE group. Three of them needed code changes: raised at 2:21 p.m., and at 4:01 p.m. we replied that they were live.

See the timeline Contact us
Timeline, August 31, 2026 Drawn to scale in minutes: 14:21 the client asks the first question, 14:34 the last one, 15:39 we pick it up, 15:59 live, 16:01 we reply to the client. The client waited 1 hour 40 minutes; live 20 minutes after we picked it up. The client waited 1 hour 40 minutes Live in 20 min 14:21 The client asks the first question 14:21First question 14:34 Last question asked 14:34Last question 15:39 We pick it up and start 15:39We start work 15:59 Live 15:59Live 16:01 We reply to the client 16:01Reply to client Timeline, August 31, 2026 Drawn to scale in minutes: 14:21 the client asks the first question, 14:34 the last one, 15:39 we pick it up, 15:59 live, 16:01 we reply to the client. The client waited 1 hour 40 minutes; live 20 minutes after we picked it up. The client waited 1 h 40 min Live 20 min after pickup 14:21 The client asks the first question 14:21First question 14:34 Last question asked 14:34Last question 15:39 We pick it up and start 15:39We start work 15:59 Live 15:59Live 16:01 We reply to the client 16:01Reply to client
Dots are placed in proportion to the actual times; the minute-by-minute record is in the timeline below.
1 h 40 minFrom the client's first question (14:21) to our reply that it was live (16:01)
3 changesShipped in code: customers' LINE display names, a whole-week view, a list of customers to follow up
1 questionNeeded no code change — we replied explaining where to look

What the client asked

Their contact person asked four questions in a row in the group (paraphrased):

  • After the AI replies, could messages from customers who weren't handed to a person get buried and go unnoticed?
  • In the sales-leads section, customer names show up as a string of random characters. We'd like to see the customer's name.
  • We don't always open LINE at weekends. If we only check on Monday, do Saturday's and Sunday's numbers reset to zero?
  • If there are 10 customers with sales leads this week, does it record which 10 they are?

How we decided

  • Names as random characters: the back office only showed the last few characters of each customer's LINE account ID. We changed it to show the customer's LINE display name — and said up front that LINE only provides the display name, not the business name, and some customers' display names are nicknames or symbols.
  • Weekends resetting to zero: the data was all there; the screen only showed "today". We added period options such as the last 7 days, so the weekend is visible when they open it on Monday.
  • Which 10: every lead was recorded, but the screen rolled them up into a single number. We added a list of "customers to follow up".
  • Could messages go unnoticed: this one needed no code change. The back-office home page already lists every customer who has sent a message, with sales leads and complaints at the top; what the client had been shown earlier was the leads-only page. We explained where to look in our reply.

Timeline

August 31, 2026, Taiwan time

  1. The client asks the first question in the group
  2. The client asks the last question
  3. We reply in the group: request received, we'll make the changes
  4. The client's questions are passed to our internal channel; work starts
  5. We post explanations for all four questions in the group first
  6. Three features written: customers' LINE display names, period options, the list of customers to follow up
  7. Checking screenshots, we notice the default period had accidentally become "All"; corrected to the last 7 days
  8. Test demo accounts filtered out; real customers' conversations kept
  9. Live; screenshots of the live back office confirm all three are there
  10. We tell the client it's done, with screenshots

Times come from the LINE group's message history, the code change history and our internal tickets.

Afterwards

The manufacturer later signed a contract and rolled out LINE customer service and an ordering account. From October 9 to 30, 2026: 75 customers and 531 messages, 155 of them after hours (weekdays 6 p.m. to 9 a.m., and weekends). The AI sent 310 replies and handed over to a person 81 times.

How we counted: this is LINE customer service usage, not how often the back office was opened. Only one-to-one messages from customers count — not group chats — and the company's own staff and our own accounts are excluded. "Handed over to a person" is the number of times the AI decided to hand over, not the number of times staff actually replied. Records start on October 9, 2026. We counted the numbers two different ways and they match (Results page).

What we didn't get done that day

For the "could messages go unnoticed" question, what the client really wanted was this: when someone gets in touch, they find out without having to go and look. That's a notification, not a screen. On the day, we only explained where to look; notifications went out as LINE push messages at the time, and that month's quota was already used up — so that half wasn't solved that day.

More records of how fast we ship: see the development log (in Chinese). Common questions before getting started: ask these 10 first.

Got a small request of your own?

Tell us in one sentence what you need, and we'll build it on your own data for you to try. Message LINE @enscon, or email [email protected].

Contact us