I'm wondering about the use of "successful" in confirmation messages after a form has been submitted ("The form has been successfully submitted." or "The mailbox has been successfully set up"). To me it seems too verbose. Is it not enough just saying the the form has been submitted? And if an error occur, I can be more specific.

When we use "successful" all the time, to me it almost sounds like we are expecting an error and are so proud that it actually worked.

What do you think?

  • I'm still waiting for my first encounter with the message "The form has been unsuccessfully submitted". Until then, I'd remove "successfully". As already written, the best confirmation is to present the next step (mailbox set up -> ask whether to write an email). Jan 13, 2014 at 13:33
  • Which is exactly why I wanted to remove it. Thank you for the feedback. Jan 13, 2014 at 15:06

3 Answers 3


I agree. Successful is a long word and The form has been successfully submitted is a bland and formal way of confirming something happened.

However, the idea that a form has been successfully submitted is more reassuring than if it had just been submitted without any other status. It indicates that not only was it sent, but it was also received somewhere. Or at least that's one interpretation of success.

What is success?

The problem is that what is successful in the mind of the developer at the time of writing may not match up with the user's idea of success at the time of completing the form. Does success mean it was sent or that it was received or that it made it's way into a database or does it misleadingly mean nothing at all. Is the success a state of guaranteeing a response or some other action.

That's really why the word successful is wrong - it doesn't explain what success means - despite the sense of optimism conveyed.

Does it work for repetitive situations?

If the user is going to see the confirmation message frequently, the phrase The form has been successfully submitted is going to get pretty boring pretty quickly. Much better to keep it short and sweet. If you can make it work for repetitive situations - it'll work for one off use-cases too.

Keep tone and voice relevant

It's important to keep the copy sensitive to the context of the surrounding tone and voice as well. For example, Thanks for that, job's a gooden might not work on a high stakes financial institution website.

Keep it real

Probably whatever copy you put after a form gets submitted is always going to feel like its a message that gets put up automatically, whether there was any real element of success or not. It may be better to give some brief animated indication that behind the scenes something is working and then to indicate the success graphically with one or two words of confirmation or thanks, and if relevant some expectation of what happens next (although if done right, the user should already have been given some indication of what to expect in terms of action and timing.).

So, thanking the user might be a better way of implicitly indicating the success of submitting a form:

  • Thank you
  • All done
  • Thanks for that. We'll be in touch within 24 hours.
  • All done - we copied an email to you as well.
  • Thank you. You've been sent a copy of this by email.
  • Thanks for that, your feedback is appreciated!
  • Thanks. In case you need it, your reference is 123456
  • Great, your account is ready to use right away

And finally - don't block the user

But that's not all - those messages are not good enough on their own. It's wrong after submitting the form to be given a message (successful or otherwise) that essentially terminates the user's activity on the site. User's should always be guided on a progressive path, meaning that they don't have to backtrack or start navigating again.

So as important as the positive feedback is, it's equally important to give users options of where to go next now that the 'form' task has been completed. This takes away the weight and responsibility that would otherwise be forced upon a simple message.

Giving the user the next steps prevents them from focusing on the message too much, and they won't hang around wondering about what success means, or about whether it really got received. Instead, with your help, they'll be thinking about what else they might want to do.

  • When I translate such messages to Norwegian I usually strip away all "thank you" and "please" and "sucessfully" etc. since I think it sounds patronising and too formal (at least it does in Norwegian, we're very informal). I'd translate it to just: "Skjemaet er innsendt" ("The form is sent in") Jan 13, 2014 at 10:18
  • I agree that "sucessful" is wrong. To a user, "sucess" when sending in a form is when something actually has happened in the real world (a human has actually read a message, a product is shipped etc.) not that it's just received by the server without producing an error (that should really be expected). Jan 13, 2014 at 10:21
  • Thank you for some great comments. At the moment I can only change copy, not functionality. And most of these confirmation messages are modal "dead ends" where user is confronted with a "go back to overview" or similar option. Plenty of room for future improvement. Jan 13, 2014 at 11:35

One good method to do this kind of a thing without interrupting the user is to just give a waiting circle while the form is being submitted. Once successfully completed, replace it with a green tick mark. And show it for just two seconds.

enter image description here
enter image description here

And as Roger said, don't block the user. Put this at a corner

  • 6
    I've been sitting here waiting for 15 minutes for that image to load - how big is it... Jan 13, 2014 at 11:38

I often just use a general "Action successful", assuming that the user knows what he/she just did (create, delete).

I think it's good to use it at all, because it shows the user that something happened. Of course, this depends on how the software is written, and I often tend to just do nothing if parameters (data) are missing (as opposed to returning an error when the parameters had been invalid).

  • 1
    I think that's a wrong assumption. Often the user does not remember what (s)he does or at least is not sure what (s)he just triggered. So confirming the actual action is certainly helping the user to stay in sync what the application actually did. Jan 14, 2014 at 7:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.