3 ms·
I don't understand your comparisons. > So its like a API but less reliable and harder to use Regular customers can't interface with an API, so that's not an a
by crazygringo 3y ago
I don't understand your comparisons.
> So its like a API but less reliable and harder to use
Regular customers can't interface with an API, so that's not an apt comparison. A lot of people call customer service or use chat for things they can't or don't want to figure out how to do on the website.
> Also much more expensive.
It isn't more expensive -- the whole point is that it's cheaper than paying customer service reps.
- willcipriano 3y agoIt works like this, they have an API, say: /refund/<order id> It has all business rules encoded into it, so the API decides with regular code if you are getting a refund or not. Instead of: <button onclick="/refund/<order_id>"> Just being added to the orders page, you have to convince ChatGPT to call the refund API for you by writing it a story. Worse UX, more expensive.
- crazygringo 3y agoAllow me to repeat my comment: > A lot of people call customer service or use chat for things they can't or don't want to figure out how to do on the website. It's not inherently worse UX, it's multiple ways of interacting for different customers who have different preferences. And when you say "It has all business rules encoded into it", that's literally what I already said twice -- "hard business logic guardrails in actual code, not in the LLM".