Triage any contractor message
Paste a message in English, Spanish, Portuguese or Malay/Indonesian. The desk returns the category, severity with its reasons, the owner, the checks in order, a reply and the internal handoff with personal data masked.
Live platform status
Read from status.humansignal.com (public Statuspage API) when you open this tab.
P0 pager drill
The posting's rule: acknowledge a P0 page in about 15 minutes or it escalates to the week's secondary. One second here is one minute.
Every public incident, run through the P0 rule
Which of HumanSignal's published incidents would have paged Services Support on-call, which needed only a pinned Discord notice, and which contractors never noticed. Click a row for the contractor announcement.
| Incident | Started (UTC) | Impact | Desk | Why |
|---|
What should move to self-service
The posting says about 81% of tickets need two or fewer agent comments. On a synthetic 13-week history tuned to that figure, this ranks ticket types by the agent hours a deterministic self-service flow would save, then checks coverage by hour against the shift plan.
| Ticket type | Tickets | Closed in 2 or fewer comments | Avg handling | Self-service fix | Agent hours saved / quarter |
|---|
Coverage by hour (quarterly review)
Help-centre audit
Self-service deflects tickets only when the articles agree with each other and with the desk. This reads HumanSignal's public contractor help centre live (Zendesk Guide API) and checks it before any macro links to it.
Two articles, two answers
Unfinished editor notes published to contractors
| Article | Note as published |
|---|
Same question, two articles
| Long-form article | Short article |
|---|
Which article each desk macro links
| Ticket type | Article(s) |
|---|
Severity
| Level | Definition | First response | Resolve target |
|---|
P0 wording is from the posting. P1 to P3 targets are my planning proposal for discussion, sized to the posting's 15 to 30 minutes of handling per ticket.
Routing: resolve here or hand off
| Ticket type | Base | Owner | First check |
|---|
Routing check on HumanSignal's own questions
Every question-type article in the public contractor help centre is a question contractors ask. I labelled each title with the ticket type that should route it, then ran the classifier. The first version scored 15.3%: its phrases were written for first-person messages. Adding three ticket types the help centre has (activation, wallet withdrawals, sign-up email) and weighted domain terms brought it to the figure below. The terms were written with these titles in view, so this is an in-sample check; the 27 queue tickets, written earlier, are the independent one and all still route correctly.
| Article title (misses only) | Should route to | Routed to |
|---|
Desk rules
- One owner per contractor. The specialist who takes the ticket keeps it through every handoff and sends every update.
- Discord is public. Anything with payment, identity or login detail moves to a private ticket, and the post is hidden.
- Support never types bank details, approves an identity, re-adds someone to a project or overturns a review. It routes those with evidence and a date.
- Five contractors with the same payment, verification, access or platform problem inside 30 minutes is one incident, raised as P0.
- A contractor's "urgent" sets the tone of the reply. Severity comes from impact and scope.
- Every handoff masks personal data and states what was checked, the ask and the date the contractor was promised.
About this prototype
I built this for my application to the Services Support Specialist role at HumanSignal. It is not HumanSignal software and uses no HumanSignal data except the public status page.
- Queue. 27 synthetic contractor tickets across Zendesk and Discord. Each one is classified (20 types, taken from the help centre's own sections), given a severity with the reasons shown, routed to the owner the posting names, and drafted: a reply to the contractor and a handoff note with personal data masked.
- Cluster detection. Six payout tickets from six countries inside 8 minutes become one P0 incident on the batch.
- On-call. The live Statuspage feed of status.humansignal.com, every published incident mapped to P0, a pinned notice or no action, plus a 15-minute pager drill with escalation to the secondary.
- Self-service. A 4,200-ticket synthetic history tuned to the posting's 81% figure, ranked by hours saved, and a coverage check by hour.
- Routing check. The classifier is scored on the 98 question-type article titles from HumanSignal's own help centre (Playbook tab).
- Replies cite the help centre. Each drafted reply links the live article for its ticket type.
- Tests. node tests/run.mjs checks every sample ticket's category and severity, the cluster, masking, the status mapping and the report figures.
- Help-centre audit. Reads every public contractor article live and lists unfinished editor notes, articles that answer the same question differently, duplicates, and the article each macro should link.
Policies in the replies (weekly payout runs, the $35 bank minimum and Pay Me Now, two ID attempts with no manual override, W-8BEN or W-9 under Identity & Payments) follow HumanSignal's public contractor help centre as read on 4 November 2026. Internal tools, vendors and thresholds are my assumptions.