WebAssist Support

[jeff150879]

I have been a loyal customer for years and own most of the WebAssist products. I am satisfied with most of them. But my post today is about my dissatisfaction with WebAssist support.

When I have a problem with a product, I need assistance today, not 2-3 days from now. I also can't afford to wait another 2-3 days after every response. If it takes 6 messages back and forth to resolve my issue, it may be two weeks or more. I don't have the luxury of that kind of time.

I opened a support ticket on 4/27/09, late in the day regarding problems with CSS Menu Writer 2. I received a response the next morning, which was OK, but basically it was a canned reply, which the technician spent no more than about 15 seconds telling me my problem is a known issue on pre-release versions of CS3. Well, I have the latest build of CS3 which I said in my immediate response. I'm going on 2 days waiting to hear back.

BTW, your sales department sent an email today wanting to sell me the "CSS Menus Starter Kit for Photoshop." The sales emails always get sent in a timely manner.

This kind of thing has been a chronic problem at WebAssist since I've been a customer. There are too little resources devoted to support for the folks who have already bought your products.

Support tickets should be answered same day if received before noon. If received after noon, they should be addressed before noon the next day. Follow-up responses should be answered within the same time frame. There should be a toll-free support number to call as well, that someone will actually answer. Online chat for support should also be available.

The new website is beautiful, and the sales & marketing emails are gorgeous too, but it's time for WebAssist to step up and start supporting their products like a real world-class software company.

I'd like to hear what others think on this issue and what the decision makers at WebAssist have to say about their "it takes forever" support practices.

[Ray Borduin]

I would be interested to hear other people's opinions of the support too.

We actualy spend a large percentage of our product sales price on support because of the complexity of our products and flexability of what they are capable of. We already put 100% of our profits back into the products and thier updtes and support, so we would have to raise or prices to afford more support, so it would be a risk, but if that is the overwhelming opinion we could try to put more resources into support.

I think most people feel that WebAssist goes above and beyond in their support, but you obviously have voiced a different opinion. I guess I'll wait and see who else chimes in.

[bobweber377579]

I agree the turnaround to questions is too long either with a support ticket or on this forum. I too feel that it can easily take a week of emails to solve a problem if at all. Or you after all the emails are told well there are limitations to in my case CSS Menu writer.
I am brand new customer with CSS Menu writer. I bought it because of "NO CSS experience required". I had two problems.
1. I wanted to have a link in nav bar to open in a new page. Well that required me to go into the code and change things and with my inexperience took time and emails back and forth. I think that should have been an option in the edit menu. I cant be the only person that wants that. But it was eventually resolved.
2. Some of my menu names were too long and caused the text to overlap the background. Again days of emails back and forth,and suggestions to go into the code again. I was nt able to understand the instructions so did not do that. Then I was given another suggestion did that but it still did not work more emails back and forth. Then I was told to just change the words on the links yes I could do that but then they are not understandable to what they are. So I was told that well there are limitations to CSS Menuwriter. Again I think other users have words for links that are longer then the space provided.
So thats my vent for the day

[Ray Borduin]

I'm not sure if this is really a complaint about support or the product. In this case no amount of support would really solve the problem.

Your problem boils down to the reality that in css menu writer you can only have one width per level in the menu. You can make it bigger, but if you have one menu item that is disproportionately larger than the rest it looks funny if you make them all that large.

You can do auto-widths in this scenario for the last menu level, but if you have sublevels it needs to place that sublevel based on the previous. In your case we tried to find a solution that would work for you but eventually ran into problems with limitations in what we expose and a css based menu implementation in general that prevented you from finding the solution you wanted.

Although you were not successful, in this case I think support did all they could in working with you. Maybe they should have given up earlier, but they made genuine attempts to find a solution that would work for you. This comment would actually tell me that we should put more resources into engineering and adding more features and not into support.

[Ian]

I've always found support pretty good to be fair - apart from one product which really should never have happened - its a disaster in my opinion and thats iRite.

If I've got any gripe its when I submit a support ticket the replies seem quite blunt and if they paid a bit more attention to the reply they could probably reduce the amount of replies they have to make!

[Ray Borduin]

When we update iRite next I think you may see the light. ;) It is a good product concept, but we did miss a few key features in v1.

I think if we fix those features, add a few more, and give it to you in context people will learn to love it. Don't give up on iRite too quick, it's going to make a comeback in the next year and it just might change your mind.

[jeff150879]

When we update iRite next I think you may see the light. ;) It is a good product concept, but we did miss a few key features in v1.

I think if we fix those features, add a few more, and give it to you in context people will learn to love it. Don't give up on iRite too quick, it's going to make a comeback in the next year and it just might change your mind.

I agree with Ian. I spent my money on iRite as well, and don't use it anymore. It's a very bad product. Someone recommended Advanced HTML Editor 2 by DMXZone to me awhile ago. I tried it and have been using it ever since. Far superior to iRite.

I hope when you guys release this next version of iRite, you will offer it as a free upgrade to those of us who wasted our money on version 1.

[jeff150879]

I would be interested to hear other people's opinions of the support too.

We actualy spend a large percentage of our product sales price on support because of the complexity of our products and flexability of what they are capable of. We already put 100% of our profits back into the products and thier updtes and support, so we would have to raise or prices to afford more support, so it would be a risk, but if that is the overwhelming opinion we could try to put more resources into support.

I think most people feel that WebAssist goes above and beyond in their support, but you obviously have voiced a different opinion. I guess I'll wait and see who else chimes in.

I wanted to post an update to my support ticket regarding CSS Menu Writer 2. Today I remembered a fix I needed to do for an issue I had long ago with an eCart upgrade. The issue was resolved by deleting the Dreamweaver WinFileCache file and re-starting Dreamweaver. I tried that today, and it solved my issue with Menu Writer.

This afternoon, after already fixing this issue myself, I finally heard back from tech support suggesting I try this very thing. Too bad it took support until Thursday afternoon to suggest this fix on an issue I submitted a ticket on last Monday.

Ray, your statement about having to raise prices in order to provide proper support is one I don't buy into. It's like having a company motto of "Quality, Service, Price...Pick one."

[Ray Borduin]

I understand your perspective, but that is not really what I am saying... I was trying to explain to you that Quality, Service, and Price are a balancing act. We are a small company, without public funding, without a government bailout and we put 100% of our profits back into updating the product, creating documentation, and support.

I know it is our burden to make these hard decisions, and I don't want to bore you with the details. I'm not saying pick one. I'm saying we already provide all three using 100% of our resources. If and when customers have issues we can either bolster the engineering so that the products are fixed and work better, bolster the documentation so that the customer can be successful on their own, or bolster the support. Unfortunately when you are using 100% of your resources, adding to one area necessarily means reducing another unless you are able to increase profit.

Of the three options engineering and documentation are usually where companies concentrate. The clear reason is that you fix it once and everybody can take advantage of it. I think Adobe, Microsoft, and in fact most software companies do not have as much dedicated support as WebAssist and in general our support is more thorough and knowledgeable. My personal opinion is that WebAssist should concentrate on engineering and documentation so that support isn't needed. Maybe that opinion came through to clearly in my tone without complete explanation it rubbed you the wrong way.

What is your incident number? It is very rare for a submitted incident to not be answered the same day. Expecially when for something as common as the winfilecache issue. I will look into it further.

[bobweber377579]

Ray I agree with you putting money into engineering and documentation so less support is needed. Yes my concerns are probably more product related. My expectations were very high from reading the glowing description of Menuwriter and its features on your site.

I have now solved my problem by switching to another style in Menuwriter. Next week I am going to go back to menus when I start adding pages to my site.

BTW those commenting on support dont ever go near DW Extensions from f-source.
Another company project 7 - excellent, excellent support I bought DW slide show magic from them.

Ray thank you for your help and listening to your customers comments.
bob

[glmcps295424]

Ray,

Your support policy has changed if I'm not mistaken in that the support through service tickets is now free. True?

I think the support pertaining to standard documented features of your products should be free. However, support that involves creating solutions that are not part of the current spec for a given product should be charged for in many cases.

For example I have a support ticket in process at the moment. It involves my lack of understanding of php sufficient to create master/detail order entry pages that function the way I want. I don't expect that this should automatically be a free support ticket.

Getting this working correctly is absolutely necessary to what I'm trying to accomplish. If I have to pay to get it working so be it.

I don't think it's WA's job to teach me PHP.


I suppose it's human nature for the customer to assume that your products will do everything.

Perhaps a disclaimer stating that coding data-driven web sites is a process that involves a degree of programming and that while WA has done the bulk of it, there is no way that you can anticipate the needs of every developer.

I'd like to see more videos created. That takes time and money and they are outdate and less useful following any major product upgrade so that probably is not a sound solution either.

I have found the attitude of you and your techs to be excellent. I can't ask for anything else.

You asked for opinions and there's mine.

Regards,

Gregg

[Ray Borduin]

We do try our best. I think you may have pointed out the flaw in our system though. All support incdents are free and unlimited. We had tried having them expire after a year and giving a certain number in the past, but customers complained, so we changed our system.

As a result we get a lot more incidents, and a lot of them do involve teaching our customers general concepts about PHP, mySQL, HTML, CSS, Dreamweaver, or the web in general. We do take on a heavy burden when we try to not only make sure that our products work, but we actually try to make sure our customers are successful with them. Very few companies go as far as we do to ensure our customer's success.

However there is a valid point that we end up spending a lot of time in support helping people do things that they can't do not because our products don't work, but because they don't know how to use them. As a result someone that has an obvious question or bug reported may not get an immediate response as we are working to help other customers.

There is another delicate balance we keep between answering all of the questions thoroughly and answering all of the questions quickly. We certainly spend a lot of time thinking about support, a lot of energy providing it, and have a lot of resources working on it, but support is a pretty thankless job I did it for over 10 years so I know.

[Ray Borduin]

Jeff, I'd still like to look into that support incident you claim went unanswered for three days. It seems unlikely... seems more likely that you didn't check it for three days and maybe thought it hadn't been replied to? Anyway I'd like to make sure this isn't really a problem, so please let me know the incident number and I can look into it further.

[jeff150879]

I understand your perspective, but that is not really what I am saying... I was trying to explain to you that Quality, Service, and Price are a balancing act. We are a small company, without public funding, without a government bailout and we put 100% of our profits back into updating the product, creating documentation, and support.

I know it is our burden to make these hard decisions, and I don't want to bore you with the details. I'm not saying pick one. I'm saying we already provide all three using 100% of our resources. If and when customers have issues we can either bolster the engineering so that the products are fixed and work better, bolster the documentation so that the customer can be successful on their own, or bolster the support. Unfortunately when you are using 100% of your resources, adding to one area necessarily means reducing another unless you are able to increase profit.

Of the three options engineering and documentation are usually where companies concentrate. The clear reason is that you fix it once and everybody can take advantage of it. I think Adobe, Microsoft, and in fact most software companies do not have as much dedicated support as WebAssist and in general our support is more thorough and knowledgeable. My personal opinion is that WebAssist should concentrate on engineering and documentation so that support isn't needed. Maybe that opinion came through to clearly in my tone without complete explanation it rubbed you the wrong way.

What is your incident number? It is very rare for a submitted incident to not be answered the same day. Expecially when for something as common as the winfilecache issue. I will look into it further.

Hi Ray,

Sorry for the delayed response to your question. My ticket number is 91107 if you still want to look into it and view the timeline of responses.

[Joe Lowery]

Jeff - fyi, Ray is on vacation this week, so you likely won't hear from him until next.

Best - Joe

[Ray Borduin]

Thank you. I will look into that incident further. I appreciate the feedback.

[joe159765]

#91120 ticket has been three days in between. I have replied almost the moment I get the email stating the ticket has been responded to. Still not getting results. I agree anything beyond what the product is SUPPOSE to do should be charged. But the point is. I've NEVER had this much problem making an extension work the way it suppose to work. I keep getting a toJSONstring issue. I've fixed it before by deleting the wincache file. But now that isn't helping. It's EXTREMELY frustrating that I have spent weeks on this now wasting on an extension that is suppose to work well (and as well as advertised). I'm always having problems with webassist products and never had this amount of problems with interakt. They were also quick to repsond. I want webassist to know that this is a problem since it looks like after the purchase of interakt by adobe, they are now going to discontinue all the products all together. So I (as well as other people) will be looking to webassist for more extensions. They are mostly affordable and promise great things. I hope they figure out some of these issues soon. Thanks for listening.