Home → Suggestions →

Move checkbox for internal replies to top

• Edit

dennis

26 Jan, 2010 05:54 PM

This happened to nearly everyone in our company:

You want to write something internally, but forgot to click the checkbox, so now the customer gets an email as well.
I think this could be prevented more easily by moving the checkbox for internal replies to the top, rather than showing it at the bottom.

1.) You know before you start typing that it's going to be an internal reply
2.) When you make that mistake once or twice you develop the habit of marking the checkbox before you start typing, so you scroll down first and then back up. I think it makes more sense to put it on top.

Cheers, Dennis

1. 1 Posted by rick on 26 Jan, 2010 05:57 PM

   

   Cool, we'll bring this up with our designer.

   What if we did something like the [Gist
   webservice](http://gist.github.com/), where we put two separate
   buttons at the bottom? That's actually the direction we're leaning
   towards right now.

   • Gist_-_GitHub.png 29.7 KB
   • Edit

2. 2 Posted by dennis on 26 Jan, 2010 06:13 PM

   

   Cool, sounds good!

   I'm not entirely sure if the checkbox or two buttons would be better. So far I had no problems with gist when posting private code, but I think they could look a bit more different (icons and/or color).

   Anyways, thanks for the speedy reply!

   Keep on rockin, Dennis

   • Edit

3. 3 Posted by rick on 26 Jan, 2010 07:57 PM

   

   Thanks, I got the idea from Kyle actually. One of the first things he did at Github was change it so there are two separate submit buttons. He designed these Tender forms, so I assume this is what he would have done on Tender :)

   • Edit

4. 4 Posted by george on 26 Jan, 2010 08:08 PM

   

   Excellent suggestion, please make it safer, especially for new users.
   

   I made the same mistake once.

   • Edit

5. 5 Posted by rick on 09 Feb, 2010 08:00 AM

   

   We tried this, and really did not like it. Placing it next to the submit button seems to be the most logical place. I've attached a screenshot of it (nevermind the pink).

   We have a few other ideas to help prevent mistakes that we want to try. I'll report back when we have something.

   Thanks for your feedback on the matter.

   • pink-reply.png 25 KB
   • Edit

6. 6 Posted by 4ever.web on 09 Feb, 2010 09:17 AM

   

   Please fix this serious usability issue... nearly every user in our company has made this mistake at least once.. send internal note to client.. not good U/I design!

   • Edit

7. 7 Posted by Justin on 03 Mar, 2010 07:04 PM

   

   This has since been fixed.

   • Edit

8. Justin closed this discussion on 03 Mar, 2010 07:04 PM.

9. george re-opened this discussion on 03 Mar, 2010 07:19 PM

10. 8 Posted by george on 03 Mar, 2010 07:19 PM

    

    Noticed that last week...

    Seems to work well...

    ... but TWO Submit buttons (SUBMIT INTERNALLY) and (SUBMIT PUBLIC) could be
    even better?

    Whatever would make it easier to avoid the mistakes... OOPS...

    All the best,
    George
    on behalf of your CoreFact support team

    ||
    || See also www.iNetMore.com
    ||

    • Edit

11. 9 Posted by rick on 03 Mar, 2010 11:43 PM

    

    We actually had that in an original iteration. However, we didn't like having a third Comment & Resolve button, so we moved the checkbox.

    Thanks for the feedback :)

    • Edit

12. rick closed this discussion on 03 Mar, 2010 11:43 PM.