We need an email response design template / guide for canned responses.

[katska]

Email templates old and new are going to need visual design. In chatting with @sabpop just now we talked about this being somewhat dependent or at least related to the visual design @JoannaHill is working on.

Here are the current state of help / support / canned responses: https://docs.google.com/document/d/19T3gsKGefMs9-lGzIyhCloarjCxi7IRYSYietOElFkE/edit#

These begin life as an initial response that I don't spend a lot of thought laying out, and they're not pretty, nor consistent visually, nor consider different devices and screens. Badly trackpad drawn loops, differently coloured arrows, and different amounts of screen shown based on what seems appropriate context. They can be much better.

I'll iterate responses as similar requests come in, so that the wording and basic screenshot is informed by and made a bit more robust as a canned response. The most recent versions in FrontApp may not be reflected in the google doc on a given day, as I periodically return and update them manually. (there's no easy way to export as a group from Front)

@sabpop you suggested picking out different kinds of response which seems like the next step here. Please chime in with your thoughts on the process to get these from slightly hokey responses to useable content.

[katska]

Also, turning the canned responses into reusable content that can be placed in a Helpdesk for example is another issue, so this is also related to converting for self served content, including the Help (currently FAQ) related to #1700

[stale[bot]]

This issue has been automatically marked as stale because there has been no activity on it for about six months. If you want to keep it open please make a comment and explain why this issue is still relevant. Otherwise it will be automatically closed in a week. Thank you!