-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Promote concierge / phone support in NewDot workspace v1 #6719
Comments
Triggered auto assignment to @tjferriss ( |
@tjferriss Whoops! This issue is 2 days overdue. Let's get this updated quick! |
This looks really great. My only comment would be that the grey "?" icon doesn't stand out. Have we considered giving it some color, maybe green. Alternatively, could we do something to bring attention to it the first time someone opens the workspace editor? Maybe Concierge sends a message about it. |
hm yeah, My thought was that we don't want to call this out to be more prominent than the surrounding product, since it's really a fallback. Green feels a bit "positive", since it is the color we use for all actions we want the user to take in product. Then red felt a bit intense on the other side of that. |
Those are all good points. I've gotten some feedback on calls where people express they wish they had realized what the "Call" button on OldDot was a long time ago. This is probably where this feedback is coming from. I like your reasoning about this being a fall back and I like that we're going with a universal "?" button. Let's do it! |
Triggered auto assignment to @puneetlath ( |
Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Also, can we get an svg of the question mark icon? Looks like we don't have that icon in new dot yet. |
Auto-assign attempt failed, all eligible assignees are OOO. |
I tried adding the design label, but it looks like everyone is ooo. @Expensify/design can someone give me the svg for the question mark icon whenever you get a chance? Thanks! |
Asked some questions about the task IDs here: https://expensify.slack.com/archives/C07F03W66/p1640902561149500 |
Icon is here: question-mark-circle.svg.zip |
Created an issue for battle cards here: https://github.com/Expensify/Expensify/issues/190312 |
@kevinksullivan to confirm, you want the request call page to have the exact same functionality on new dot that it does on old dot? From what I can see, there are a handful of things the old dot page that the new dot page doesn't:
To confirm, you want to update the modal to have all that? It's all doable, we just will need to add the API call to get the wait time. |
@puneetlath yes I think we should add these to NewDot. The callback time was recently added to OldDot, but it would be great to make that consistent in NewDot as well. We could always spin up a separate GH for that as well @puneetlath ? |
Cool. GH for updating request a call modal is here: #7067 |
Looks like botify is jumping the gun here. |
This just hit production. |
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:
Expected Result:
Following up on https://github.com/Expensify/Expensify/issues/184190. Let's promote support options for call/chat in each tab of the workspace editor. We will do this by:
Adding the

?
icon to the top-right corner of each page within the workspaceWhen the icon is tapped, go one level of navigation deeper that promotes two options:

Actual Result:
there are no support options promoted within the workspace
Reproducible in staging?: Yes
Reproducible in production?: Yes
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL: https://github.com/Expensify/Expensify/issues/184190
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: