←back to thread

418 points speckx | 5 comments | | HN request time: 0s | source
Show context
jawns ◴[] No.44974805[source]
Full disclosure: I'm currently in a leadership role on an AI engineering team, so it's in my best interest for AI to be perceived as driving value.

Here's a relatively straightforward application of AI that is set to save my company millions of dollars annually.

We operate large call centers, and agents were previously spending 3-5 minutes after each call writing manual summaries of the calls.

We recently switched to using AI to transcribe and write these summaries. Not only are the summaries better than those produced by our human agents, they also free up the human agents to do higher-value work.

It's not sexy. It's not going to replace anyone's job. But it's a huge, measurable efficiency gain.

replies(39): >>44974847 #>>44974853 #>>44974860 #>>44974865 #>>44974867 #>>44974868 #>>44974869 #>>44974874 #>>44974876 #>>44974877 #>>44974901 #>>44974905 #>>44974906 #>>44974907 #>>44974929 #>>44974933 #>>44974951 #>>44974977 #>>44974989 #>>44975016 #>>44975021 #>>44975040 #>>44975093 #>>44975126 #>>44975142 #>>44975193 #>>44975225 #>>44975251 #>>44975268 #>>44975271 #>>44975292 #>>44975458 #>>44975509 #>>44975544 #>>44975548 #>>44975622 #>>44975923 #>>44976668 #>>44977281 #
dsr_ ◴[] No.44974877[source]
Pro-tip: don't write the summary at all until you need it for evidence. Store the call audio at 24Kb/s Opus - that's 180KB per minute. After a year or whatever, delete the oldest audio.

There, I've saved you more millions.

replies(10): >>44974925 #>>44975015 #>>44975017 #>>44975057 #>>44975100 #>>44975212 #>>44975220 #>>44975321 #>>44975382 #>>44975421 #
alooPotato ◴[] No.44975057[source]
you want to be able to search over summaries so you need to generate them right away
replies(2): >>44975113 #>>44975296 #
krainboltgreene ◴[] No.44975113[source]
Pro-tip: You won't ever do that.
replies(3): >>44975139 #>>44975210 #>>44975232 #
1. ch4s3 ◴[] No.44975232[source]
I would imagine OP is probably mining service call summaries to find common service issues, or at least that's what I would do.
replies(1): >>44976357 #
2. krainboltgreene ◴[] No.44976357[source]
That's what everyone says they'll do and then it never gets touched again.
replies(1): >>44977034 #
3. ch4s3 ◴[] No.44977034[source]
I guess you just know better than everyone, include the people who do look at user interactions. I know I've done it, so I must be no one.
replies(1): >>44977638 #
4. morkalork ◴[] No.44977638{3}[source]
I guess I'm no one too because I've done plenty of call analyses too.
replies(1): >>44980581 #
5. ch4s3 ◴[] No.44980581{4}[source]
We should start a company!