The problem: I'm maintaining a list of requested features for Poker Copilot. These mostly come in through e-mail or discussion forums. It's getting unwieldy and I'm running multiple e-mail conversations and forum threads discussing these features. People are requesting things others have already requested. The same bugs are reported multiple times. I'd like the list of requested features and bug reports to be public. I'd like this to be as painless as possible, for myself, and especially for my customers.
The solution (maybe?): Get Satisfaction. I've been considering this site for customer support. Before I take the plunge, would anybody like to offer strong opinions for or against using this service?
The Poker Copilot Blog
Tracking the development of Poker Copilot, Mac OS X software for poker analysis and statistics.
Wednesday, 27 August 2008
Is "Get Satisfaction" Worthwhile?
Subscribe to:
Post Comments (Atom)
Subscribe To This Blog
Posts
Comments
Poker Copilot Translation Project
About This Blog
Blog Archive
-
►
2012
(96)
-
►
May
(13)
- Lock Poker News
- What do MP, EP, CO mean in the positional stats?
- Adding a new Ongame Network poker room to Poker Co...
- Adding a new Merge Network poker room to Poker Cop...
- PokerStars on iPad and Poker Copilot
- Lock Poker and Poker Copilot
- Phil Gordon's Little Gold Book and Poker Copilot's...
- Poker Copilot 3.10 Now Available
- Crushing the Microstakes and Poker Copilot's HUD
- Early Access Version of the next Poker Copilot Upd...
- How many hands do I need for Poker Copilot's HUD t...
- Coming soon: PFR by position, Aggression by street...
- Comments on this Blog
-
►
April
(18)
- Important information from 2+2 : Two Plus Two Foru...
- Coming in the next update: VPIP by position
- A Nice Email…in French
- Poker Copilot Tip: Move HUD Panels without the Ful...
- Update for Winamax Users
- Poker Copilot 3.08 Now Available
- Poker Copilot Blog: 1000+ blog posts
- Poker Copilot and Zoom Poker: Update
- Poker Copilot 3.07 Now Available
- A poker player uses Poker Copilot to improve
- Coming in the next update: FALSE filters
- Mockup of Potential Poker Copilot Dashboard Concep...
- A Poker Copilot work-around for Merge Network idio...
- Poker Copilot App Updating
- Carbon Poker has its own HUD! (but only on Windows...
- Improving Poker Copilot's App Updating
- Poker Copilot 3.06 Now Available
- False Assumptions
-
►
March
(18)
- How NOT to make money as a software company
- Zoom Poker HUD Early Access Edition
- Changes to the Poker Copilot Hand Formatter
- Coming in the Next Update: Zoom Stats can be separ...
- Poker Copilot and Zoom Poker: played my first sess...
- The Absurdity of Modern Life: Facebook claims trad...
- Poker Copilot and Zoom Poker: Progress Update
- What character is that?
- PokerStars screen names
- Poker Copilot and Zoom Poker
- Poker Copilot 3.05 Now Available
- Ongame and Table Size
- Updated Poker Copilot User Guide
- Coming in the next Update: Unopened PFR Statistic
- Poker Copilot 3.04 Now Available
- Google Analytics Update: Almost a Good Graph
- Poker Copilot Website in Russian
- Downloading Older Poker Copilot Updates
-
►
May
(13)
3 comments:
I want to start by saying: I'm completely biased. I am the community manager at Get Satisfaction.
I think that a number of the problems you're having could certainly be solved by using our site, but I don't want to give you the hard sell. Rather, I want to point you to Mac-centric (including solo) developers who are using our site, so you can get an idea of how they are using us:
Sci-Fi Hi-Fi: http://getsatisfaction.com/scifihifi/products/scifihifi_podworks
Tapulous: http://getsatisfaction.com/tapulous
Panic: http://getsatisfaction.com/panic
RescueTime: http://getsatisfaction.com/rescuetime
Second Gear: http://getsatisfaction.com/secondgear
I will leave additional comments to other folks. Call on me if you have any questions whatsoever!
E
Eric Suesz
Community Manager
Get Satisfaction
eric [at] getsatisfaction [dot] com
You should read Getting Real by the 37 Signals guys. Their advice would be to not track feature requests because the important ones will come up over and over again and you won't be able to ignore them.
Although I respect 37 Signals emphasis on simplicity and tactics, if there is a method that allows Steve to collect all comments for later consideration without being "in the loop" I think he should do it. Not only can he still see the same feature requests coming up frequently - there might be that one "gem" in there, that is only mentioned once, that turns out to be a huge winner. If you don't track so you can reflect with leisure, I think it would be very easy to miss something like that.
Steve .. certainly give us an update post not only on what you decide - but how it works out for you!
Post a Comment