-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Investigate if the new contact us form has indeed reduced admin for us and simplified user experience #1831
Comments
Might be worth digging into to this a little bit. This is what came into the inbox: To start with usage as follows:
|
So an update could be:
|
@JoannaHill good start. When I see this list the following come to mind So how does this revised list look to you?
|
Yeah great Kat! I'm happy to support this change. I will also add this issue to the list of things to test/research more deeply. |
@JoannaHill I've reported the latest emails in the inbox via contact form in the #planningalerts channel in slack, let me or Matthew know if you want Missive access again at any point |
Inbox Emails via contact form since June 30 = 61 Contact form: Stopped receiving alerts 4 |
@JoannaHill haha I felt a bit nervous about pasting the stats this in here, so thanks for being bold! I'm removing myself from this since I'll be away. There's a mix up in I want API access, somewhere in there its about seeing spam mails come in via that option. I'll try and find time to track it down before I go. |
Adding link to non public google doc with manual canned responses which could inform this issue. |
I note that the references to canned responses are not the current ones. The new ones are in Missive. @JoannaHill would it help to have these exported? I seem to remember this is a manual cut and paste job, but I could find time to do this if it seems important here. |
I've updated the document to refer to a new list of canned responses as of today 08/08/24 |
Background
With the new design look and feel we moved from an email address to a form as a way for users to contact us. The purpose being to simplify the admin required on our end and to make things easier for users. I think we could do some testing and exploring to make sure that's what we've arrived at - for us and users.
Specifically I wonder if we limit the drop down list to 5.
We're asking the user to read each one and reflect on their query and whether it fits, which is a big ask ultimately benefiting us. So I propose we cut the current list of 9 down to 5.
The text was updated successfully, but these errors were encountered: