Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Post History

60%
+1 −0
Q&A How can we integrate a lightweight public ticketing system into our documentation feedback form?

Why not email? We'd rather not ask for email addresses; this should feel completely opt-in and safe to the person offering us the feedback. I assume this is a totally open system - no "login"...

posted 3y ago by manassehkatz‭

Answer
#1: Initial revision by user avatar manassehkatz‭ · 2021-07-08T17:51:38Z (almost 3 years ago)
### Why *not* email?

> We'd rather not ask for email addresses; this should feel completely opt-in and safe to the person offering us the feedback.

I assume this is a totally open system - no "login" needed. Because if a login was needed then you already have email and/or other information needed to connect an issue with a user.

In a totally open system, **requesting an email address is about as simple as you can get while still being functional.** It is a lot less than "create an account". If people are uncomfortable with this they can either use a throwaway email address (which may be a one-time use and they check it if they feel like it (which you won't know), may be a bitbucket (and you won't know), or may actually bounce).

Use this address to:

* Send an initial confirmation.

Just "Thanks for submitting" followed by the text of their submission, followed by "We will notify you if we make any changes or have questions blah blah blah" and "Reply to this email if you have additional information" (the Reply address should be oursystem-12345@example.com, where 12345 is the issue #, which with a little programming can be used to automatically add the replies into your ticketing system).

This message and any future messages should include:

An Unsubscribe link so that if either the submitter doesn't want any more messages or the address was fake (effectively spamming someone else) that it can be removed from your active list.

and

A "view online" link. Since this is open stuff and not confidential, this can simply be a link with the issue ID # plus some sort of hash to prevent casual unwanted random access (12345 was my issue, I wonder what 12346 is...). Not a true "login" - that is more complicated than necessary here.

* Send followups if appropriate.

The message was an actual honest-to-goodness useful suggestion and you implemented the suggestion. Or it was a complaint about inappropriate text on the page and you removed the text. Or whatever. You might *never* send a followup - e.g., if the original user message was spam or "thanks" or "your system sucks" or simply an issue you don't want to deal with.

* Never, EVER send actual marketing emails.

Your messages (initial and followup) can, and should, include your company information, but since this list is not positioned as a marketing list, do **not** use it as a marketing list. It should never leave the appropriate support department except individual items to appropriate people as needed.