Open cbeams opened 6 years ago
I have been available on Keybase support the following hours this cycle:
23.00 - 02.00 UTC Friday evening - Saturday morning 23.00 - 02.00 UTC Saturday evening - Sunday morning 23.00 - 03.00 UTC Sunday evening - Monday morning
Also jumped in at other times when I was available.
I have participated with all but one of the support calls.
Trading has been quieter this cycle. Seems like trade volumes are down across the board of all exchanges.
I updated the https://bisq.wiki/User_support page and linked to it from the wiki home page to give users a place where the different supports options, and when they might use each can be viewed.
The java heap space error seems to have been causing a number of issues but hopefully this has now been resolved.
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages.
Assisted numerous users with fee reimbursements, failed trades, unable to confirm and funds shown as locked even after doing a resync. this cycle I've performed many manual payouts from trades that did not appear on my side as mediator and was able to contact users through keybase.
Been in constant communication with devs when issues occur.
Attended the Weekly support Calls
The java heap space error didn't allow me to reach some mediation tickets for a day.
Thanks to @leo816 for the opportunity :)
I have been available on Keybase support my usual hours this cycle plus some more when I had time.
I have participated in al the support calls that have taken place.
I have supported about 6-10 users this most that have been experiencing ghost locked funds. Most of the time it is due to a failed trade and the GUI showing a locked balance that has actually been spent. An SPV resync only helps in a couple of cases.
I have been replying to users regularly on Keybase, Reddit and Bisq Community forum.
This was my internship cycle. I worked from the hours of 1pm to 10pm PST. Cases were fewer than 10. 4 other agents came through for shorter shifts. There is more agents than cases. I understand better why there is a limit on agent hours. Looking forward to my next month as a full time Level 1 Agent.
My first month as a L1 Support Agent. I spent a lot of time helping customers via the Bisq support channel in keybase. Also helped a considerable number of users who were asking questions on github. My hours have been 1pm to 10pm PST. A few agents pass through and help. Their shifts are shorter. I think I'll eventually adopt this as there are not that many cases. I use the downtime to contribute code to the dev team. Looking forward to reducing my hours and channelling the time into more dev contributions until the support cases increase.
This my 2nd cycle working as an L1 Support Agent. There is still more agent hours than cases. The long hours are starting to get to me. I'm seriously considering cutting back my hours in the next cycle. Most of the work I've done has been on github and in the support channel. It is very helpful to have good documentation that I can direct the users to. I"m also contributing to Bisq via the dev team in my down time. The few cases are a sign of good work done by past agents. So Bisq has a constant stream of users as demonstrated by the growth team reports, however the support load because the users already know what to do. I'll be resting and also giving more of my time to the dev team, at least until a new wave of users come through seeking support.
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages.
Assisted numerous users with fee reimbursements, failed trades, unable to confirm and funds shown as locked even after doing a resync. this cycle I've performed many more manual payouts than most cycles from trades that did not appear on my side as mediator and was able to get all the needed information through users on keybase.
Been in constant communication with @jmacxx as the bridge between support and devs when issues occur.
Weekly support Calls, all took place this cycle except 1.
This is my first cycle reporting work done for support, although I have been on the team for 8 months.
8/14/2021 analyzed logs for PDPCJYFF
-> payout tx / wallet corrupted
8/18/2021 support call
8/22/2021 analyzed logs for WYJWT
missing payment details -> ShareBuyerPaymentAccountMessage not received
8/25/2021 support call
8/27/2021 analyzed logs for 2281113
-> missing payment details -> resulted in PR to fix issue PR5679
9/1/2021 support call
9/4/2021 analyzed log for FP0X8JAP
-> missing payment details
9/7/2021 analyzed log for yxqxwres
9/8/2021 support call
9/9/2021 analyzed logs for f3Xqel
-> maker/seller computer locked up 6 minutes due to Tor problems, trade timed out
9/10/2021 analyzed logs for f3Xqel
again -> DepositTxAndDelayedPayoutTxMessage does not arrive at taker/buyer.
9/13/2021 analyzed logs for TradeId 7377735
(missing payment details)
9/17/2021 analyzed logs for UvIoKX
and oatsu4q
(BitcoinJ wallet out of sync)
Now that the victim repayments have completed, the fee addresses should be stable and we can re-enable the feature that validates transactions and fees prior to trading. (It was turned off a few months ago because changing the fee addresses caused some user's offers to be disabled). This should reduce the number of failed trades caused when BitcoinJ gets out of sync.
This is my second cycle as a L1 support agent.
Following a summary of the cases I had during my shifts (not so much actually):
I have also joined all the weekly support calls.
Thanks for this opportunity!
I have been available on Keybase support my usual hours this cycle.
I have joined in all but one of the weekly support calls.
It has been a pretty busy cycle for support. This month I have supported about over 30 users via PM in Keybase as well as other in the support channel, Reddit and Bisq community forum.
There were a few support tickets as a result of Tor 3 onion address upgrades but these all seem to be resolved.
I also started this month trying to help with the Support repository on GutHub by responding to compensation requests and closing old ones that were non responsive or had been settled/rejected.
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages.
Assisted numerous users with fee reimbursements, failed trades, unable to confirm and funds shown as locked even after doing a resync.
Been in constant communication with devs when issues occur.
Weekly support Calls, all took place this cycle except 1.
the main BUGS for this cycle are:
- Banking Issues
Banks not accepting payments, Monthly payment limit allowed, Making a payment from the wrong account.
- Messages not arriving to peer
It seems it has to do with the Hibernating mode, currently preparing a fix to solve this.
- Funds showing as locked when the trade fails: SPV resync doesn't always fix this, when this happens the easiest is to delete the ClosedTrades and FailedTrades files in the db folder.
- BTC seller being unable to confirm that they received the payment or stuck in stage 2.:
This issue has been fixed for the most part, all problems with users not being able to move from stage 2 to 3 have to do with the payment period having expired
Not so much support tickets to answer during my shifts, basically usual questions.
I hope one day to be maybe a mediator :)
Thanks!
Support for me has seemed a little quieter this cycle, but still supported the same amount of users in Keybase via PM as last cycle (30). I have been available on Keybase support for my usual hours.
Active on here, Keybase, Reddit and the Bisq community forum to support users as required.
Joined in all the weekly support calls.
Most issues were general support queries that were quickly resolved.
In addition to second level support, I've been spending time assisting users on keybase.
9/22/2021 support team meeting 9/24/2021 analyzed logs for 5918604 and czcgg resulting in https://github.com/bisq-network/bisq/issues/5725 9/27/2021 analyzed logs for 9186044 locked up funds from a failed trade 9/30/2021 looked into issue https://github.com/bisq-network/bisq/issues/5494 eventually came up with a fix 10/2/2021 looked into an issue with flailing offer count. (ended up being incorrect system time affecting Tor) 10/6/2021 support team meeting 10/7/2021 supported a user reporting problems with their bisq wallet receiving & address gaps 10/13/2021 support team meeting 10/17/2021 supported a user having problems DAO resync (https://github.com/bisq-network/bisq/issues/3094#issuecomment-945322947)
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages.
Been in constant communication with devs when issues occur.
Hosted the weekly support call, were we discussed the main issues and reported bugs.
This cycle I have supported 35 users in Keybase in my DMs. I have also been active in Keybase support, Reddit and the Bisq community forum.
I think I managed to make it to all the weekly support calls this cycle.
I feel support is working well. Users are being responded too quickly and there is good communication between everyone in the support team.
I am looking forward to the GUI locked funds issue being sorted as that will save many support hours each month and make for a better user experience.
In addition to second level support, I've been spending time assisting users on keybase and github.
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages. This cycle I've assisted more than 25 users, most of them having to do with mediations but some just regarding usability.
Been in constant communication with devs when issues occur.
Hosted the weekly support call, were we discussed the main issues and reported bugs. https://github.com/bisq-network/support/issues/916#issuecomment-972308140
In the last two cycles support chat has been quieter (around 3-4 cases per week). Unfortunately also I did not have much free time to dedicate to support apart from my shifts, but now I should be more available I hope.
Thanks!
My internship cycle. Following are the unedited notes I've taken during this time for my contribution, I started very detailed but then became way more essential with the granularity of the report. I have patrolled heavily keybase, attentively the forum, and been available also on reddit and github. I'd love to also help in the telegram group, but have had no luck until now with the many free "receive authentication SMS" services around to create another tg account specifically for bisq; if this continues, I might just cave in and use one of my existing accounts.
Welcome, @w0000000t!
In addition to second level support, I've been spending time assisting users on keybase and github.
Been available on Keybase from 7:30pm - 9:30pm Monday to Sunday. But active all day answering messages. Most of them having to do with mediation disputes.
Been in constant communication with devs and collecting logs when issues occur.
Hosted the weekly support call, there we discussed the main issues and reported bugs. https://github.com/bisq-network/support/issues/916#issuecomment-989140976
notes: @jmacxx and @w0000000t I like the detailed format you have given to your reports. Tomorrow at the weekly call we should talk about creating a template and applying this for all of our reports so that they are represented in the same manner.
All is going well with Bisq support.
I have supported 44 users on Keybase since my last update. This is a mix of people where I am their mediator but also people with other issues or questions related to Bisq.
I have also been replying to people on Bisq community forum but often @w0000000t has beat me too it :)
I have also been replying to users on Bisq sub reddit as well as discussion related to Bisq in general on Reddit.
I attended all but one of the weekly support calls this cycle.
I am really happy with how everything is going with support and feel that the high majority of Bisq users are getting a good customer support service when needed.
I am making a concerted effort to categorize the support request that come in to see what the important things are to action.
As per last weekly call, here's the gist for the proposed template of this thread (my own template for Cycle 32, which I tidied up for the occasion): https://gist.github.com/w0000000t/81ee4fccf4c9c4647abcdc57d51d730e
Support activity on keybase, matrix, forum, telegram, reddit, github (limited to what I can deal with). "Case" (C): support situation requiring 10+ minutes of assistance "Request" (R): support situation requiring from a single to a few replies
In addition to second level support, I've been spending time assisting users on keybase and github.
I had a quieter support cycle than usual this month. I think it was a little quieter in general due to the holidays.
Examples of support queries are:
Everything is going well no issues were unresolvable. Focus this month for me will be moving things and users over to Matrix.
@leo816, could you have a look at the @bisq-network/l1-support-agents team and add/remove members as necessary? I'll update the list of assignees to this issue to reflect when complete. Thanks.
Support activity on keybase, matrix, forum, telegram, reddit, github (limited to what I can deal with). "Case" (C): support situation requiring 10+ minutes of assistance "Request" (R): support situation requiring from a single to a few replies
Autogenerated with Bisq support agent report script "Case" (C): support situation requiring 10+ minutes of assistance "Request" (R): support situation requiring from a single to a few replies "Ban" (B): usually done on Telegram "Call": meeting call for support agents, or other
Second level support on matrix and github.
Buyer not responding to a trade in mediation Assisting users to do a manual payout Missing funds in wallet - spv resync required Questions about mediation Questions about Bisq trading process. Supported user in moving to new data directory. Supported user with failed trade concerned about loss of funds (no loss of funds occurred). Supported user with questions about arbitration.
notes: Transition to Matrix was successful. We keep improving week over week as a support team and with communication. Looking forward to increase the team members as bisq2.0 comes to place.
Case (C): support situation requiring 10+ minutes of assistance Request (R): support situation requiring from a single to a few replies Example: 2022/01/01 2R [two requests] matrix; 1C keybase (user had problem X, suggested to do Y and Z, problem was solved)
Details
All is going well with support. Weekly calls are really helpful and the Matrix support team room is regularly utilized.
Been gradually moving things over to Matrix. Pinned a few posts in the Keybase chat to advise community members to move to Matrix. Keybase is pretty quiet now with most discussion activity occurring in Matrix.
Autogenerated with Bisq support agent report script "Case" (C): support situation requiring 10+ minutes of assistance "Request" (R): support situation requiring from a single to a few replies "Ban" (B): Telegram s(p|c)ammers "Call": meeting call for support agents, or other
164 requests 9 cases 103 TG bans
Most active: TGram friday 17-19 UTC
Support is going well.
Very few activity in the Keybase rooms now. Still the odd DM from previous users I have supported though asking questions or requiring assistance.
@w0000000t 103 telegram bans LOL. I knew there were a lot but seeing the exact numbers... That's very ugly, Telegram should add captcha as an option directly from Telegram (no bots) before joining groups.
Second level support on matrix and github.
Support is going well, the support team is handling well as of right now with all the support issues popping up. Not much activity on keybase but some users still reach out through there, so taking a look every now and then.
notes: I've had to do several manual payouts and a few cases that took more work than usual. I created 2 proposals but will have them laid out on the support team lead report
Autogenerated with Bisq support agent report script "Case" (C): support situation requiring 10+ minutes of assistance "Request" (R): support situation requiring from a single to a few replies "Ban" (B): Telegram s(p|c)ammers "Call": meeting call for support agents, or other
Stats collected since 2022-03-22
170 requests 13 cases 57 TG bans
Most active: TGram thursday 17-19 UTC
Support is going well.
Almost all support discussion now taking place on Matrix.
Support activity on ... ["keybase", "matrix", "forum", "telegram", "reddit", "github"]
Case (C): support situation requiring 10+ minutes of assistance Request (R): support situation requiring from a single to a few replies Example: 2022/01/01 2R [two requests] matrix; 1C keybase (user had problem X, suggested to do Y and Z, problem was solved)
Details
To do: Improve wiki BSQ and connectivity issues.
Docs: https://bisq.wiki/Support_Agent Team: @bisq-network/l1-support-agents