cancel
Showing results for 
Search instead for 
Did you mean: 

Reply to message

View discussion in a popup

Replying to:
ISSG_DW
Level 1

Reply to message

I'm sorry but this is a little like the game that gets played among siblings where the older one grabs the younger's arm is popping them in the head with their own arm and saying "stop hitting yourself, why are you hitting yourself..." 

 

For the QB Team - you guys know that there is a problem with this known/stated/recapped/pleaded for/beyond begging issue.  It's really a pretty simple thing and it's NOT the fact that someone simply needs to push the Gear button and log a request.  That has been done repeatedly not to mention you guys keep responding to us so why don't YOU log the issue internally.  After the issue has been rehashed over such a long period of time, how about just cowboy-up and either have someone much, MUCH higher up the food chain (ie VP of Cust Svc) login and say one of probably two responses:

 - "We heard you - sorry that this has gone on so long.  This shouldn't take much to resolve and we've assigned two people to it and should have a fix within X number of weeks.  Please let us know if you're willing to test the new functionality for us."

  -- OR --

 - "Look - why do you keep hitting yourselves with this issue.  If you can find a better online product then go with it.  Otherwise, we really don't care that much to go back and address this - it's not worth it for us to dedicate resources to an issue that is important to a small percentage of users.  Now click on the Gear button and log this as an Enhancement Request or else see if we have an app."

 

Sorry but for you, the QB Team, to keep logging such ineffectual responses comes across as disingenuous and somewhat insulting.

Need to get in touch?

Contact us