-
-
Notifications
You must be signed in to change notification settings - Fork 196
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
Make replying to a correspondence thread easier for users #5441
Comments
See also comments at: |
The question of what route people are using to write to the admin team in these cases has been raised. On WhatDoTheyKnow over the last two years, of the 268 cases 172 were replies with a subject "Re: New response to your FOI request ..." so users replying to the alert telling them they'd had a new response, the remainder include people sending their clarification request via reporting requests for admin attention (selecting various grounds for the report!) and by replying to other alerts. There were, perhaps surprisingly, only three cases of replies with the subject "Re: Clarify your FOI request" - perhaps as confused users' requests are never in the "requires clarification" status. In most, if not all, cases it appears users have read the responses before replying, so they're not just replying to the email alert, they're visiting the site, reading the incoming message, in some cases reading attachments too, then returning to their email to reply. I think a clearer reply option on the site is the best way to address this, but some text changes to the alert emails might be worth considering too. |
On WhatDoTheyKnow.com we occasionally have users opting, not unreasonably, for the "respond to request" link under "Actions" when they intend to do what we call "write a reply" or "send a followup". See also Hide "Authority: Respond to request" [from non-authority users] in actions menu #4179 and "When trying to respond as the public authority but you're not the error message could be clearer" #1453 |
+1 having just seen a WhatDoTheyKnow.com admin send a user a screenshot with the actions button ringed in red and describing the process of sending a reply! Having to explain to users the reply option is accessible via "Actions" is a common support activity. |
The WhatDoTheyKnow support mailbox contains 252 support threads (which are from the last two years) which are included in the results for a search:
So about 2.5 times a week we're helping a user find what they want to do (typically send a reply) by pointing them to the actions button/menu. Perhaps my search is a bit broad, it's 171 hits (1.6 times/week) without "the actions". It appears likely to be people with lesser web/IT skills/confidence who need help, and who there might be an opportunity to serve better. |
+1 following correspondence with a user asking the WhatDoTheyKnow.com team to un-redact an email address so they could reply to a public body. What wasn't clear to the user was that ideally we'd want them to keep their FOI correspondence in public on the site and that the way to reply is via "Actions". |
I suspect lots of users are struggling with replying to correspondence threads. Example correspondence from today:
user support response
|
I've created #6363 and added it to the design backlog for estimation and hopefully scheduling next sprint. |
We also get users replying to the "New response to your FOI request" rather than replying on the site. The "New response to your FOI request" email currently contains no advice on how to reply nor a warning not to reply by hitting "reply" to the email. Related: Send site generated emails from a no-reply address #6404 |
User feedback on WhatDoTheyKnow today:
From context it appears they were seeking to ask for an internal review. It appears they opted to write to the public body directly off-site because they couldn't see how to send their message on the site. |
+1 I've resorted to copying the link from the actions menu on each request myself, and sending that to users because of how difficult it to find this option. |
Issue noted again by a user, who has said that:
|
+1, some users turn to making a "new request" to the relevant body, rather than following up, which must be confusing for everyone, since the body will be receiving emails from multiple addresses, and the user will be continually prompted to classify their requests. |
Closing in favour of the specific fix #6363. |
I'm not sure whether this is better here, or in #6363, but a user has suggested displaying the reply process "in a user friendly visible (colour coded) S.M.A.R.T page" (more about SMART, assuming I've got the right end of the stick.) |
The option to "write a reply" is not currently presented directly on a request thread as it is accessible only via the "Actions" menu.
Putting a reply button on the request thread itself, when a user is viewing their own thread at least, might reduce the occurrence of people writing to the admin team with replies rather than replying via the site
Frequency of users writing to the WhatDoTheyKnow team rather than replying on the thread: 268 cases over the last two years. ~1.4% of support mail. (Those are the cases where we've used our canned-response for this occurrence).
Related: Improve the user experience of replying to your own request #4354
Issues #3648 / #3649 on duplicating the actions menu at the bottom of the thread, which has now happened, were also aimed at addressing this issue.
The text was updated successfully, but these errors were encountered: