L1 Support Agent #64
Comments
|
@alexej996, I've assigned you to this new role, as you have in fact been doing this kind of 'Support Staff' work in addition to your Forum Operator (#19) role. As mentioned in the description above, it would be good if we can get an additional couple people helping you with this work in a dedicated way. If there are frequent forum contributors you'd like to invite to take this on, please do! |
2018.01 reportThis month was all about support. With the timeout and transaction broadcast failure bugs in v0.6.3 and v0.6.4, we had around 60 total reimbursements to handle over the last month or so. In the process, we created the https://github.com/bisq-network/support repository, including the reimbursements project board at https://github.com/bisq-network/support/projects/1, all of which made a big difference in managing all this stuff. We came up with the process detailed in https://github.com/bisq-network/support#35 for how to deal with these reimbursements in a very efficient way, and in the end I think it's safe to say that users have been happy with the service they got. I've been keeping a collection of the heartfelt thank-you emails I've gotten after people got their reimbursements back. I have about a half-dozen now, which sort of makes it all worth it. I figure for every one of those I get, there's probably another few people at least who are really happy, but just didn't write anything about it. There have been zero upset or dissatisfied users in this process, so far as I know. I won't be able to do support like that for much longer into the future, and hopefully we won't need it in such an intense way any time soon, but it's a good thing that we have systems and processes in place for dealing with this stuff if and when it does come back up. As Bisq really grows, we'll need people doing one kind of support or another all day long. It would be great to have some of those people get started now. I've been thinking actually, that we might want to reach out via Twitter, Reddit, and elsewhere to up and coming Bitcoin developers who want to get their hands dirty with a real Bitcoin project by helping support its users. I still learn stuff every day when I do this work, it's an amazing education, really. |
2018.02 reportThis month was much lighter support-wise, but there were still a handful of reimbursements to process, and I still haven't gotten to them. There were also several out-of-the ordinary support requests that took special handling from me and @ManfredKarrer. In general, I struggled to keep on top of support issues this month, and I don't foresee the situation getting better. This role needs to be transitioned soon to people who can care for it. By this time next month, I will get out a recruiting communication out about the opportunity of contributing support work for Bisq. In particular, I think we can reach out to smart and capable, technical people who are still relatively new to Bitcoin but want to get involved deeply with it. These people would have a lot to gain from doing support work for Bisq. They would be required to learn about Bisq (and therefore many aspects of Bitcoin) in a deep way—so deep that they end up being able to address virtually any problem that comes up for users. This would be an excellent, apprenticeship-style approach to building technical skills with Bitcoin. The ideal arrangement would be working with young developers who naturally evolve from doing support work to fixing simple bugs that they encounter in support issues, to taking on larger and larger development responsibilities, eventually training other new developers how to do support and transitioning themselves on to dedicated dev work. |
2018.03 reportFrom last month's update:
I sent out the following tweets to this effect, and we'll see what comes of them. About 10 people joined our Slack workspace right afterward, and some conversations have started. From https://twitter.com/bisq_network/status/981216134220468224:
Otherwise, support efforts were fairly light this month. There have been 10 or so new reimbursement issues, and I'll issue the next batch reimbursement for them in bisq-network/support#76 later this week. Many thanks to @alexej996 for continuing to do excellent first-line support on the Bisq Forum. I very rarely have to check anything there myself these days. |
2018.04 report@cbeams serviced a batch reimbursement (bisq-network/support#76) this month. @alexej996 continues to do first-line support via the Bisq Forum, and for the most part, I never see escalations, which I take to mean that he fully resolves most issues that come up there. @alexej996, going forward I'd like to draw a clean separation between the Forum Operator role (#19) and the Support Staff role. You're playing both of these roles, and you've been reporting on the Forum Operator role every month, which is great, but could you begin reporting here every month too? I think what we want to see in from reporting on this role is information about how many support requests we're getting every month, what kind of common issues people are running into, etc. I realize this isn't very specific what I'm saying here, and we can talk further about it, but my main point is that since you're actually our main support staff right now, it would be good to have you reporting on how it's going here, and helping raise awareness about what's missing / what's trending / what we need. I'd like to have you take the primary position here, and I'll take a backseat as secondary, and stop doing monthly reports on my side. Let me know if this works for you, thanks. |
|
Sure. I will think of something when it comes to writing monthly reports for this role in the future. |
|
Thanks, @alexej996. I've updated the description to reflect that you're primary now. |
|
See my comments on this role in the context of @alexej996's current monthly compensation request at bisq-network/compensation#60 (comment) |
2018.5 updateOne of most common issues users always seemed to have on the forum are timeouts when taking offers and lost trading fees as a result. Since these times of issues are handled and refunded by Chris, I usually just advise them to contact him, although Manfred stepped in for one of these this month. There were multiple users on the forum getting exceptions regarding duplicate transactions in their wallets. Manfred also assisted on this one and these users seemed to recover their funds successfully. There were some general questions about some payment methods on the forum this month that @alfsbs agreed to answer, since I wasn't familiar with them. He was really helpful about this. We also had users trying to recover their funds from their older Bisq wallets that used Dash as a base currency. We also had some people asking general questions about development and running on CentOS. Users also seem to be asking for some features commonly, such as fiat fixed offers and chatting between traders. There is also one user on reddit asking about identity verification during the dispute process and why it is necessary, I wasn't really able to answer that question for him as I am generally not that familiar with the fiat side of things. |
|
Hello support staff !, |
|
That sounds great to me :) Come and help out whenever you can and you can request a compensation at the end of the month. I don't really have any specific times I am not available, but I am usually around in the 12:00-02:00 GMT interval. |
|
As a general note to @HarryMacfinned and anyone else who wishes to perform support services in the future, there's really no permission required. Simply help people out in whichever forums and channels you choose, and then submit a compensation request at the end of the month with links to your work. The first few times around, you'll want to be explicit in your compensation requests, linking to as many of your support interactions as possible. As the months go by, and you build a reputation, it will be less necessary to link to everything, and you can start to report more in the aggregate, much as @alexej996 does now. In the beginning, though, everyone will want to know whether the kind of support you're providing is the kind of support we as stakeholders want to reward with BSQ, so folks will want to review your links as a way of figuring that out. |
|
For Cycle 65 Summary of contributions: Detail log of support workNovember 8 Matrix: Support ACH Transfer issues November 8 Matrix: Support Trade error / SPV Resync November 8 Matrix: Support payment for trade not yet received November 8 Matrix: First BTC Room large trade recommendations November 9 Matrix: Support CBM trade discussion November 10 Telegram: Bisq waiting for confirmation/SPV resync November 10 Telegram: Bisq Bisq 2 not showing payment confirmaiton button November 11 Matrix: General Money order trade questions November 12 Matrix: Support DAO resync/seed node discussion November 12 Matrix: Support issues getting 4 BTC node connections November 12 Matrix: Support unable to send payment/seller account closed November 12 Matrix: Support spv resync stuck / no BTC connections November 13 Matrix: Support moving data folder from win to ubuntu November 13 Matrix: General ACH discussion November 13 Matrix: Support Call active on support call November 14 Matrix: Support banking issues with trade November 14 Matrix: Contrib Internal attended contributor call November 14 Matrix: Support sent payment from wrong account November 14 Bisq 2: Support->Assistance burning bsq/dust limit November 15 Matrix: DM bisq 2 vs bisq 1 discussion November 15 Matrix: Support revtag question November 16 Matrix: Support finding mediator November 16 Matrix: Support seller wants to cancel trade November 16 Matrix: First BTC Room bisq 2 vs 1 discussion November 16 Matrix: General scammer November 16 Matrix: General support room link November 17 Matrix: Support connection problems during spv resync November 17 Matrix: Support null deposit tx showing up November 17 Matrix: Support zelle issue November 18 Matrix: Support finding mediator November 18 Matrix: General vlcash by mail discussion November 19 Matrix: Support locate app dir in win November 19 Matrix: Support reserved funds question November 19 Telegram: Bisq spam November 19 Matrix: Support finding your mediator November 19 Matrix: Support bank not displaying name from payment November 19 Matrix: Support connection issues November 19 Bisq 2: Support->Assistance reputation discussion November 19 Matrix: Support scammer warning November 20 Matrix: Support Call active on support call November 22 Matrix: Support scammer discussion November 26 Matrix: Support unable to complete zelle trade November 26 Matrix: Support xmr trade stuck on step 1 / spv reaync November 26 Matrix: Support version 1.9.18 info November 26 Matrix: Support Call active on support call November 27 Matrix: DM bisq 2 password December 1 Matrix: Support strike as a payment option December 1 Matrix: Support Linux bugs on 1.9.18 December 1 Matrix: Support incomplete spv resync December 1 Matrix: Support zelle account names December 2 Matrix: Support dispute/finding mediator December 4 Matrix: Support suspected scammer December 4 Matrix: Support Call active on support call December 5 Matrix: Support missing deposit tx December 5 Bisq 2: Support->Assistance only able to take offer once December 5 Matrix: Support reputation December 5 Matrix: Support arbitration December 5 Matrix: Support zelle issues December 6 Matrix: Support dispute process December 7 Matrix: Support tails install December 9 Matrix: Support sending bsq to another instance |
Cycle 66Approximated event volume over last 6 cycles (older to newer, 4679blocks ~ 32.5days per cycle going back from today): Following the sharp increase of support volume given during the last two cycles, I will adjust this cycle's CR amounts accordingly. Cycle 66 saw an increase of:
Discounted increases in CR amounts will be:
List of 203 Bisq1 support actions
List of 132 Bisq2 support/moderation actions
|
Cycle 66I supported 39 users on Matrix Attended team meetings this cycle. Still need to action
Additional infoReport07.12.24 Old arbitration question |
Cycle 66 ReportThis cycle:
Detail log of support issues I assisted with:December 10 Matrix: Support trade fee reimbursementDecember 10 Matrix: General cash by mail/money order accounts in bisq December 10 Matrix: Support missing btc after spv resync December 11 Matrix: Support buyer wrote btc in reason for payment December 11 Matrix: DM bisq 1 ach trade policies December 11 Matrix: Support error connecting to seed node on tails install December 12 Matrix: Support SPV loop December 12 Matrix: Support CBM and MO questions December 12 Matrix: General Seller received chargeback request December 12 Matrix: Support spv resync December 13 Matrix: Support Seller hasn't confirmed payment/time still left in trade December 13 Matrix: Support Buyer hasn't sent payment for trade/time almost up December 13 Matrix: Support More discussion on custom tails install December 14 Matrix: Support Trade penalties December 15 Matrix: Support Zelle limits December 15 Matrix: Support Bisq 1 reputation December 18 Matrix: Support Payment not received/time running out December 18 Matrix: DM ACH trade questions December 19 Matrix: Support opening support ticket/mediation December 20 Matrix: Support banking issue with sepa transfer December 22 Matrix: Support Bisq 1 vs Bisq 2 December 22 Matrix: Support verify bisq download/expired pgp signature December 23 Matrix: Support stand alone zelle app December 23 Matrix: Support failed trade/spv resync December 24 Matrix: General zelle changes December 25 Matrix: Support account signing December 26 Matrix: General failed trade / spv resync December 27 Matrix: Support zelle payment from different name. December 27 Matrix: Support multiple zelle accounts as seller December 27 Matrix: Support money order trade questions December 27 Bisq Easy: USD Market questions about money order/cash trades December 28 Matrix: General request for sats view within bisq December 28 Matrix: Support address format exception when trying to send btc December 30 Matrix: Support oom on spv resync December 30 Matrix: General tax discussion December 31 Matrix: Support bisq 2 message delivery issues December 31 Matrix: Support account signing question December 31 Matrix: Support banking/zelle issues December 31 Bisq Easy: USD Market XMR trades December 31 Matrix: General connecting own BTC node December 31 Matrix: Support xmr trade questions December 31 Matrix: Support can not see seller info January 2 Bisq Easy: USD Market larger ACH trades January 2 Matrix: Support Support reply times January 2 Matrix: Support safe to close with offer taken January 3 Matrix: Support Portfolio history filter January 4 Matrix: Support trade stuck/spv resync January 4 Matrix: First BTC Room bisq easy to get started January 4 Matrix: Support ln implementation January 4 Matrix: DM selling bsq/dust limits January 5 Matrix: Support restore old wallet January 5 Matrix: Support seller not release funds January 5 Matrix: Support trade rules/penalties January 6 Matrix: Support dispute process January 7 Matrix: Support bank limits not allowing fiat payment January 7 Matrix: Support mediation/dispute process January 8 Matrix: DM bisq 2 initial data not loading January 8 Matrix: Support BSQ January 8 Matrix: Support scammer January 8 Matrix: Support seller confirmed in chat but not trade screen January 8 Matrix: Support Trade penalties |
Cycle 66I have not been very active during Christmas, so I have decided to reduce my compensation request. Items10 |
Cycle 66
Here is a more detailed review of my work: Click to see report15.12.24 - Reported scammer |
pazza83
assigned luis3672, strayorigin, suddenwhipvapor and darawhelan and unassigned wiz, huey735, leo816 and Bayernatoor
Cycle 67Approximated event volume over last 6 cycles (older to newer, 4679blocks ~ 32.5days per cycle going back from today): Bisq1 events were the same amount as previous report (203 vs 202), maintaining same CR amount as last cycle (1020$) Bisq2 events were 37% over baseline, increasing base compensation by 25% (600$ => 750$) List of 202 Bisq1 support actions
List of 123 Bisq2 support/moderation actions
|
Cycle 67I supported 41 users on Matrix Active on Bisq Forum Attended team meetings this cycle. Still need to action
Additional infoReport06.01.25 Arbitration questions |
Cycle 67Beginning of the cycle was quite slow, then back to normal. Items10 |
Cycle 67
Here is a more detailed review of my work: Click to see report14.01.25 - Matrix: User never accepted the mediation proposal and trade went to arbitration |
Cycle 67 ReportThis cycle:
Detail log of support issues I assisted with:January 9 Matrix: Support MacOS installJanuary 14 Matrix: Support Mediator NA January 15 Bisq 2: Discussions->Bisq Zelle locked account January 15 Matrix: General cashapp for us sellers January 15 Matrix: General Bisq 2 January 16 Matrix: General Trade periods for different payment methods January 16 Matrix: General opening mediation / time left on trade January 17 Matrix: Support disputes received on wise January 17 Matrix: Support responding to financial institutions January 17 Bisq 2: EUR Market trading 2500 EUR January 17 Bisq 2: EUR Market max trade limits January 17 Bisq 2: EUR Market buyer privacy January 17 Matrix: Support sending payment to other account January 17 Matrix: DM chargeback/scammer discussion January 18 Matrix: Support bisq easy recommended January 18 Matrix: Support off site communication/trades January 19 Matrix: DM wallet not showing correct balance January 20 Matrix: Support payment will arrive after trade period January 20 Matrix: DM sepa scammer discussion January 21 Matrix: General active mods January 21 Matrix: Support penalties January 21 Matrix: Support dispute process January 21 Matrix: Support chargeback discussion January 21 Matrix: Support f2f trades January 23 Matrix: DM Money order trade questions January 23 Matrix: DM account signing questions January 23 Matrix: Support cancelling a trade January 25 Matrix: First BTC Room Bisq 2 recommended to new seller January 25 Matrix: Support Bisq Easy limit January 26 Matrix: General Veruv link dead January 27 Bisq 2: USD Market reputation January 27 Matrix: First BTC Room trade feedback January 27 Matrix: First BTC Room Bisq Easy recommendation January 28 Matrix: Support user can not see their own offers January 28 Matrix: Support support tickets February 3 Matrix: Support invalid tx / spv resync February 3 Matrix: Support failed trade February 4 Matrix: DM wallet balance issues/spv resync February 4 Matrix: Support unable to send messages from certain bisq 2 profile February 4 Matrix: Support contacting mediator February 4 Matrix: Support scammer warning February 4 Matrix: Support correct room for support February 4 Matrix: DM assisted user with github issue February 4 Matrix: Support AddressFormatException - taproot address February 5 Matrix: Support confirming Solomon as mediator February 5 Matrix: Support Bisq Easy security mechanisms February 5 Bisq 2: USD Market privacy notice February 6 Matrix: General wiki edit rights February 6 Matrix: General running own node/bind question February 6 Matrix: Support waiting for confirmation/spv resync February 6 Matrix: Support strike converted incoming USD to BTC February 7 Matrix: DM man in middle scam February 8 Matrix: General Bisq 2.1.5 bug February 8 Matrix: Support waiting for confirmation/spv resync February 8 Matrix: Support backing up data dir February 8 Bisq 2: USD Market seller history/rep discussion February 9 Telegram: Bisq doge spam February 11 Matrix: Support importing wallet into sparrow |
and others
Docs: https://bisq.wiki/Support_Agent
Team: @bisq-network/l1-support-agents
The text was updated successfully, but these errors were encountered: