Where contractor tickets come from in the HumanSignal Services journey, how I would triage and route them, what the public help centre and status page show, and a working desk that does it live.
The contractor's one point of contact. Enterprise Support serves the paying client; this desk keeps annotators, collectors and experts verified, paid, signed in and working, in every time zone.
Open contractor postings span 24 annotation countries across South and Southeast Asia, Africa and Latin America, 20 data-collection countries and 16 design markets. Most of the queue files outside North American working hours.
A desk that classifies a message into the help centre's own 20 ticket types, sets P0 to P3 with the reason shown, routes it, drafts a reply that links the right article, catches a payout cluster, maps live incidents to on-call, and audits the help centre live.
| Takeaway | Why it matters on the desk |
|---|---|
| Most tickets are a step in one journey | Sign-up, ID check, tax form, payout method, project, wallet, payout. Each step has its own ticket types, and the step tells you the owner. |
| Two policies drive the hardest replies | ID checks allow two attempts and staff cannot override the provider. Payouts run weekly and can take up to two weeks to land. Both need honest wording and a date. |
| Five similar tickets in 30 minutes is one incident | A failed payout run or an ID-provider outage shows up as many single tickets first. Grouping them early turns fifty replies into one P0, one handoff and one notice. |
| Self-service needs one answer per question | The public help centre answers several questions twice, sometimes differently. Consolidating those is the cheapest ticket reduction available. |
| Discord is a public room | Project questions belong there. Pay, identity and login details move to a private ticket, and the post is hidden. |
A platform company that added a services arm. The services arm brought a contractor workforce, and the workforce brought this role.
| Platform | Label Studio, the open-source labeling tool, and Label Studio Enterprise. Started in 2019 as Heartex, renamed HumanSignal in 2023, headquartered in San Francisco, Series A led by Redpoint in 2022. |
| Services | HumanSignal Services launched with the acquisition of Erud AI (announced 5 November 2025). It designs datasets, recruits domain experts and runs collection and evaluation projects on its own platform. |
| Contractor stack | Apply at onboard.humansignal.com; work at app.humansignal.com in a Label Studio Enterprise workforce organisation. ID check by a third-party provider (Trolley, with Veriff in some countries), then a W-8BEN or W-9, then PayPal or bank transfer. |
| Pay mechanics | Approved tasks reach a wallet after a weekly processing run. Bank transfers need a USD 35 balance and a Pay Me Now press; arrival can take up to two weeks by country and currency. |
| Channels | A Zendesk help centre and email for account and pay; Discord for project questions, training and announcements. |
| Current load | Sixteen country postings for a design-rating project opened between 14 and 30 October, and its help article already notes an access backlog. This role was posted on 29 October. |
Contractors compare platforms and move between them. Support quality is part of what keeps the best raters on a project.
| Platform | Payout | Identity check | Support model and the gap |
|---|---|---|---|
| HumanSignal Services | Wallet, weekly runs, USD 35 bank minimum, PayPal or bank | Third-party provider, ID and selfie, two attempts | Zendesk plus Discord. Promises that a person reads every ticket, which makes response time the brand. |
| Outlier (Scale AI) | Weekly, PayPal, AirTM or bank | Government ID check | Help centre and tickets at very large scale; reply speed is a frequent theme in contributor forums. |
| DataAnnotation | PayPal, profile email must match | ID and selfie, VPN off | Email support only, with no community channel for project questions. |
| Mercor | Stripe Connect weekly, Wise where Stripe is unsupported | Persona, plus Stripe KYC | A documentation portal. Its March 2026 breach exposed contractor identity documents, so ID handling is now a trust question across the industry. |
| Alignerr (Labelbox) | Stripe Connect, PayPal or Wise | SMS, then Persona at project match | Intercom help centre with in-app chat, plus Discord. The closest model to HumanSignal's. |
Payout and verification rows from each platform's own help pages or docs where available; support-model notes summarise public contributor discussion.
Every ticket sits at one step. The step names the owner before the message is fully read.
| Step | Typical ticket | Owner | First check |
|---|---|---|---|
| Sign-up | Verification email missing (often in spam), wrong email, joined the wrong organisation so Identity & Payments is missing | Services Support | Which organisation the account sits in |
| ID check | Declined photo, pending result, second attempt failed, name differs from bank account | Services, then Verification/Trust | Decline reason and attempts used |
| Tax form | W-8BEN or W-9, "Rate Pending", backup withholding, 1099 questions | Services, Finance for corrections | Is the form on file? |
| Payout method | PayPal unavailable in the country, Payoneer setup, returned payment | Services | Method active and in the contractor's own name |
| Project | Assessment result, retake, empty queue, paused, removed | Project Operations | Project status before account status |
| Work | Task will not load or submit, work disappeared | Support Engineering | Status page, then other reports in the last 30 minutes |
| Wallet | Approved tasks not in the wallet, short pay, below the minimum | Services, Project Ops for approvals | Has the weekly run happened? |
| Payout | Processed but not received | Services, then Payments/Finance | Inside or past the two-week window |
| Any step | Takeover, fake recruiter or "moderator", disturbing content | Safety/Security | Protect first: hold payouts, lock sessions |
Read from the public contractor help centre and status page on 4 November 2026. A young help centre (written June and July 2026) carries draft-stage items; each one below maps to a ticket type the desk would otherwise answer by hand. The demo re-checks them live.
| Finding | What the pages say | Ticket effect and fix |
|---|---|---|
| ID reset: two answers | "My ID was denied" says a failed check "is not final" and to ask support for a reset. "Can a Rejected ID Be Manually Verified?" says staff cannot override, two attempts only. | Each such ticket needs two replies. Keep one article with the real rule and the retry guide. |
| Wrong email: two answers | One article says most cases need no new account; the other says to create a new account and ask support to delete the old one. | Duplicate accounts and a second ticket. One article, one path. |
| Editor notes left in | 16 "[TODO: ...]" notes are live in 14 articles, nine of them screenshot placeholders. One asks for a concrete activation time because "a concrete range would significantly reduce tickets on this topic". | Activation-time tickets stay open until that number exists. Publish the range. |
| Questions answered twice | A long-form set (9 July) and a short set (15 July) are both live: ten topics have two articles, including ID retry, pending ID, activation and Discord joining. | Search returns both. Merge into one and redirect. |
| 1099 wording | Non-US data-collection postings say "1099 contractor assignment"; the help centre says non-US contractors file a W-8BEN and are generally exempt from Form 1099. | A predictable tax-question stream from new markets. Align the posting template. |
| Two programme names | Four articles say HumanSignal Labs, seven say HumanSignal Services. | Feeds "is this real?" tickets, which already have their own article. Use one name. |
| Incidents that would page | Of 27 published incidents since November 2022, 15 stopped or put at risk labeling or review, and 4 more degraded it (for example "Errors when saving Annotations"). | A contractor notice template per class, posted at acknowledgement, with a time-credit line. |
| Posting duty | How I would do it | Detailed in |
|---|---|---|
| Own and resolve contractor tickets in Zendesk | Tag by journey step on arrival; resolve status and how-to in one reply that links the single right article; every reply ends with the next update and its time. | §03, demo Queue |
| Single point of contact across teams | The specialist who takes the ticket keeps it through every handoff and sends every update. The contractor never gets "please contact Payments". | §05 |
| Escalate to the right team | A fixed handoff format: what happened, what I checked, the evidence with personal data masked, the ask, and the date the contractor was promised. | §05, demo |
| Monitor Discord | Answer project questions in thread; hide posts carrying ID, bank or login details and open a private ticket; watch for fake moderators asking for fees or codes. | §06 |
| Apply P0 to P3 | Severity from impact and scope; the contractor's "urgent" sets tone only. Five similar reports in 30 minutes is P0. | §05 |
| Flag repetitive tickets for self-service | Rank ticket types by agent hours saved, fix the help-centre conflicts first, then build status and reset flows. | §07 |
| Quarterly volume and coverage review | Tickets by hour against shifts, re-escalation and reopen rates, secondary-escalation count on pages. | §07 |
| P0 on-call, 15-minute acknowledgement | Pre-written notices per incident class; acknowledge, post the notice, one handoff, updates every 30 minutes. | §05, demo On-call |
P0 wording is the posting's. P1 to P3 targets are my planning proposal, sized to the posting's 15 to 30 minutes of handling per ticket.
| Level | Definition | First response | Resolve target |
|---|---|---|---|
| P0 | Systemic inability to work, widespread payment or verification failure, major production incident, credible safety or security concern. Pages on-call. | 15 min (page ack) | 4 h or incident close |
| P1 | One contractor fully blocked from earning, or money or an account at risk: takeover, payout to a changed destination, pay more than one cycle late, distress after harmful content. | 1 h in shift | 24 h |
| P2 | Blocked on one thing with a path forward: missing payout inside the window, declined ID check, login or 2FA, platform error for one person. | 4 h | 72 h |
| P3 | How-to, status, paperwork and preferences: tax forms, payout method changes, retakes, empty queues, Discord roles. | 24 h | 5 days |
To, ticket and severity, contractor ID and country, the issue, what I checked in order, the evidence with ID and account numbers masked, the ask, and the date the contractor was told. One note per ticket; one note per incident.
Pinned Discord notice and a Zendesk macro: what is wrong, that no ticket is needed, that lost time will be handled, next update in 30 minutes. At resolution: a closing notice that asks for task IDs from anyone who lost submitted work.
| Case | Checks in order | Reply carries | Owner, severity |
|---|---|---|---|
| "Not paid" from six countries in eight minutes | Weekly run happened; lines sent; methods active; countries spread across rails, so the problem sits upstream of any one bank | One macro: known issue, no action needed, update in one hour | Payments/Finance, P0 incident |
| Payout destination changed by someone else | Login history, new device and country, time of the change, any pending payout | Account secured, payout paused, we never ask for codes or fees | Safety/Security, P1 |
| Second ID attempt failed | Decline reason for both attempts; name match with profile and payout account | What happened, that staff cannot override, what Verification will review and when | Verification/Trust, P2 |
| Passport number posted in Discord | Hide the post; open a private ticket; check the ID-check status | In channel: moved to a private ticket, please never post documents here | Services, P2 |
| "The content today was disturbing" | Any risk to life first; task ID and project; illegal content to Safety unviewed | You can stop now with no effect on pay or standing; Safety will contact you | Safety/Security, P1 (P0 if life at risk) |
The posting says about 81% of tickets need two or fewer agent comments. On a synthetic 13-week history tuned to that figure (in the demo), these move the most agent hours.
| Ticket type | Self-service fix | Prerequisite |
|---|---|---|
| Payout not received | A payout tracker in the wallet: weekly run date, transfer started, provider reference, expected arrival date | One article for the two-week window |
| ID check declined | The decline reason and the retry guide shown inside the verification flow, with attempts remaining | Resolve the two-answers conflict first |
| Login and 2FA | Self-service 2FA reset behind an identity check | Takeover safeguards on payout changes |
| Onboarding and activation | A status line per step with a stated activation range | The number the TODO note asks for |
| Empty queue, paused, retakes | Project status in the dashboard and a pinned Discord post per project | Project Ops posts status in one place |
| Discord roles | A bot that grants project roles from the roster | Roster as the single source |
Takeovers, harmful content, quality disputes, name mismatches and anything where money moved wrongly. These need judgement, privileged access and accountability.
With a contractor base weighted to Asia, Africa and Latin America, two North American day shifts leave about 44% of modelled tickets arriving with nobody on shift; a third shift in the Asia-Pacific day cuts that to 17%.
Role: Services Support Specialist, HumanSignal (public job posting, 2026).
HumanSignal's public contractor help centre (all 111 articles through its public API), status page incident history, contractor job postings on its careers board, and company pages. Read 4 November 2026. Competitor rows from each platform's own help pages where available.
The demo is my own build for this application. Contractors, tickets and the ticket history are synthetic; severity targets, thresholds and the coverage model are my assumptions. The incident history and the help-centre audit are read live.
Demo: humansignal-support.pages.dev · Contractor help centre · Approved tasks and the weekly run · ID override policy · Tax information · Status page · Careers · Heartex to HumanSignal · Mercor payments · Outlier payments · DataAnnotation FAQ · Alignerr ID verification
Independent homework for the HumanSignal Services Support Specialist role · 2026 · edwardtay.com