-
Notifications
You must be signed in to change notification settings - Fork 16
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
Support Team Lead #102
Comments
Cycle 12 reportThis is the first cycle report on this newly-created role issue. I've been playing this role since its inception in January along with the other new team lead roles, but we only just now got the actual role issues in place. In any case, cycle reports here should be a good opportunity to sum up what's happened over the cycle with the support team, what's needed and what to look forward to. Support coverage calendarSo far as I can tell, the coverage calendar is working out well and we've got pretty decent shift coverage. For a while there it seemed like we may have actually overdone it and brought on too many support agents, but with the recent spate of issues, I'm not sure that's the case. If you have any feedback on how we're doing here, please speak up. New support agentsThis cycle was the first with @bisq-network/l1-support-agents @Bayernatoor, @huey735 and @MwithM, all of whom played the support intern role between Cycles 10 and 11. Welcome all! Changes in the mediator role@bisquser has stepped down as a mediator, and @wiz and @Bisq-knight have recently bonded into the role, meaning that the @bisq-network/mediators team now consists of @leo816, @wiz and @Bisq-knight. Thanks @bisquser for your efforts, and welcome to the new team members! New support budget proposalIf you haven't already seen it, please review @wiz's proposal for how much each support role will be compensated at bisq-network/proposals#200. Support case trackingOne of the projects started in the wake of the Q1 update was to establish support issue case tracking (bisq-network/projects#5). Unfortunately, this effort got stalled and hasn't been picked back up to date. Without it, we don't have any real metrics around how many support cases we're dealing with or how well we're dealing with them. I have simply been unable to push the ball forward on this due to time constraints, and that probably won't change any time soon. If someone on the team is interested in taking over this project, please speak up. bisq.support Keybase subteamAnother change we made out of the Q1 update was to create a private bisq.support subteam where agents and devs could work together in private, sharing case information with each other on an as-needed basis. This seems to have been a positive addition and the subteam is pretty lively with activity. This is in addition, of course, to the existing, public Critical bugs boardOne of the projects we did complete out of the Q1 update was to establish a critical bugs board and process (bisq-network/projects#16). However, without the support case tracking process in place, I'm not sure how much value the support team is getting out of / putting into the critical bugs board. The idea has been to reference critical bugs (and other issues) in our support case tracking GitHub issues, so that we have some kind of running count of how many support cases are related to each bug, helping us to prioritize which ones to fix first. In any case, if you're a support agent, please consider adding comments to critical bug issues when you encounter them with users, whether or not we have the support case tracking process in place. See https://bisq.wiki/Critical_Bugs for more details. Lost fee reimbursementsWhen trades fail for technical reasons like transactions failing to broadcast, we have a policy of reimbursing traders for their lost Bisq trading fees and Bitcoin mining fees. For quite a while, @KanoczTomas played the informal role of handling these reimbursement requests, but has stepped down and has now handed the work off to @leo816. I will create a new "Lost fee reimbursement agent" role very shortly, and will assign it to @leo816. This will not be a bonded role. Indeed, it requires the agent to put up the reimbursement funds out of pocket and then be reimbursed by the DAO in BSQ. Fortunately, these amounts are never very large. Changes to the refund agent / arbitrator role@RefundAgent is now in the process of stepping down from this role, and it is of urgent importance that we find someone to take their place. @m52go has recently written up documentation on the Refund Agent role and its relationship to the Burning Man / Donation Address Holder role. See bisq-network/admin#70 (comment) for details. @wiz and @cbeams will be meeting soon to further define the Refund Agent / Arbitration role. If you are interested in owning this role, please let one of us know. The Bisq wikiYet another project out of the Q1 update was rolling out the new Bisq wiki, principally for the reason of creating a kind of knowledge base for Bisq support. There has been quite a bit of activity on the wiki since, and many articles have been written. We still haven't officially rolled it out, but I think we're getting close to a place where we should do that. The main outstanding items are putting together a suitable main page that guides the users to the different major kinds of content. If someone is interested in doing this, or more generally owning the project to roll out the wiki, please speak up. Also, @kemccall has come on board to fill the Wiki Editor role. This role is still being defined, but please keep an eye out for anything Ken has to say, and feel free to reach out to him. The main idea of the Wiki Editor role is to have someone responsible for the overall structure and standards on the wiki. Think about how Wikipedia Editors work, and you'll get the idea. Ken is not a subject matter expert on Bisq (yet), but he is a seasoned professional technical writer and editor, so should be able to add a lot of value in helping us keep our content clean and consistent. Final thoughtsI may have missed something above. If there's an important topic I haven't covered here, i.e. something outstanding in support that needs to be addressed, please speak up. Thanks everyone for your efforts. |
Cycle 13 report
|
I would like to formally apply for this role.
|
@leo816 wrote:
Thanks, Leo. All, I think the process of handing this role off should include defining it more clearly. When we created this role, I took it on and started several initiatives to improve support. These included:
I've just updated and in some cases closed each of those projects to reflect their current state. The one outstanding project is rolling out the Bisq wiki. Would the new support team lead take over and own this project? What other regular duties would the support team lead carry out? Note that outside of the owning the projects mentioned above, the only duty I've been carrying out as the Support Team Lead is reviewing support team members' compensation requests. Nominally, I've been responsible for the support budget as well, but outside of compensation request reviews, the only budget-related action I've taken there is approving the recent proposal to normalize mediator and support agent compensation rates. Note also that the Donation Address Holder (burning man) and Arbitrator (refund agent) roles fall under the Support Team, so the support team lead needs to be on point for making sure things are going well with these critical roles, checking the accounting for their reports, etc. I'd like to hear from members of the @bisq-network/support team what they would want to see from a team lead going forward. I have spent very little time on the role outside of the projects and duties mentioned above, and I wouldn't want to hand the role off in its current state assuming that it's the way things should be. And I'd like to open up the candidacy for this role to anyone who thinks they would be a good fit for it. It's true that Leo and I have talked about him owning the role a number of times, but it's actually not a decision that I want to make on my own; if you're interested in owning this role, please speak up and make a case why you'd be a good fit, what you'd want to get done, how you'd expect to be compensated, etc. The best way to do this would be to create a proposal issue titled "@Yourusername to assume Support Team Lead role" and to include in the description of that issue why you're a good fit, etc. We can then vote on any such issues in the next cycle. In any case, the first task for whoever owns the role should be to update the Support Team Lead wiki documentation to reflect what owning the role will look like going forward. |
Almost all of the criteria for delivery for the wiki is complete, and in the current state is already very helpful. In a few weeks I think it could be considered ready for delivery. |
I've added these two duties that I think the Support Team Lead should have:
|
Per the approval of bisq-network/proposals#230, I have un-assigned myself as owner of this role, and assigned @leo816 as the new owner. @leo816, please go ahead with cycle reports here starting in the current cycle (14). Cheers! |
Cycle 14 report
|
Where? |
On the keybase bisq.support subteam keybase://chat/bisq.support#general/2535 |
Cycle 15
|
Cycle 16When support tickets are closed and then reopened I find users can receive my messages but can't answer back on most cases. This is an issue when funds get stuck on the multisig and I need to get both party's private keys or we are trying to get hold of a user who may have received the wrong payout. I edited some parts about the private key on the Manual Payout that were missing on the Bisq.wiki |
It's not possible to write messages for tickets that have been closed. To reopen a ticket the shortcut ctrl+u has to be used which reopens the ticket but it doesn't reload the ticket view. If the user has no other tickets they need to restart their application after doing ctrl+u to get a field to enter messages. |
@leo816 FYI bisq-network/bisq#4446 implemented lots of improvements. |
Cycle 45 ReportThe number of cases this cycle has decreased from last cycle's ATH. 184 mediation tickets this cycle whereas on the previous one we reached a maximum of 280. Number of manual payouts have increased.
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 46 ReportThe number of mediation tickets this cycle has remained stable after the decrease from last cycle's. 101 mediation tickets on my end, waiting for Pazza's but the total amount should be quite far from this two cycles ago when we reached a maximum of 280. Number of manual payouts have remained stable with 3 on my end and - from Pazza.
Main points from this cycle:
There are other applicants but under review as there is no need to add more people to the team. Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 47 ReportThe number of mediation tickets this cycle has increased from last cycle's. 102 closed mediation tickets on my end, but +45 open, on pazza's side he has also experienced an increase with 128 and 27 open that means a total 303 which is a reasonable increase, mainly due to the network congestion which has left some users with their trades on the mempool until today. Number of manual payouts have remained stable with 2 on my end and 1 from Pazza.
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 48 ReportThe number of mediation tickets this cycle has decreased from last cycle's.
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 49 ReportThe number of mediation tickets this cycle has increased from last cycle's.
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 50 ReportThe number of mediation tickets this cycle has increased from last cycle's.
One call with regards to different Bitcoin companies that have reached out since Miami to study potential synergies. Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 51 Report
One call with regards to different Bitcoin companies that have reached out since Miami to study potential synergies. Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 52 & 53 ReportCycle 52 Cycle 53 The high decrease in mediation cases on Cycle 53 is mainly due to late reporting on cycle 52 which made the number much higher on the previous cycle and much lower on this one. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. If we add the open cases we have (66 tickets), the total number would go up.
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
|
Cycle 54 ReportCycle 54 The high increase in mediation cases on Cycle 53 is mainly due to late reporting on cycle 52 which made the number much lower on the previous one. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has decreased (34 tickets), the total number would go up. We have found a web editor for bisq 2 that can replace the previous role holder. Demo seems on point and we are closer than ever for the released.
Main points from this cycle:
Calls have been done through matrix as usual. Improving the bisq 2.0 wiki. Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
|
Cycle 55 ReportThe number of mediation tickets this cycle has decreased from last cycle's. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has remained constant (33 tickets).
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand, no need to add extra members for now. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
|
Cycle 56 ReportThe number of mediation tickets this cycle has increased from last cycle's. On average we are doing around 120 mediation tickets a month each which means closing 4 tickets a day. The total number of open tickets has remained constant (33 tickets).
Main points from this cycle:
Regarding support requests, besides the data from the overall mediation tickets, support messages via different platforms have remained constant, bugs, comments, issues... etc. The support team is handling well the current demand, no need to add extra members for now. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
|
Cycle 57 ReportThe number of mediation tickets this cycle has increased from last cycle's. On average we are doing around 150 mediation tickets a month each which means closing 5 tickets a day. The total number of open tickets has also increased a little on my end (40 tickets). Out of the ordinary this cycle there have been two variables,
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day and the liquidity issue. Main points from this cycle:
Calls have been done through matrix as usual. Regarding support, we are at an all time high with mediation, bisq 2.0 has also required quite a lot of work. So I predict that we will shortly need new team members for the support team to keep up with the demand. So far support messages via different platforms have remained constant about bugs, comments, issues... etc. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
N of Issues cycle 56: 234
|
Cycle 58 ReportThe number of mediation tickets this cycle has decreased from last cycle's. On average we are doing around 145 mediation tickets a month each which means closing around 5 tickets a day. The total number of open tickets has also increased a little on my end (60 tickets). Out of the ordinary this cycle we've just had the number of manual payouts that has increased again to 35.
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day perfromance and the liquidity issue on bisq 2. Main points from this cycle:
Calls have been done through matrix as usual. Regarding support, we have experienced a decrease from last cycle's all time high mediation tickets, bisq 2.0 has also required quite a lot of work. So I predict that we will shortly need new team members for the support team to keep up with the demand. So far support messages via different platforms have remained constant about bugs, comments, issues... etc. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
N of Issues cycle 56: 234
N of Issues cycle 57: 195
|
Cycle 59 ReportThe number of mediation tickets this cycle has remained steady from last cycle's. The number of manual payouts has slightly increased from last cycle to a total of 29 this cycle On average we are doing around 145 mediation tickets a month each which means closing around 5 tickets a day. This cycle is a little below average although we are still missing the report from the new mediator which should increase that number Out of the ordinary this cycle we've had impersonators through all matrix channels that have created similar user ids and have sent private messages to people asking for their private key. We have made an effort responding as many messages as we could to get people to avoid these scammers but there is only so much we can do. In most cases they are not even in the bisq channels using those user names, so we can't kick them out of the rooms.
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day perfromance and the liquidity issue on bisq 2. Main points from this cycle:
Calls have been done through matrix as usual. Regarding support, we have experienced an increase in demand from the matrix channels and mediation tickets are very similar from last cycle's. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
N of Issues cycle 56: 234
N of Issues cycle 58: 195
|
Cycle 60 ReportThe number of mediation tickets this cycle has increased significantly from last cycle's. The number of manual payouts has slightly increased from last cycle to a total of +40 this cycle On average we are doing around 145 mediation tickets a month each which means closing around 5 tickets a day. This cycle is well above average although we are still missing the report from solomon which should increase that number to around double of what has been explained. This cycle was quite busy because of the bitcoinj bug, the decrease of btc and seed nodes that led to unsuccessful SPV and DAO resyncs. Therefore the number of messages and complaints we have received has gone through the roof this past month. We've had impersonators through all matrix channels as we did on the last cycle, usually dm'ing users privately and asking them to click on links as well as asking for users their private key. We have made an effort responding as many messages as we could to get people to avoid these scammers but there is only so much we can do. In most cases they are not even in the bisq channels using those user names, so we can't kick them out of the rooms.
I'm very proud of the support team we have developed and I trust that the next mediators will do an even better job. Thank you all, I will continue to contribute but slowly fade away for other people to take more responsibility.
We've had the support weekly calls as usual getting updates from all of the support team + some growth calls discussions regarding the market day perfromance and the liquidity issue on bisq 2. Main points from this cycle:
Calls have been done through matrix as usual. Regarding support, we have experienced an increase in demand from the matrix channels and mediation tickets are very similar from last cycle's. Analysis of Mediation Cases If I continue the mediation progression report, it would look like this: Click to see reportMediation Issues ReportN of Issues cycle 15: 85
N of Issues cycle 16: 111 44 Wiz
N of Issues cycle 17: 128 52 Wiz
Summary: the btc seller took longer to respond/ confirm the payment for N of Issues cycle 18: 89 31 Huey735
N of Issues cycle 19: 184 36 Huey735
N of Issues cycle 20: 160 82 Huey735
N of Issues cycle 21: 160 N of Issues cycle 22: 101
Report from cycle 21 was a late report instead of midcycle like usually, reason why the amount is significantly larger than in previous cycles. Mediation tickets seem like there are more to me but it's just because we are now just two mediators working instead of 3 or 4. N of Issues cycle 28: 107
N of Issues cycle 29: 139
N of Issues cycle 30: 104
N of Issues cycle 32: 117
N of Issues cycle 33: 147
N of Issues cycle 34: 136
N of Issues cycle 35: 200
N of Issues cycle 36: 193
N of Issues cycle 37: 192
N of Issues cycle 39: 223
N of Issues cycle 40: 143
N of Issues cycle 43: 273
N of Issues cycle 54: 270
N of Issues cycle 56: 234
N of Issues cycle 58: 195
N of Issues cycle 60: 217
|
Docs: https://bisq.wiki/Support_Team_Lead
Teams: @bisq-network/support, @bisq-network/team-leads
The text was updated successfully, but these errors were encountered: