GET STARTED

Signup. To use requests you will need to signup. You can signup whenever the app is running, on this website, on 3'rd party sites on on mobile app. Signup is easy and does not takes more than 2 minutes of your time.
Setup user profile. Upon signup you will be taken automatically to profile setup view. Specifying correct details such as phone and possibly other contact details is necessary for successful interaction between helper and requester.
Using the app. Once you signed-up you can post requests, help others by responding to their requests, or do both. Posting requests is free. Only helpers pay for using the app as explained below. Of course you will have to pay to helper for their help according to agreed offer set for request, but this is between you two and Requests app is not a side in this deal.
Paying for use. Once helper lock a request we log a $1 Request-Handling-Fee (RHF) commission in helper's wallet. Note that this fee persist also if helper is rejected or if decided to abandon the request. This helps us to prevent from helpers to lock requests they are not qualified to handle. We check helper's wallet monthly and if total usage amount greater than minimum amount (currently stand on $10), or if 3 months passed since last bill, we generate payment-request.
PrePay. A PrePay option is also available and has the benefit of getting a bonus (currently stand on 25% of paid amount) once payment received. PrePay method may be good choice for helpers that work on many requests. It is not recommended for new users. You don't have to wait for billing cycle to end, you can do the prepay at any time and your wallet balance will be adjusted accordingly.
 
 

Request Life-Cycle

Request life cycle. Whether you are helper or requester it is important to understand the life cycle of requests and what is expected in each phases.

  • Pending - the request is pending when it is just created. During the pending phase all helpers can view your request and try to lock the request for suggesting help. During the pending state, the requester case still edit request details. Pending requests should include ar least description and pay offer, which is the amount a requester is willing to pay for get help.
  • Pending-Approval - to handle a request, an helper set the bid price (that may be the same as pay offer) and "lock" a request. This puts the request in the pending-approval state. The first that lock win the prize. A pending-approval request stopped from being presented to other helpers, and in case that other helper has try to lock the request too, the operation deny. The requester is notified and require to either "accept" of "reject" the helper. If requester reject the helper, the request return to "pending" state.
  • In-process - when helper approved by request, request status change to 'in-process'. During this phase, Helper and Request contact each other, using their profile details (this is what make profile details so important) and collaborate for working on the issue specified by request. Parties may collaborate using any approach they find to be convinient. They can use tools provided by the requests app, but will probably want to use additional tools too. Requests does not dictate the collaboration course. Instead it aim to provide a content-glass based collaboration tools as part of its evolution. Using these tools is optional.

    Note that it may happen that parties does not manage to solve the issue. To allow a request to be available for other helpers, the helper may abandon the request. Abandoning the request will put it back in the pending mode.

  • Pending-Payment - when request task is completed, Helper sends a notification for request to make payment. The status of request changed to pending-payment. The requester is now required to pay to helper the agreed amount set upon accepting the helper. We provide a payment link together with helper's notification for paying using PayPal. This payment method is optional, and payment may performed on any platform agreed by parties.

Create Request

 

Supported Environment and Browsers

Requests is a web app, designed to run on modern updated browsers. Requests can be used directly from browser, or in the future as an app.  The information below shows current support and status.  

Windows

Chrome: supported

Opera: supported

Firefox: supported

Edge: supported (require more tests)

Other browsers: NOT TESTED.

Generally chromium based browsers, with an updated  chromium version should work. To test chromium version you can use https://chromiumchecker.com or open developer console (if you know how) and type:

navigator.userAgent

Then you will see something like: 

'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36 OPR/81.0.4196.37'

In this case: Chrome/95.0 is the actual version of chromium. However since chromium, is a platform for creating custom browsers, you may see that actual brand version is different. For example in this case above this is opera 81.

 

 

Android

Browsers

Chrome: supported, under testing

Opera touch: supported, under testing

Other: not tested yet

* we assume browser is updated

Android App:

Requests Content Glass

Status:  Experimental, internal version 1.1.3,  under testing. 

Download: Link to download can be found on download page. 

 

iOS

Browsers

Chrome: Currently NOT SUPPORTED

Safari: Currently NOT SUPPORTED,

a problem was detected with loading on user data. In progress. Problem was inspected with iPad and iPhone 8 iOS 14.6

App

Status: NOT IMPLEMENTED. Will be implemented in the future. 

 

 

Linux

Not tested yet.