Nobody should log in and go hunting to find out something needed them.

So work comes to you instead. Queues rank by the consequence of waiting rather than by age: a three-day-old row with a lapsing ownership claim outranks a twelve-day-old one without.

37 task kindsone owner eachself-closingraised once, not per scan

company · action inbox 37 KINDS

Real product screens. Figures shown in them are seed data from a demo workspace, not customer results.

Why it works when others do not

Four properties. Drop any one and the queue dies.

01 One task, one owner

Routed to a single person, not broadcast to a team where everyone assumes somebody else has it.

02 Deep-linked

It opens the exact screen with the action loaded, not the module's home page.

03 Self-closing

Do the thing and it closes itself. There is no mark-as-done step to forget.

04 Fires once

Not every time a background scan runs. This is the whole reason people keep reading it.

That last one matters more than it sounds. A queue that re-raises the same item every fifteen minutes trains everyone to stop reading it, and then it is worse than nothing.

The catalogue

All 37 of them. You will never see every one.

Which appear depends on your configuration and your permissions. A recruiter and a finance approver share almost none of this list.

Candidates and intake 12

Review new candidate(s)
Review ranked shortlist
Resolve possible duplicate
Confirm classification
Review low-confidence résumé
Review unparseable résumé
Review unreadable JD
Review AI-disabled résumé
Resolve intake routing conflict
Review resurfaced pool candidate
Fix Drive connection
Review retention sweep

Assessment 3

Chase pending assessment
Review assessment result
Review screening knockout

Interviews 4

Confirm interview time
Submit feedback
Schedule next round
Run the next round

Offers and joining 4

Ready to offer
Chase offer
Confirm candidate joined
Confirm role close

Agencies and money 10

Review submitted candidate
Approve / decline agency
Decide approval
Submission sent back
Submission rejected — in-house
Invoice ready to raise
Approve vendor invoice
Review invoice mismatch
Invoice disputed
Resolve invoice dispute

Administration 4

Confirm automated action
Automation dispatch
Escalate overdue task
Act on recommendation

Note Four of these are résumé-quality tasks that used to be undocumented: a low-confidence parse, an unparseable file, an unreadable JD, and one where AI parsing was disabled. Each was quietly costing candidates their scores, which is exactly the kind of thing a queue is for.

Routing

You decide who gets which kind.

Per person or per role, per task kind. The default is sensible; the point is that when a task lands on the wrong desk, that is a setting rather than a support ticket.

The badge is the honest numberThe count beside Action Inbox is open tasks assigned to you, not to your team. If it says three, there are three things only you can clear.

Batch by typeFilter to approvals for one sitting and feedback for another, rather than working a mixed pile.

Task routing settings, mapping each kind of task to a person or role

One-tap confirmations

“The system just did it” is never an explanation for something that mattered.

Anything consequential an automation wants to do becomes a Confirm task rather than a silent action, and the confirmation is recorded. That rule is enforced in the core, not by a setting somebody can quietly turn off.

30 trigger event typesAutomation rules react to real events. What happens without a human, and what asks first, is yours to set.

Notifications are a different thingThe inbox is work you must do. Notifications are things you may want to know. Ignore a notification and usually nothing happens; ignore a task and something is genuinely stuck.

Automation rules settings, showing what runs without a human and what asks first

What this part does not do

Worth knowing before the demo, not after.

✕It is not a notification feed notifications are things you may want to know

✕Nothing here is broadcast to a team one owner, so it cannot be everyone's job

✕No SLA escalation policies you author one overdue escalation, not a policy engine

✕No mobile app or push notifications in-app and email only

✕It goes completely static without workers no new tasks, no auto-completion, screens still load

✕No custom task types the 37 are the catalogue

Keep going

The rest of the record.

Candidate intake Four doors in, duplicate checking, the talent pool The score receipt Seven factors, and why the number equals the table Pipeline & assessments Requisitions, stages, gates, measured scores Interviews Rounds, panels, scorecards, and no calendar engine Offers & joining Approvals, two guards on the amount, onboarding Ownership & fees Who submitted first, and who gets paid

Book a demo → All 18 areas