| Well, Customer Support, which I build software for, for a start. Existing bots are pretty good at answering simple informational queries. But the business has to do a lot of configuration work to make that happen, and that's a big ask. Just the tech getting good enough to understand dialog more reliably, summarize, rephrase, ask for clarification, is a big deal. Something like this or lambda configured for a particular business would likely handle a much larger percentage of their volume. This is a big industry if you include phone, email, chat, all of which will eventually get bots; typically a single digit percentage of the workforce works in contact centers, stats like 4%. It also seems like software development will be changed a lot. Here's a related thought: how would you optimize your software stack to make it really easy for a tool like this to assist in? Lots of dense self contained modules that can fit in token window, to maximize the systems ability to reason about them and alter them?
Would that be worth it? |
At <our company> we do <thing we do>. We are going to provide all of our documentation, then at the end, marked by the separator "===" on a line, we'll provide a customer question or problem. Provide an example of a helpful response a customer service representative might provide that customer with.
... <all company documentation> ...
===
Customer: Where do I find the X capability in Y?