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

Encourage users to find new email addresses for bodies themselves in case of errors/bounces #1782

Closed
RichardTaylor opened this issue Aug 12, 2014 · 3 comments · Fixed by #8000
Labels
easier-admin Make issues easier to resolve f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc)

Comments

@RichardTaylor
Copy link

When users mark a response for our attention we give them a free text box to explain the problem.

If the issue is the email address for the authority needs updating we should point them to the update authority form.

https://www.whatdotheyknow.com/change_request/new?body=bens_test_authority

We should encourage users to research a new address for themselves - eg. stressing the site is administered by volunteers and they can help us by finding the address and saying if they provide the address we might be able to re-send their request quicker too.

@crowbot crowbot added 1 - new and removed 1 - new labels Aug 12, 2014
@garethrees garethrees added f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) labels May 29, 2018
@garethrees
Copy link
Member

garethrees commented Oct 31, 2018

Could also include this where we show a failed delivery status for outgoing messages

@garethrees
Copy link
Member

One possible way could be to have this as a message, something like:

"We think we've found a delivery error - can you find a new email address for us to use? Click here to let us know"

this could then link to a variant of the change request form, which allows the admin to approve the update and re-send the user's request in a one-click operation.

Why? Quicker for all concerned, and reduces a potential misuse vector (as in, we still want to check the addresses!)

@mdeuk

@mdeuk
Copy link
Collaborator

mdeuk commented Mar 25, 2022

Why? Quicker for all concerned, and reduces a potential misuse vector (as in, we still want to check the addresses!)

To expand on that one slightly: we get a fair few 'dodgy' address change requests through the existing mechanisms - sometimes it's just misdirected communications (where a little 'hand holding' can help!), other times it's those annoying form spammers.

A workflow that allows for a site admin to quickly verify that the change seems reasonable would help protect against this, and also allow us to ensure that we do right be our users - as in, prevent some of the more evasive bodies we've seen in recent times causing a nuisance.

garethrees added a commit that referenced this issue Nov 9, 2023
Finding contact details can take a fair amount of work. Users are often
happy to help, but the only signpost we have for this is when submitting
the classification. They might not have time to source a new address
there and then – and the form itself could be improved – but a reminder
for them and other users viewing the requests might help distribute some
of this work to the community.

Fixes #1782.
garethrees added a commit that referenced this issue Nov 9, 2023
Finding contact details can take a fair amount of work. Users are often
happy to help, but the only signpost we have for this is when submitting
the classification. They might not have time to source a new address
there and then – and the form itself could be improved – but a reminder
for them and other users viewing the requests might help distribute some
of this work to the community.

Fixes #1782.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easier-admin Make issues easier to resolve f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants