Skip to content

[HOLD for payment 2022-05-20] Present all main CTAs in NewDot as green buttons to encourage engagement #7706

@kevinksullivan

Description

@kevinksullivan

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Action Performed:

  1. Create workspace
  2. Navigate to any of the workspace pages

Expected Result:

Per this conversation, we want to present the desired next step very clearly within NewDot when in the "empty" or non-configured state, by presenting the ideal CTA as a green button. More specifically, that means we'll show the following actions as green buttons throughout the product:

Connect bank account
This button is shown in the following pages of the Workspace editor:

  • Issue cards
  • Reimburse expenses
  • Pay bills
  • Send invoices
  • Book travel

Connect online with Plaid
This button is shown in the Connect bank account page. Additionally, we'll want to use the same pattern whenever a user has started adding a bank account but the setup is incomplete. That includes:

  • Continue with setup (shown when user exits before completing bank account flow)
  • Yes, let's chat! (shown when user fails check and we follow up with next steps in concierge)
  • Chat with concierge (shown when user has 1) signed up with a public domain and 2) successfully added a bank account through this flow, but must add a private email address.)

Add payment method
We will show Add payment method as a green button when no payment method exists within the Payments page.

Actual Result:

We do not use green buttons to promote these CTAs, and thus next steps for configuring a workspace and/or account are less obvious.

Notes/Photos/Videos:
Connect bank account

Connect online with Plaid

Add payment method

Slack conversation: Link

CC: @shawnborton @JmillsExpensify @quinthar @miljakljajic

View all open jobs on GitHub

Metadata

Metadata

Labels

DesignEngineeringExternalAdded to denote the issue can be worked on by a contributorImprovementItem broken or needs improvement.WeeklyKSv2

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions