Now, working in both a development and support function, I can appreciate that everyone is busy and that trying to debug faults in my application isn't the job of support. However, I do get a little tired of the support process going like this:
But it's the next request that often follows - "Please supply example project" that is sometimes irksome. It's going to take me several hours to try and and build a sample standalone project and at the end of that, it's not guaranteed I'll be able to reproduce the fault. It could be that it only happens in a very specific situation that a sample project can never reproduce. I once had to resort to sending you a complete VM so you could see the fault as when stripped down to basics, it didn't happen. It turned out in that case to be a localisation bug.
In situations like this, it would be preferable to discuss the problem conceptually with the developer. Wearing my development hat, the support people here often go "Can you think of any reason why XYZ should happen?". As I know the code and they don't, it's often very easy for me to glance down the code and go "Ahh, yes - that could happen if XYZ".
So the plea is to not always bounce the support call straight back at me. I'm not in the habit of making up issues just for the hell of it :-)
Cheers, Rob,
PS. The DELETE key doesn't work in this editor. Backspace is fine.
I should mention that I'm a priority support customer too - but I wouldn't recommend it as it doesn't make the slightest bit of difference for reporting bugs (which is all I use support for). It does provide access to "live chat" but all they do here is file a request with the contents of the chat, and it gets dealt with in the usual way! There's also telephone support but I find technical issues are best written down.
> Another sign of an out-sourced support function where one of the metrics is getting jobs signed off ASAP.
I've had the same thought before. I had a request which had an associated development issue, and I prefer to keep these open until the development issue has been fixed so that the request doesn't get lost among my collection of closed ones. However, the support engineer insisted that the request should be closed since their job was done (even though from my point of view the request was far from complete). Eventually they had the cheek tell me they would be closing it, and promptly did so! I wondered if this engineer had a target to meet.
There's a noticable lack of recent replies from Infragistics on this thread. Where are you?
ustesgreenridge said: I hate to get the run around when trying to solve a problem. Tell you the truth, I hate using the support all together.
I hate to get the run around when trying to solve a problem. Tell you the truth, I hate using the support all together.
Things like this annoy as well:
Hello,
Hope you are doing well. (what?? you want to know about the pain in my neck?) I was wondering if you need further assistance on this case. We have not heard back from your side for the last three days.
So how come we have to wait months for a resolution but you expect us to respond to your messages within 3 days? Another sign of an out-sourced support function where one of the metrics is getting jobs signed off ASAP.
Cheers, Rob.
I am so in agreement with Rob!! As a priority spport customer, I hate to get the run around when trying to solve a problem. Tell you the truth, I hate using the support all together. The reason we call tech support is cause we have an issue implementing your tool with our existing app, not a skeleton app. To date, I think tech spt has helped me resolve just one of my issues (it was really a hack, hard coded the spell checker id). I would never recommend this suite just becasue of the support. I currently have an issue, lets see how this gets resolved...I swear I want a refund sometimes!!!!
> Come on - not supporting PNG!
Yep, but zip files are fine so zip the PNG and it will get through (but none of this is documented or reported in any error messages).
> over 763 users joined in the last week
I think you've hit the nail on the head there. It seems to me that they've grown too big to cope, which has led to poor support, and so many bugs being introduced as they hack in random features requested by their ever-increasing customer base. They really need to stop and think about the effect this is having on their existing, long-term customers, and how all these features affect the performance of their flagship products such as the grid.
Cheers,Jon
jsenior said: > So did I. Let's hope they read them.
> So did I. Let's hope they read them.
According to this forum, over 763 users joined in the last week. I can't believe there isn' t more pressure to improve support & quality.