Q: 2
You have a product support manual. You need to build a product support chatbot based on the manual. The solution must minimize development effort and costs. What should you use?
Options
Discussion
B Had something like this in a mock and B was the right pick.
Makes sense to go with B here. It's basically built for quick Q&A from docs, barely any effort to set up compared to fine-tuning or building an OpenAI+Search stack. Not totally ruling out C if you wanted more control, but for minimum dev and cost, B.
I don't think A is right for minimum effort since fine-tuning takes extra steps and cost, plus managing training data. B is designed for quick Q&A on docs, which matches the requirement. C might feel tempting if you like big LLMs, but that's more complex/expensive. Pretty sure it's B but happy to hear if I'm missing something.
A
I'd go for A since you can fine-tune Phi-3-medium with the manual content, so it should give relevant answers like a chatbot. To me, that seems like less coding compared to building a Q&A index first. Not sure if it's cheaper than B long-term, but for quick development, I think it works. Open to feedback if I'm missing something obvious!
I'd go for A since you can fine-tune Phi-3-medium with the manual content, so it should give relevant answers like a chatbot. To me, that seems like less coding compared to building a Q&A index first. Not sure if it's cheaper than B long-term, but for quick development, I think it works. Open to feedback if I'm missing something obvious!
B or D? B makes sense for quick Q&A on manuals, barely any dev needed. D is more about extracting info from docs, but not really a chatbot thing. Not 100% sure but I'm leaning B for simplicity. Anyone disagree?
D imo, B is tempting but Document Intelligence is a trap here since it's better for OCR, not chatbots.
Probably B for this one. Custom question answering is built exactly for turning manuals into chatbots with almost no dev work. The other options either need more setup or cost more in the long run, I think. If anyone's actually tried C in production for this use case, let me know, but I'm sticking with B.
It’s not A. B is the one made for quick Q&A directly on docs, so best fit if you want low effort.
I actually thought C since grounding GPT-4 with Azure Search feels like low code, but it's more involved (extra components and costs).
Its B
Be respectful. No spam.