Confirmed users
5,365
edits
Thunderbird/Support/Workflow: Difference between revisions
→= Merge Duplicate Threads
| Line 61: | Line 61: | ||
==== Change to a Problem if appropriate ==== | ==== Change to a Problem if appropriate ==== | ||
* If you look at a topic and leave a reply but it's not Answered or Solved then change it to a Problem and set status to "Acknowledged" or "In Progress" if that make sense.Try not to leave topics that you reply to without updating the status. | * If you look at a topic and leave a reply but it's not Answered or Solved then change it to a Problem and set status to "Acknowledged" or "In Progress" if that make sense.Try not to leave topics that you reply to without updating the status. | ||
==== Merge Duplicate Threads ==== | |||
* Lots of times, users post multiple duplicate threads. This of course makes support harder than it should. Best thing is to catch it early and merge them using GS's merge facility. However 90% of the time, you won't catch it early. In this case it's best to anoint a "canonical thread" (or start a new one) and leave it at "Problem, In progress" and close (i.e. set to Question, Answered or Problem, Solved) the other duplicate threads (but of course link to the canonical thread and state clearly that you are leaving the canonical thread open so people won't be offended you are closing the duplicate threads). Tag the canonical thread "canonical" plus "canonical [1-3 word topic summary]" e.g. "canonical message preview". for an example see: http://gsfn.us/t/ooa7. | * Lots of times, users post multiple duplicate threads. This of course makes support harder than it should. Best thing is to catch it early and merge them using GS's merge facility. However 90% of the time, you won't catch it early. In this case it's best to anoint a "canonical thread" (or start a new one) and leave it at "Problem, In progress" and close (i.e. set to Question, Answered or Problem, Solved) the other duplicate threads (but of course link to the canonical thread and state clearly that you are leaving the canonical thread open so people won't be offended you are closing the duplicate threads). Tag the canonical thread "canonical" plus "canonical [1-3 word topic summary]" e.g. "canonical message preview". for an example see: http://gsfn.us/t/ooa7. | ||
==== Create a summary thread if users post their problem across multiple threads ==== | ==== Create a summary thread if users post their problem across multiple threads ==== | ||
* Lots of times, desperate users post fragments or all of their problems on multiple (let's call it 'n') threads. In their desperation, they don't realize that this makes it more difficult to help them. They figure that this will maximize the exposure and likelihood of getting a response. Recommendation: Create a new "summary" support topic for them with a relevant title and with content paraphrasing all of their problem across all the threads. And then post a reply (using the "use one topic, not multiple topics boilerplate") on all 'n' (or at least 2 of n) of their threads linking to the summary support topic and unsubscribe from the other threads in Get Satisfaction. | * Lots of times, desperate users post fragments or all of their problems on multiple (let's call it 'n') threads. In their desperation, they don't realize that this makes it more difficult to help them. They figure that this will maximize the exposure and likelihood of getting a response. Recommendation: Create a new "summary" support topic for them with a relevant title and with content paraphrasing all of their problem across all the threads. And then post a reply (using the "use one topic, not multiple topics boilerplate") on all 'n' (or at least 2 of n) of their threads linking to the summary support topic and unsubscribe from the other threads in Get Satisfaction. | ||