Support Agent

Requirements

What makes a great support agent?

• You're a Bisq user. You understand how to use it well enough to help others.
• You can be available for 10 hours or more per week to handle support cases.
• You're familiar with the existing Docs and Knowledge Base articles.

If you're interested in becoming a support agent, see the #Internship section below.

Infrastructure

Includes all of Support Team#Infrastructure, plus the following:

Coverage calendar

The coverage calendar tracks shifts for each support agent, with the goal of achieving 24/7 coverage.

• Public HTML
• iCal File
• Google Calendar (login required)

Case tracking board

• https://github.com/bisq-network/support/projects/2

GitHub team

• @bisq-network/support-agents (includes l1, l2 and intern subteams)

Role issue

• L1 Support Agent #64

Duties

Handle support cases

If unable to solve the trade successfully you must gather the appropriate data before reaching out to a developer.

Required data to request support from developers:

• Create a directory with the trade ID as name
• Add a short description in a plain text file of the problem/bug. Use BTC buyer/BTC seller if you refer to any trader. Ask user when the issue happened so its easier to find the issue in the logs.
• Ask them if they have done anything non-standard or had past issues.
• Add all available trade tx IDs of both traders as plain text to the report.
• Get a screenshot of the trade details window (click on trade ID). Tell users to only blur out the payment account details but not the tx IDs or other data. There is no relevant privacy issue with exposing trade ID, tx IDs or onion address.
• Add a screenshot from the mediators dispute details window. The contract as json data is not required initially and only needed if the dev requests it. The payment account data in the json file should be removed before handing over to a dev to protect traders privacy.
• Get all log files from both users (at Account/Backup there is a button for opening the data dir) - its up to 11 files.
• Put all logs from one user into a directory named buyer and seller
• Add a screenshot of both traders first chat message (system message containing data like version number/OS,...)
• If there have been any error/warning popups request a screenshot of that as well.
• Zip all and send it in keybase as PM to a dev who has commited to work on it. Avoid adding it to the support channel as then nobody will feel responsible to work on it.

Rights

• Writer access to the bisq.support Keybase subteam
• Triage access to Support Team#Repositories
• Edit access to the #Coverage Calendar

Policies

Time to response

If you are on duty, it's your job to respond as promptly as possible to incoming user requests. The goal is to respond to all support inquiries in the #support channel within 1 hour of being asked and preferably much faster. This initial response need not actually resolve the user's issue, it is merely letting the user know that you've heard their question and that you'll be their primary support agent for this case.

Sensitive user data

Often support agents will need to ask users to share their logs with you or specific information about their offer or trade, such as trade ID, trade amounts, etc. This data should not be shared in any public channel and should be destroyed one month after the case is closed. Note that any such information that shared in the bisq.support subteam is automatically destroyed after 30 days.

Processes

Internship

Prospective support agents are asked to go through an internship process that lasts one DAO cycle (approximately one month). During this period, you'll perform the duties of a support agent, but your contributions won't be eligible for compensation. This gives you a chance to get to know the ropes and for all parties involved to determine whether a support agent role is a good fit for you.

1. Indicate in the #support channel that you're interested in interning as a Support Agent.
   • Say a bit about yourself and why you're interested in doing this work
   • Mention what days and times you'll be available to do this work
2. The Support Team Lead will then:
   • Add you to the @bisq-network/intern-support-agents team
   • Add your requested shifts to the support coverage calendar
   • Announce your internship:
     • with a message to the larger @bisq-network/support team
     • with a message in the #support channel
3. After one full cycle of interning
   • Submit a proposal to be added to the @bisq-network/l1-support-agents team
   • If your proposal is approved, the support team lead will promote you as per the process below.

Case tracking

Trade transaction structure

If there are any issues with transactions or doubt if the deposit or delayed payout tx is correct you can check it in a block explorer by following the transactions outputs.

There are 5 diff. txs:

• Maker fee tx
• Taker fee tx
• Deposit tx
• Delayed payout tx (only get broadcast when arbitration gets opened)
• Payout tx

The 2 trade fee txs have as first output the trade fee. That goes either to one of the BTC receiver addresses ([1] and [2]) or to a BSQ change address of the user in case BSQ was used for the fee (the diff from BSQ input and change output is used for miner fee and is the burned BSQ). The **second output of both trade fee txs must lead to the (same) deposit tx**. The deposit tx has an OpReturn and the first output is to a multiSig address (start with `3` if non-segwit or with `bc1` if segwit). There can be an optional change output if trade amount was smaller than max. offer amount, but there are never more then 2 outputs + opReturn. If the delayed payout tx or the normal payout tx was published you see that the first output of the deposit tx (the MS output) is spent and lead to one of those txs as the single input. The normal payout tx has exactly 2 outputs, 1 address for each trader and that addresses are dispayed in the trade/ticket details. The delayed payout tx need to have exactly 1 input and 1 output to one of the addresses listed in [1] and [3]. **If arbitration is opened this tx MUST exist otherwise a refund MUST NOT be made**. The input must be the multisig output of the deposit tx (we have a code to check if its the deposit tx of the trade and not any past one - if a popup in mediation or arbitration tells you that there is an issue, take it serious and contact devs for advice).

To check the txs (and addresses) use a block explorer which shows clearly the inputs and outputs, not all explorers have a very intuitive UI to follow the flows of txs. If you select the addresses like in the below screenshot you can see the flow pretty clearly.

Checking if the trade fee tx leads to the deposit tx helps to quickly see if the trade funds are locked up and all is ok with the trade. If that is not the case the traders might have lost trade fee (if their trade fee tx is published - if one side is missing that user has not lost trade fee so no fee reimbursement is justified, such users need to do a SPV resync as the tx is likely committed in their wallet but not in the mempool due to too low fees or a bug at broadcast).