Mews recognizes that content is design and we approach it the same way. We use data, careful consideration, and justification for every word.


The Mews in-product voice embodies our mission statement and values, while taking into account the way we communicate with property staff and guests.


We know what we're doing and want our users to feel the same level of confidence and assurance with every action they make.


We are helpful, considerate, and caring towards any situation that may come up and ensure that property staff and guests feel their needs will be met.


Whether you're taking care of guests, or you are a guest, we can relate. We want our users to feel like they're communicating with colleagues, fellow travelers, or simply put, a human.


The tone we use shifts depending on the situation the user is in. With this in mind, the following is a list of situations the user will come across most often, with guidelines of how to write content for each of them.



Success messages notify the user that an intended action was completed and registered in the product. This can include adding, saving, confirming, or deleting. Do not use the word “successfully” in any success message, as it’s already implied.


Use a positive tone when writing success messages. We want to reassure the user that their intended action was completed.



Informational messages inform the user of a state or status within the product. Be clear and concise with information to not overwhelm users. Use components effectively and follow their individual guidelines.


Use a neutral tone when writing informational messages. We want to give the user more information that could be valuable to them, and we should do this calmly.



Warning messages, or confirmation messages, require feedback from the user. They are used in places where we want the user to take a moment to consider their action.


Use a cautionary tone for warning messages. The user should take a moment to fully review and understand what they are doing, and the possible consequences of their action. Avoid writing "Are you sure?", instead, confirm their action. In the case of removing or canceling, the tone can be sterner. In the case of adding or saving, the tone can be more assuring.



Danger messages, or error messages, notify the user that something went wrong within the product. When writing error messages, lead with a solution when possible.


Use an understanding tone when writing most error messages. We want to guide the user through their problem, not just notify them that a problem exists. In more system-critical situations, use a serious tone. For more info, go to Error messaging