Trade Feedback Issue

Discussion in 'Trade Talk' started by CraftBeerLos, Jan 29, 2016.

Thread Status:
Not open for further replies.
  1. CraftBeerLos

    CraftBeerLos Zealot (682) Jul 18, 2014 North Carolina
    Trader

    I recently completed a successful trade and provided feedback, but I noticed that the other trader provided good feedback yet elected the "Bad" option. I assume since his feedback description was good and he stated "100%" recommended, that there were no issues.

    I have sent a couple polite messages asking trader to please review their feedback and fix to no avail. I have checked and they have been on several times since my messages.

    I probably wouldn't care, but it affects my successful trade percentage.

    How should I proceed? Was thinking of editing the feedback that I provided to reflect this issue. Maybe that would draw their attention?

    Thanks for the help
     
  2. F2brewers

    F2brewers Maven (1,432) Mar 12, 2005 Massachusetts
    Society Trader

    @Lucho please fix this or explain why you marked the trade as "bad".
     
    CraftBeerLos and JohnGalt1 like this.
  3. Abbbp

    Abbbp Pooh-Bah (1,762) Mar 9, 2013 Texas
    Pooh-Bah Trader

    Just looks like it was an mistake/accident, I'm sure @Lucho will fix it. Granted he sure could stand to let you know he would...
     
    CraftBeerLos likes this.
  4. CraftBeerLos

    CraftBeerLos Zealot (682) Jul 18, 2014 North Carolina
    Trader

    Yep, I definitely think it was an honest mistake. Just wish he would address it. Since I see his last seen time keep updating, I can only assume he uses the mobile app and doesn't see alerts nor checks his messages. Doubt he is ignoring messages and alerts... but who knows. :slight_frown:
     
  5. F2brewers

    F2brewers Maven (1,432) Mar 12, 2005 Massachusetts
    Society Trader

    well, he's been on today, so he should see the tags and alerts.
     
    CraftBeerLos likes this.
  6. CraftBeerLos

    CraftBeerLos Zealot (682) Jul 18, 2014 North Carolina
    Trader

    @Lucho apologized and addressed the issue. All set. Thanks everyone!
     
Thread Status:
Not open for further replies.