Skip to content
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

Add a "Contact Support" button to Spoke #1642

Open
ajohn25 opened this issue Jul 24, 2023 · 3 comments
Open

Add a "Contact Support" button to Spoke #1642

ajohn25 opened this issue Jul 24, 2023 · 3 comments
Labels
additions: feature 🆕 New feature or request experience: ux 👤 User experience platform: node 🔅 Related to Node backend platform: react ⚛️ Related to React client application

Comments

@ajohn25
Copy link
Contributor

ajohn25 commented Jul 24, 2023

Is your feature request related to a problem? Please describe.
Clients opening tickets do not get a clear sense of what relevant information to include

Describe the solution you'd like
A "Contact Support" button within Spoke (UI details TBD) which captures relevant information from the instance, as well as user feedback, and submits a ticket to our inbox

Describe alternatives you've considered
Gathering details through ticket follow up https://app.asana.com/0/1203474796993214/1205129778362403/f

Additional context
Follow up from a wide impact incident

@ajohn25 ajohn25 added additions: feature 🆕 New feature or request platform: react ⚛️ Related to React client application platform: node 🔅 Related to Node backend experience: ux 👤 User experience labels Jul 24, 2023
@ajohn25
Copy link
Contributor Author

ajohn25 commented Jul 24, 2023

@politics-rewired/spoke-client plz weigh in on details here whenever! (ex. what screens could this pop up on, what info should the email we get include, what the user dialog should look like etc.

@lediur
Copy link
Contributor

lediur commented Aug 2, 2023

Could we use Help Scout beacons for this?

I think this should appear on every screen in a consistent location on the top navbar, and in the bottom right corner on the login screen. We can provide customer information to the Beacon programmatically, so that should reduce the amount of information we need to manually gather from the client.

@kohlkenn
Copy link

I think this should appear on every screen in a consistent location on the top navbar, and in the bottom right corner on the login screen

We/admins may not want "texter" role to have a direct line to support. Two ways around this:

1) If user is supervolunteer/admin/owner: Beacon appears on every screen
If user is texter: Beacon appears on /app/#/account/# only

2) Beacon appears on all pages except /app/#/todos

2 would be easier to implement but would prevent any user from submitting reports from the todos page (while 1 would allow those with role > texter to do so)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
additions: feature 🆕 New feature or request experience: ux 👤 User experience platform: node 🔅 Related to Node backend platform: react ⚛️ Related to React client application
Projects
None yet
Development

No branches or pull requests

3 participants