unnecessary information
most of your emails never made it to my inbox, and the ones that did were extremely unhelpful. It's a week planner, not a dialysis machine. Your emails are autoflagging as spam, and I almost manually flagged it the same. Review your email practices.
Graphics quality
"The graphic you used feels very MSpaint"
Totally agree. I should probably get someone to redo them, especially if they distract from the message. Thanks for the feedback.
The tone
"First, I don't really appreciate the condescending tone"
Let me address this. Your first message contained things like
"the ones that did were extremely unhelpful"
"It's a week planner, not a dialysis machine. "
"Review your email practices."
If you have a feedback to give, you don't have to use this tone. If you expected a better tone in my reply, you should not be aggressive from the get go.
Yes I should probably have been a bit nicer, but that's why I have people helping with customer support, because I don't have the level of tolerance. I am ok to lose the business of users who are just not nice..
User interface
"First, the roles and Goals section is just as rename-able as your parking lot, and any other section. It has the same functionality, the same use experiences, etc; it's arbitrary."
It is not arbitrary, it is actually done by design so that the user experience is consistent and users don't have to relearn how to do similar actions across different concepts (roles / lists / days).
"Additive actions are really straightforward and easy. but if I want to remove something from my grid and not have it associated to a role or goal anymore, its a lot less intuitive than being able to drag, drop, and add. "
In order to declutter the user interface, we have to pick which features are the most useful, used the most frequently, and make them easily accessible. Less frequent operations (like removing a role from a task, how often does someone need to do this?) take a bit more time to access by design.
Thanks for taking the time to give your feedback.
You're right; my initial comments were a bit rude. I'm sorry. But as a complainant, I don't have the responsibility of representing your company, you do. Your CSR was doing a fine job, even tone and straightforward questions, not really engaging my attitude. That's a good way to defuse a potentially unhappy individual. Hi fives for them. You didn't really have a reason to get involved in the conversation at all, and I'm still not sure why you did. The only reason that makes sense to me is that you felt slighted personally and took my criticism as an attack on your service and, by proxy, you. This wasn't the case. I saw a problem and I told you about it. If anything, I want you to succeed. Nothing would make me happier than helping you improve something you're proud of!
Also, you wouldn't be losing the business of someone with a bad attitude, you would be failing to gain it. And there's no reason why that has to be the case, either. Often, a bad attitude isn't a lifelong condition of an individual. We all have bad days, bad moments, and I don't think we should be judged solely by those moments. I'm sure not assuming that you are, by nature, this aggressively respondent to one-off criticisms, and I don't think you would want to be. So again, I'm sorry if my comments came off as unfairly antagonistic. It wasn't my intent.
My criticism of your email practice stands: if they're sliding into my spam folder without me sending them there, then you have a problem that needs to be revised. Either the body of the email is reading as spammy, or a lot of other people have flagged your email as spam in the past and the service we use to flag spam has learned from that. My comment that I almost flagged it as spam would tend to support this, as well. Keep in mind, I didn't flag it as spam, and I don't really want to.
My criticism of the content of your email stands: the one that made it into my inbox wasn't helpful. maybe not extremely unhelpful, but certainly just fluff. The difference isn't semantic, it's practical. Telling me what some roles are without really showing me a practical, mechanical application of those roles in your system is just telling me that sometimes people label themselves as different things. If you stand by the practical functionality of Roles in your system, then show off how they work in the email! Celebrate it! These emails should be giving your users a knowledge of the tools, empowering them to use it to it's fullest. becoming familiar with a tool, fluent in the language of its application, will make someone want to pay for it. Your emails are this opportunity to empower the recipient and slyly encourage them to pay you to keep using it.