When something goes wrong: disputes and tickets
Most tasks go smoothly. When one does not, a person on our team steps in, not an automated rule. There are two routes, and choosing the right one gets you an answer sooner.
- A dispute is about one rejected submission, between the tasker and the advertiser.
- A ticket is for everything else: a payment that has not arrived, a withdrawal that seems stuck, a suspension you think is wrong, or something that looks broken.
Disputes
If your work was rejected and you think it should not have been, you can dispute it within 72 hours of the rejection. Disputes are for taskers challenging a rejection; an advertiser who thinks work passed wrongly should open a ticket instead.
A dispute is one shared conversation between the tasker, the advertiser and an administrator. Everyone in it can write and read the whole thread, and the proof that was sent is shown there too. The advertiser appears by the name they chose for taskers, or simply as the advertiser, and emails and phone numbers cannot be posted. Evidence settles it: the campaign's instructions, the proof as sent and the reason given. Exact times and the original screenshots help far more than "they are lying".
The administrator's decision is final, and the money follows it straight away:
- For the tasker: the tasker is paid from the campaign's budget, just as if the work had been approved.
- For the advertiser: the rejection stands, and the advertiser pays nothing for it.
Tickets
A ticket that gets a quick answer sticks to one subject and says which campaign, task or payment it is about. Every campaign, task, deposit, withdrawal and dispute has a short code on its page, such as CMP-7F3A9C21: Ask Support about this on that page opens a ticket with it already chosen, or choose it on the ticket form yourself, from your own or by pasting its code. Then add the amount, the time, and what you expected against what happened. Copy any error message into the ticket word for word. A suspended account can still open a ticket.
Nobody from Taskerise will ever ask for your password or a two-factor code.
The best dispute is the one you avoid
Advertisers: write briefs and rejection reasons someone can act on. Taskers: read the whole task before you take it. It saves everyone time.