
I'm a Data Analyst at a medium-sized online store, and I mostly handle customer feedback from support tickets, surveys, and what people say about our stuff. Before Azure OpenAI, doing this was a real pain. I had to open tons of tickets in Zendesk, copy and paste everything into Excel, and try to sort things out myself. It would take forever, and I'd often miss stuff.
What I really like about Azure OpenAI is that it sorts all this messy text into something I can use automatically. Every Monday, I grab the last week's support tickets (usually like 500–600 chats) and run them through a gpt-4o-mini thing that our IT folks set up for me. I send each ticket to the system with a simple instruction: Put this ticket into one of these groups: Billing, Shipping, Product Quality, Returns, or Other. Also, figure out if the customer is happy, okay, or mad, and write a quick summary of the problem.
The result is a nice, clean file that I can just drop into Power BI. What used to take me 6–8 hours every Monday now takes about 20 minutes. I didn't even need to learn fancy coding — our team made this easy thing that connects Zendesk to Azure OpenAI and puts the results in a SharePoint list. I just open the list, hit refresh on my Power BI thing, and my report is ready for the meeting at 10 AM. It actually works with other Azure stuff; I don't have to be a tech expert to get something out of it. Review collected by and hosted on G2.com.
I'm a business user, not a techie, so my issues are all about using this stuff every day.
First off, the rate limiting is a pain in the neck. We have 120,000 TPM (tokens per minute) for our gpt-4o-mini, which sounds like plenty. But when you're dealing with 500 tickets, and each has 800–1,500 words, you hit that limit fast. Then you get those 429 errors (Rate limit exceeded). When that happens, my Power Automate thing just stops working. I've got to wait a minute and start it up again myself. IT said I could do some kind of batching thing, but that's way too complicated for me. I just want it to work without getting into all that technical stuff.
Second, the outputs are all over the place. Even with the temperature set to zero, the same ticket might be called Shipping one week and Delivery the next, even though I said Shipping is the right one. It makes it hard to track trends over time. Someone on Gartner Peer Insights nailed it, saying it has inconsistent behavior even with specific instructions and low temperature. Couldn't agree more.
Third, it's hard to know how much this all costs if you're not a tech person. I don't see the Azure cost stuff; IT just tells me we're spending too much. I have no idea how many tokens I'm using for my weekly summaries, or if I could save money by using shorter tickets. There's no easy way for regular users to see how much they're using. I feel like I'm using this really powerful thing without knowing how much it's costing me. Review collected by and hosted on G2.com.



