this post was submitted on 11 Jul 2023
65 points (95.8% liked)

Technology

59308 readers
5201 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
 

Dukaan founder and CEO Suumit Shah revealed that 90% of the company’s support staff has been laid off after the introduction of an AI chatbot to answer customer support queries.

you are viewing a single comment's thread
view the rest of the comments
[–] june@lemmy.world 28 points 1 year ago (7 children)

The big problem with wanting to use AI (which generally means LLM these days) is that it lacks real creativity. If a problem isn’t documented, the AI won’t know what to do about a particularly difficult support request, or it will give wrong answers all together. My time in CS for tech taught me that the number of novel resolutions is far, far greater than most people realize.

[–] James@lemmy.ca 16 points 1 year ago (1 children)

That’s all tier 1 help desk ever does anyway.

From my experience they know less about the product than I do when I try to get support on it.

[–] Pika@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

it's so true... I feel bad due to it but, half the time t1 is just rehashing the power cycle and try again list.

[–] jsveiga@sh.itjust.works 9 points 1 year ago

Yes, but for all the common issues, for which there's a script that 1st level will have to follow anyway, AI can do it. If it forwards to a human when it gets to a dead end - and snoops the conversation to learn from it - then less humans are employed.

Some years ago I opened an issue with Google Pay through the app feedback option.

A CS messaged me in less than 5 minutes. She was so thorough and her texts looked so scripted, that I had to ask "I apologize in advance, but... are you a bot or a human?", because I could be much more concise and less patient in my answers if it was a bot. She solved my issue very efficiently btw, and though it was quite funny that I asked.

[–] Hypersapien@lemmy.world 7 points 1 year ago

First level support staff generally aren't allowed to have creativity. They just follow the script and then pass the problem up when it's something they can't handle.

[–] Phyrin@lemmy.world 3 points 1 year ago

I would agree, this was my first thought.

Though if the product is sufficiently defined, and bounded, it might make sense. Think support line for a fridge, oven, or other less-open products. Unbounded spaces like general purpose computer support will initially struggle while documentation is built up.

[–] bill_1992@lemmy.world 3 points 1 year ago (2 children)

Wouldn't any automated system ideally escalate to the next tier of (human) support when it detects something complicated?

Though I agree with you, I don't think LLMs are lay-off 90% good.

[–] balder1991@lemmy.world 8 points 1 year ago

Wouldn’t any automated system ideally escalate to the next tier of (human) support when it detects something complicated?

In my experience, this never happens. Since they have now very few human staff they make it VERY difficult to talk to a human to the point you often give up.

[–] LordOfTheChia@lemmy.world 2 points 1 year ago

system ideally escalate to the next tier of (human) support when it detects something complicated?

Why escalate when you can hallucinate!

[–] swrdghcnqstdr@lemmy.ml 2 points 1 year ago

often times it will get actual documented solutions wrong too. this is an example of the same type of concept implemented in the MDN

[–] swrdghcnqstdr@lemmy.ml 2 points 1 year ago

often times it will get actual documented solutions wrong too. this is an example of the same type of concept implemented in the MDN