Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Updated Email #48

Closed
jehlers opened this issue Sep 12, 2014 · 2 comments
Closed

Updated Email #48

jehlers opened this issue Sep 12, 2014 · 2 comments
Labels

Comments

@jehlers
Copy link

jehlers commented Sep 12, 2014

Current email

screen shot 2014-09-02 at 2 39 46 pm

New email design

Biggest updates:

  • Reorganization into 3 columns - Product, Price, Vendor
  • Associating the tags with either the product or the vendor
  • "Branding" in process. We may or may not keep the Communicart wordmark. For now it is a placeholder.
  • Colors are also still in process (as you will see in issue # )

c2-email-approver

Current approval notification emails

screen shot 2014-09-02 at 2 40 39 pm

screen shot 2014-09-02 at 2 41 24 pm

New approval notification emails

Biggest updates:

  • Pulled the approval notifications into the context of the purchase request
  • 2 columns for the list of users who's approval is pending vs approved - Helps the user follow the process and clearly identify which approvers they are waiting for.

c2-email-pending

c2-email-approved

@jehlers jehlers added the design label Sep 12, 2014
@jtag
Copy link

jtag commented Sep 23, 2014

Hello!
Some thoughts:

  1. When you squint at these emails the highest contrast and strongest shape is the "product, price, vendor" header for the items table. How to dial it back so it's supporting info?
  2. Esp when the approvals box comes into play my brain wants a (h1-like) hierarchy
    Purchase Request
    Approval Status
    Items <<maybe adding this before the table would help
  3. Language for empty pending state could use shortening.
  4. Do the approvers know who else is on the approver list? Or a later feature? Knowing someone else had already approved this might help me approve this too. (Could argue you don't want people influenced but it might help) But I digresss...
  5. What happens when something is not approved? Can it be rejected? Is that indicated?
  6. "View item in this browser" is bold blue link while other links aren't. "Feels" too much like a required CTA. Might be outside needs of this but a lot of emails have the "view in your browser" right at the top in a mini header of sorts.
  7. Price alignment. Should they all align to the decimal point? So you can tell large and small numbers.
  8. What do items look like when it is one item? $5.99 (1 x 5.99?--just kicking around use cases.
  9. For Purchase Request that Approver sees: Instead of a "tip"--funny connotation, consider a more appy way to reject it.

[Approve All with One Click]

Or Reply to this email with the word "Reject" and your reasons why.

^^ I'm curious how Zen Desk handles their in email correspondence that is also associated with a system. Might be something there.

@jessieay
Copy link
Contributor

Seems like we are due for another round of email redesigns. At the moment, this seems outdated. But cc @amberwreed as a reference for when she thinks through next round of redesign!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants