Ready

Error Handling

This page provides guidelines for using positive, helpful, and polite language when displaying error messages to users in the Basis design system.

Ready

Error Handling

This page provides guidelines for using positive, helpful, and polite language when displaying error messages to users in the Basis design system.

Positive Language

Present information using positive language instead of negative language--say “can” and “do” instead of “can’t” and “don’t”. It gives users confidence. Avoid being too cheerful as it can come off as insincere.

Do

Do

  • Upload a CSV with column headers representing Unique ID,

  • Name, Date, and at least one delivery metric.

  • Try again

  • To apply add ons, create a revision.

  • Spring 2016 exported to Google Campaign Manager

Don't

Don't

  • File (.csv) must include column headers representing Unique
    ID, Name, Date, and at least one delivery metric.

  • An error occurred

  • You can’t apply add-ons to an approved plan

  • Great job! You successfully exported Spring 2016 to Google
    Campaign Manager!

Offer links to Basis support pages that can provide more information or assistance.

Do

Do

  • There was an error generating the report. [Please
    issue].

  • There was an error loading the page. Please try again.
    If the problem persists, [contact support].

Don't

Don't

  • There was an error generating the report. Please navigate to
    the support page and click the submit issue link.
    There was an error loading the page. Please try again.

  • If the problem persists, navigate to the support page and
    click the contact support link.

Use "Please" sparingly

Even though we want to be polite, try to use “please” sparingly. Only use “please” when the suggested action is inconvenient for the user or implies an issue with the product. 

Do

Do

  • If the issue persists, please contact your CSM.

Don't

Don't

  • If the issue persists, contact your CSM.

Be polite and respectful

Use a friendly tone and avoid blaming the user for the error.

Do

Do

  • There was a problem. Please check the format and try again.

Don't

Don't

  • There was a problem. You most likely used the wrong format

Suggest a solution

Offer specific guidance on how to fix the error, including any steps the user should take.

Do

Do

  • Tactics pasted are outside of group date range. Try updating
    your date range.

Don't

Don't

  • Tactics date range incorrect.

Explain the problem

Clearly describe the issue that has occurred and why it has occurred.

Do

Do

  • Changes were not saved because service provider is inactive

Don't

Don't

  • Changes were not saved

Use clear and concise language

Ensure that the error message is written in simple and easy-to-understand language.

Do

Do

  • File must be in CSV format.

Don't

Don't

  • The file that you are trying to upload must be in a .csv format
    so that the back-end database can process it

Need more guidance?

Suggest an addition or an edit.

Need more guidance?

Suggest an addition or an edit.

© 2025 Basis Technologies
© 2025 Basis Technologies
© 2025 Basis Technologies