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

feat: add email in feedback widget #4825

Closed
wants to merge 1 commit into from
Closed

feat: add email in feedback widget #4825

wants to merge 1 commit into from

Conversation

alter-eggo
Copy link
Contributor

@alter-eggo alter-eggo commented Jan 18, 2024

Try out this version of Leather — Extension build, Test report

Screenshot 2024-01-18 at 19 15 42

Copy link
Contributor

@pete-watters pete-watters left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, nice to add this 👍

Copy link
Collaborator

@kyranjamie kyranjamie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This configuration should be added in src/shared/utils/analytics.ts. In this file I disabled email intentionally.

I wonder also if we want to add email? Allowing user to submit email suggests we'll get back to them. Who's going to take responsibility for this? Are we sure we want it? cc/ @markmhendrickson @314159265359879

@alter-eggo
Copy link
Contributor Author

alter-eggo commented Jan 18, 2024

I believe there is no much sense in most of feedback messages (and actually in the feature itself) without getting back to user and help with problems

@314159265359879 314159265359879 self-requested a review January 18, 2024 19:00
Copy link
Contributor

@314159265359879 314159265359879 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is turning into a nightmare for the support team.

Sentry is giving us a lot of feedback from users that actually look like they expect a reply. Now we can't respond to that.
Adding email seems like a good solution, but it is only helpful if that forwards the message history to our existing support app, keeping track of another channel that is separate won't work.

Can sentry forward these messages to our support app, that way we can let them atleast integrate with the desired flow. https://trustmachines.slack.com/archives/C069V6G48F7/p1703239096414329?thread_ts=1703236711.123909&cid=C069V6G48F7 )

Lets talk about this and possible solutions.

@kyranjamie
Copy link
Collaborator

I know it might seem like a good idea to collect as much info as possible, but like Werner says, people will expect us to get back to them.

This isn't a support tool and we don't want to blur the lines. Working on a feedback tool in the past, people using it for support was a common problem, normally resolved by a msg pointing user that need support towards our actual tool.

Let add a message instead to the effect of "If you need support, go here instead"?

@pete-watters
Copy link
Contributor

I approved this but I should have checked if there was an issue for it. Was there an original issue to do this?

@alter-eggo
Copy link
Contributor Author

@kyranjamie @314159265359879 there are already some feedback messages containing user's email, as I understand we don't answer them?

Let add a message instead to the effect of "If you need support, go here instead"?

yeah, such message may help, though imo the less steps user needs to send feedback/get help, the better, especially when you work with money. I believe it's crucial thing for the project. at the same time I agree with @314159265359879 that we need to use only one tool. maybe existing one has feedback widget?

@markmhendrickson markmhendrickson added enhancement-p1 Critical functionality needed by many users, with no clear alternatives enhancement labels Jan 19, 2024
@markmhendrickson
Copy link
Collaborator

Thanks for taking this initiative @alter-eggo! I agree with the sentiment that users need fewer steps to get support, and I also agree with others here that we need to provide users with that in a way that flows into our support team's process effectively. I've created a new project for us to explore the best solution here before moving forward with any particular issue or pull request.

@alter-eggo
Copy link
Contributor Author

close this pr for now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement enhancement-p1 Critical functionality needed by many users, with no clear alternatives
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants