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 would like to address both 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 step they take.


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 talking with a colleague, fellow traveler, or simply put, a human.


Our tone should always shift depending on the situation the user finds themselves in. With this in mind, the following is a list of situations the user will come across most often, and examples of how to approach content for each.



Success messages notify the user that an action was completed and registered in the product. This can include adding, saving and completing actions across the product. Avoid directly using the word “successfully” - as it’s unnecessary.


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



Informational messages inform the user of a state or status within the product. Be as clear and concise with information to not overload the user. 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.



Confirmation messages request 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 confirmation messages. The user should review and take a moment to fully understand what they are doing and what are 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 shift to be more stern. In the case of adding or saving, the tone can shift to be more assuring.



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 a problem, instead of notify them of a problem and instill panic. In more system-critical situations, use a serious tone.