PROTOTYPE: Provide guidance on how to create a bilingual template using Notify

[yaelberger-commits]

Provide guidance on how to create a bilingual template using Notify

Description

As a Sender, I need to know how to send bilingual messages so that I can provide information in both official languages when I don't know the language preference of the recipient.

WHY are we building? Through usability testing we surfaced that some users don't know how to send bilingual messages using Notify.

WHAT are we building? Guidance earlier on in the onboarding process to help Senders understand their options for sending messages in EN, FR or bilingually when using Notify and when creating templates. A new guidance page specifically about crafting bilingual messages

VALUE created by our solution More public servants will consider using Notify because they will know they can send bilingual messages easily. Creates more trustworthy messages because bilingual messages are often associated with official federal government messages. This would distinguish Notify from other notification tools because it will support bilingualism where other COTS might not.

Acceptance Criteria** (Definition of done)

• [ ] Ensure any guidance we give here about which language goes first aligns with federal OL policy, check with the product policy team
• [ ] It is made clear from the onboarding content that a service can be either in EN, FR or bilingual, and templates can be created either in EN, in FR or bilingually to send messages using Notify (Maybe in Features with images)
• [ ] A template for a bilingual messages in a bilingual guidance doc that can be copy/pasted
• [ ] Designs updated in English and French
• [ ] Team review
• [ ] Design critiques (a11y)
• [ ] Link research insight back to hypothesis from Epic or Objective in Airtable
• [ ] Once change/fix/feature is implemented, mark insight as "resolved" in Airtable
• [ ] Once change/fix/feature is implements, link insight to design artifacts (Figma) in Airtable

Given a Sender doesn't know the language preference of their recipients, when they go to set up an account, create a new service or create a template, they are able to choose the best option for their service and template to send bilingual messages.

Might be a link to branding here. If a service could have multiple brandings/logos uploaded and select which branding for which template, it could provide a better experience when creating bilingual messages.

Technically would be quite easy to add prepopulated language tags and content to all templates Alternatively, we could provide it in guidance and have people copy/paste

**Technically wouldn't be too difficult to also add new template options when creating a new template for bilingual email and maybe bilingual SMS, even though SMS can't be formatted with HTML. More work than just prep-populating templates. But additional value because would be more personalized experience and users who don't need to send bilingual messages wouldn't need to delete anything from the templates.

[yaelberger-commits]

Hey team! Please add your planning poker estimate with ZenHub @adriannelee @amazingphilippe @YedidaZalik

[adriannelee]

Would we include testing for this card?

[yaelberger-commits]

IDEA: pre-populate language tags in the template to show Senders how a bilingual message would be structured.